Thursday, 2013-04-04

*** lloydde has joined #openstack-meeting00:01
*** crank has quit IRC00:03
*** mestery has quit IRC00:04
*** crank has joined #openstack-meeting00:05
*** woodspa has quit IRC00:17
*** flaper87 has quit IRC00:20
*** anniec has quit IRC00:23
*** danwent has quit IRC00:30
*** cdub_ has quit IRC00:31
*** zhuadl has joined #openstack-meeting00:34
*** tomoe_ has joined #openstack-meeting00:48
*** lloydde has quit IRC00:54
*** zhuadl has quit IRC01:01
*** tomoe_ has quit IRC01:03
*** tomoe_ has joined #openstack-meeting01:03
*** tomoe_ has quit IRC01:08
*** tomoe_ has joined #openstack-meeting01:10
*** ryanpetrello has quit IRC01:10
*** Mandell has quit IRC01:10
*** ryanpetrello has joined #openstack-meeting01:10
*** ctracey|away has joined #openstack-meeting01:12
*** terry7 has quit IRC01:22
*** dansmith has quit IRC01:23
*** dansmith has joined #openstack-meeting01:24
*** zhuadl has joined #openstack-meeting01:26
*** colinmcnamara has quit IRC01:27
*** ryanpetrello has quit IRC01:28
*** dwcramer has joined #openstack-meeting01:28
*** tomoe_ has quit IRC01:28
*** noslzzp has joined #openstack-meeting01:28
*** tomoe_ has joined #openstack-meeting01:29
*** tomoe__ has joined #openstack-meeting01:31
*** tomoe_ has quit IRC01:32
*** noslzzp has quit IRC01:33
*** fnaval has joined #openstack-meeting01:33
*** jog0 has quit IRC01:35
*** rmohan has quit IRC01:41
*** dkehn has quit IRC01:42
*** ryanpetrello has joined #openstack-meeting01:45
*** ryanpetrello has quit IRC01:51
*** rmohan has joined #openstack-meeting01:52
*** mestery has joined #openstack-meeting01:53
*** dwcramer has quit IRC02:04
*** dwcramer has joined #openstack-meeting02:18
*** rmohan has quit IRC02:22
*** dabo- has quit IRC02:22
*** rmohan has joined #openstack-meeting02:23
*** sandywalsh has quit IRC02:27
*** edleafe has joined #openstack-meeting02:34
*** lillie has quit IRC02:43
*** lillie- has joined #openstack-meeting02:43
*** tomoe__ has quit IRC02:45
*** tomoe_ has joined #openstack-meeting02:45
*** Mandell has joined #openstack-meeting02:47
*** sandywalsh has joined #openstack-meeting02:47
*** tomoe_ has quit IRC02:50
*** zyluo has joined #openstack-meeting02:56
*** dkehn has joined #openstack-meeting03:00
*** tomoe_ has joined #openstack-meeting03:08
*** martine has joined #openstack-meeting03:12
*** martine has quit IRC03:14
*** vipul is now known as vipul|away03:15
*** esker has joined #openstack-meeting03:24
*** tomoe_ has quit IRC03:35
*** ryanpetrello has joined #openstack-meeting03:35
*** tomoe_ has joined #openstack-meeting03:35
*** tomoe__ has joined #openstack-meeting03:37
*** tomoe_ has quit IRC03:40
*** novas0x2a|laptop has quit IRC03:44
*** SergeyLukjanov has joined #openstack-meeting03:59
*** fifieldt has joined #openstack-meeting04:07
*** ryanpetrello has quit IRC04:11
*** almaisan` has joined #openstack-meeting04:15
*** cdub_ has joined #openstack-meeting04:16
*** sivel_ has joined #openstack-meeting04:16
*** dripton__ has joined #openstack-meeting04:16
*** jeblair_ has joined #openstack-meeting04:16
*** almaisan-away has quit IRC04:16
*** cp16net has quit IRC04:16
*** cdub has quit IRC04:16
*** sivel has quit IRC04:16
*** dripton_ has quit IRC04:16
*** jeblair has quit IRC04:16
*** cp16net has joined #openstack-meeting04:16
*** zigo_ has quit IRC04:16
*** ayoung has quit IRC04:17
*** ayoung has joined #openstack-meeting04:17
*** zigo has joined #openstack-meeting04:18
*** cdub has joined #openstack-meeting04:19
*** rushiagr has joined #openstack-meeting04:19
*** zhuadl has quit IRC04:20
*** lloydde has joined #openstack-meeting04:31
*** reed has quit IRC04:33
*** KurtMartin has joined #openstack-meeting04:33
*** matiu has quit IRC04:35
*** Mandell_ has joined #openstack-meeting04:36
*** Mandell has quit IRC04:38
*** arata has joined #openstack-meeting04:39
*** garyk has quit IRC04:46
*** sacharya has joined #openstack-meeting04:50
*** sirushti has quit IRC04:50
*** mfaraji has joined #openstack-meeting04:52
*** danwent has joined #openstack-meeting04:54
*** zyluo has quit IRC04:56
*** SergeyLukjanov has quit IRC04:56
*** boris-42 has joined #openstack-meeting05:00
*** KurtMartin has quit IRC05:02
*** sirushti has joined #openstack-meeting05:03
*** marun has quit IRC05:16
*** matiu has joined #openstack-meeting05:18
*** matiu has quit IRC05:18
*** matiu has joined #openstack-meeting05:18
*** mfaraji has quit IRC05:19
*** koolhead17 has joined #openstack-meeting05:20
*** zbitter has joined #openstack-meeting05:26
*** lloydde has quit IRC05:27
*** lloydde has joined #openstack-meeting05:27
*** afazekas has joined #openstack-meeting05:29
*** zaneb has quit IRC05:30
*** lloydde has quit IRC05:32
*** SpamapS_ has joined #openstack-meeting05:33
*** Brainspa1kle has joined #openstack-meeting05:33
*** asalkeld_ has joined #openstack-meeting05:33
*** chmouel_ has joined #openstack-meeting05:34
*** anderstj_ has joined #openstack-meeting05:35
*** maurosr- has joined #openstack-meeting05:35
*** creiht_ has joined #openstack-meeting05:37
*** EntropyWorks_ has joined #openstack-meeting05:37
*** rainya has quit IRC05:38
*** asadoughi has quit IRC05:38
*** rainya has joined #openstack-meeting05:38
*** asalkeld has quit IRC05:38
*** Brainspackle has quit IRC05:38
*** SpamapS has quit IRC05:38
*** johnpur has quit IRC05:38
*** chmouel has quit IRC05:38
*** anderstj has quit IRC05:38
*** EntropyWorks has quit IRC05:38
*** maurosr has quit IRC05:38
*** antonym has quit IRC05:38
*** creiht has quit IRC05:38
*** anderstj_ is now known as anderstj05:38
*** BeardyMcBeards has quit IRC05:38
*** BeardyMcBeards has joined #openstack-meeting05:38
*** rainya has quit IRC05:38
*** amir1 has joined #openstack-meeting05:38
*** EntropyWorks_ is now known as EntropyWorks05:38
*** briancline has quit IRC05:38
*** tr3buchet has quit IRC05:38
*** rainya has joined #openstack-meeting05:38
*** sirushti has quit IRC05:39
*** diogogmt has quit IRC05:40
*** esker has quit IRC05:40
*** antonym has joined #openstack-meeting05:41
*** esker has joined #openstack-meeting05:41
*** antonym is now known as Guest598805:41
*** resker has joined #openstack-meeting05:42
*** briancline has joined #openstack-meeting05:42
*** afazekas has quit IRC05:44
*** esker has quit IRC05:46
*** SpamapS_ is now known as SpamapS05:46
*** Slower has quit IRC05:50
*** sirushti has joined #openstack-meeting05:51
*** sacharya has quit IRC05:51
*** matiu has quit IRC05:57
*** lloydde has joined #openstack-meeting05:58
*** oomichi has joined #openstack-meeting06:02
*** garyk has joined #openstack-meeting06:02
*** lloydde has quit IRC06:07
*** fifieldt_ has joined #openstack-meeting06:07
*** mrunge has joined #openstack-meeting06:14
*** markmcclain has joined #openstack-meeting06:20
*** otherwiseguy has quit IRC06:20
*** mikal has quit IRC06:22
*** salv-orlando has joined #openstack-meeting06:24
*** henrynash has joined #openstack-meeting06:25
*** henrynash has quit IRC06:28
*** gongysh has quit IRC06:30
*** gongysh has joined #openstack-meeting06:30
*** danwent has quit IRC06:38
*** gongysh_ has joined #openstack-meeting06:40
*** gongysh has quit IRC06:40
*** mikal has joined #openstack-meeting06:41
*** matiu has joined #openstack-meeting06:43
*** gongysh__ has joined #openstack-meeting06:45
*** gongysh_ has quit IRC06:46
*** vipul|away is now known as vipul06:47
*** lillie- is now known as lillie06:56
*** lloydde has joined #openstack-meeting06:58
*** jhenner has joined #openstack-meeting06:58
*** rezax` has quit IRC07:01
*** gongysh has joined #openstack-meeting07:01
*** gongysh__ has quit IRC07:02
*** lloydde has quit IRC07:03
*** egallen has joined #openstack-meeting07:04
*** nati_ueno has quit IRC07:05
*** afazekas has joined #openstack-meeting07:10
*** tr3buchet has joined #openstack-meeting07:11
*** esdaniel has joined #openstack-meeting07:12
*** oomichi has quit IRC07:13
*** vipul is now known as vipul|away07:21
*** leseb has joined #openstack-meeting07:22
*** gongysh_ has joined #openstack-meeting07:22
*** gongysh has quit IRC07:23
*** markmcclain has quit IRC07:24
*** davidhadas has quit IRC07:24
*** nati_ueno has joined #openstack-meeting07:25
*** tomoe_ has joined #openstack-meeting07:26
*** tomoe__ has quit IRC07:26
*** koolhead17 has quit IRC07:31
*** esdaniel has quit IRC07:31
*** tomoe_ has quit IRC07:32
*** flaper87 has joined #openstack-meeting07:34
*** zhuadl has joined #openstack-meeting07:34
*** jhenner has quit IRC07:41
*** zhuadl has quit IRC07:44
*** SergeyLukjanov has joined #openstack-meeting07:47
*** matiu has quit IRC07:47
*** zhuadl has joined #openstack-meeting07:49
*** sirushti has quit IRC07:50
*** henrynash has joined #openstack-meeting07:52
*** esdaniel has joined #openstack-meeting07:54
*** zhuadl has quit IRC07:57
*** lloydde has joined #openstack-meeting07:59
*** zykes- has quit IRC08:00
*** zykes- has joined #openstack-meeting08:01
*** sirushti has joined #openstack-meeting08:02
*** henrynash has quit IRC08:03
*** lloydde has quit IRC08:03
*** derekh has joined #openstack-meeting08:07
*** davidha has joined #openstack-meeting08:07
*** SergeyLukjanov has quit IRC08:07
*** rahmu has joined #openstack-meeting08:11
*** tomoe_ has joined #openstack-meeting08:14
*** SergeyLukjanov has joined #openstack-meeting08:14
*** Mandell_ has quit IRC08:15
*** sirushti has quit IRC08:16
*** mrunge has quit IRC08:21
*** lloydde has joined #openstack-meeting08:22
*** derekh has quit IRC08:23
*** tomoe_ has quit IRC08:23
*** MarkAtwood has joined #openstack-meeting08:26
*** MarkAtwood has left #openstack-meeting08:28
*** sirushti has joined #openstack-meeting08:30
*** leseb has left #openstack-meeting08:30
*** mrunge has joined #openstack-meeting08:31
*** tomoe_ has joined #openstack-meeting08:32
*** derekh has joined #openstack-meeting08:35
*** lloydde has quit IRC08:39
*** tomoe_ has quit IRC08:39
*** boris-42 has quit IRC08:40
*** jhenner has joined #openstack-meeting08:42
*** johnthetubaguy has joined #openstack-meeting08:47
*** tomoe_ has joined #openstack-meeting08:48
*** zbitter is now known as zaneb08:49
*** afazekas has quit IRC08:49
*** SergeyLukjanov has quit IRC08:54
*** SergeyLukjanov has joined #openstack-meeting08:56
*** davidhadas has joined #openstack-meeting09:06
*** dricco has quit IRC09:06
*** davidha has quit IRC09:09
*** sankarshan has joined #openstack-meeting09:12
*** alexpilotti has joined #openstack-meeting09:13
*** afazekas has joined #openstack-meeting09:15
*** jhenner has quit IRC09:16
*** jhenner has joined #openstack-meeting09:17
*** rushiagr has left #openstack-meeting09:18
*** arata has quit IRC09:26
*** psedlak has joined #openstack-meeting09:27
*** darraghb has joined #openstack-meeting09:29
*** mikal has quit IRC09:39
*** mikal has joined #openstack-meeting09:41
*** sankarshan is now known as sankarshan_away09:42
*** SergeyLukjanov has quit IRC09:47
*** asalkeld_ is now known as asalkeld10:03
*** BobBallAway is now known as bobball10:04
*** bobball is now known as BobBall10:04
*** nati_ueno has quit IRC10:06
*** rahmu has quit IRC10:06
*** mkollaro has joined #openstack-meeting10:07
*** egallen has quit IRC10:07
*** boris-42 has joined #openstack-meeting10:12
*** zbitter has joined #openstack-meeting10:13
*** zaneb has quit IRC10:16
*** zbitter is now known as zaneb10:16
*** johnthetubaguy1 has joined #openstack-meeting10:19
*** johnthetubaguy has quit IRC10:19
*** SergeyLukjanov has joined #openstack-meeting10:23
*** tomoe_ has quit IRC10:29
*** tomoe_ has joined #openstack-meeting10:31
*** tomoe_ has quit IRC10:35
*** tomoe_ has joined #openstack-meeting10:35
*** tomoe_ has quit IRC10:39
*** garyk has quit IRC10:41
*** egallen has joined #openstack-meeting10:41
*** dwcramer has quit IRC10:49
*** rahmu has joined #openstack-meeting10:50
*** garyk has joined #openstack-meeting10:55
*** dansmith has quit IRC10:55
*** dansmith has joined #openstack-meeting11:01
*** mfaraji has joined #openstack-meeting11:01
*** dprince has joined #openstack-meeting11:02
*** topol has joined #openstack-meeting11:03
*** egallen has quit IRC11:07
*** egallen has joined #openstack-meeting11:08
*** Guest5988 has quit IRC11:08
*** Guest5988 has joined #openstack-meeting11:08
*** Guest5988 is now known as antonym11:08
*** davidha has joined #openstack-meeting11:09
*** dansmith has quit IRC11:09
*** davidhadas has quit IRC11:11
*** markmcclain has joined #openstack-meeting11:15
*** pcm_ has joined #openstack-meeting11:16
*** anteaya has joined #openstack-meeting11:21
*** topol has quit IRC11:22
*** dansmith has joined #openstack-meeting11:23
*** esdaniel is now known as esdaniel-away11:25
*** dprince has quit IRC11:30
*** psedlak has quit IRC11:32
*** ttrifonov is now known as ttrifonov_zZzz11:32
*** psedlak has joined #openstack-meeting11:32
*** ttrifonov_zZzz is now known as ttrifonov11:33
*** vkmc has joined #openstack-meeting11:36
*** fifieldt_ has quit IRC11:38
*** sirushti has quit IRC11:43
*** ayoung has quit IRC11:48
*** sirushti has joined #openstack-meeting11:53
*** boris-42 has quit IRC11:57
*** sandywalsh has quit IRC12:01
*** dwcramer has joined #openstack-meeting12:02
*** esdaniel-away is now known as esdaniel12:02
*** davidhadas has joined #openstack-meeting12:05
*** davidha has quit IRC12:08
*** markmcclain has quit IRC12:12
*** sivel_ is now known as sivel12:14
*** sandywalsh has joined #openstack-meeting12:15
*** arata has joined #openstack-meeting12:21
*** maurosr- is now known as maurosr12:22
*** resker has quit IRC12:23
*** esker has joined #openstack-meeting12:23
*** mrunge has quit IRC12:25
*** rnirmal has joined #openstack-meeting12:26
*** sankarshan_away is now known as sankarshan12:27
*** esker has quit IRC12:28
*** esdaniel is now known as esdaniel-away12:28
*** boris-42 has joined #openstack-meeting12:30
*** mfaraji has quit IRC12:30
*** ryanpetrello has joined #openstack-meeting12:31
*** psedlak has quit IRC12:32
*** psedlak has joined #openstack-meeting12:32
*** ryanpetrello has joined #openstack-meeting12:32
*** jbr_ has quit IRC12:36
*** psedlak has quit IRC12:36
*** psedlak has joined #openstack-meeting12:37
*** noslzzp has joined #openstack-meeting12:41
*** noslzzp has quit IRC12:41
*** adalbas has joined #openstack-meeting12:42
*** egallen has quit IRC12:43
*** joesavak has joined #openstack-meeting12:44
*** rnirmal_ has joined #openstack-meeting12:45
*** rnirmal_ has quit IRC12:45
*** egallen has joined #openstack-meeting12:48
*** dwcramer has quit IRC12:48
*** rnirmal has quit IRC12:49
*** jbr_ has joined #openstack-meeting12:50
*** arata has quit IRC12:50
*** dprince has joined #openstack-meeting12:57
*** boris-42 has quit IRC12:57
*** noslzzp has joined #openstack-meeting12:57
*** boris-42 has joined #openstack-meeting13:04
*** rnirmal has joined #openstack-meeting13:12
*** radez_g0n3 is now known as radez13:13
*** lbragstad has quit IRC13:14
*** davidhadas has quit IRC13:19
*** woodspa has joined #openstack-meeting13:25
*** alexpilotti has quit IRC13:28
*** ayoung has joined #openstack-meeting13:28
*** timello has quit IRC13:29
*** lbragstad has joined #openstack-meeting13:29
*** timello has joined #openstack-meeting13:30
*** afazekas has quit IRC13:34
*** alexpilotti has joined #openstack-meeting13:40
*** alexpilotti has quit IRC13:45
*** sacharya has joined #openstack-meeting13:49
*** dwcramer has joined #openstack-meeting13:49
*** Gordonz has joined #openstack-meeting13:50
*** Gordonz has quit IRC13:53
*** Gordonz has joined #openstack-meeting13:53
*** eharney has joined #openstack-meeting13:53
*** martine has joined #openstack-meeting13:55
*** ewindisch has quit IRC13:55
*** tomoe_ has joined #openstack-meeting13:56
*** ladquin has quit IRC13:56
*** esker has joined #openstack-meeting13:57
*** maksimov has joined #openstack-meeting13:59
*** n0ano has joined #openstack-meeting14:00
*** lloydde has joined #openstack-meeting14:02
*** stevemar has joined #openstack-meeting14:03
*** Kharec has quit IRC14:08
*** adalbas has quit IRC14:09
*** creiht_ is now known as creiht14:11
*** Slower has joined #openstack-meeting14:11
*** dwcramer has quit IRC14:12
*** cp16net is now known as cp16net|away14:13
*** creiht has quit IRC14:15
*** creiht has joined #openstack-meeting14:15
*** topol has joined #openstack-meeting14:15
*** ewindisch has joined #openstack-meeting14:15
*** fnaval has quit IRC14:16
*** mtreinish has joined #openstack-meeting14:16
*** mrodden has joined #openstack-meeting14:17
*** adalbas has joined #openstack-meeting14:18
*** jeblair_ is now known as jeblair14:19
*** egallen has quit IRC14:24
*** davidkranz has quit IRC14:25
*** davidkranz has joined #openstack-meeting14:25
*** egallen has joined #openstack-meeting14:26
*** markmcclain has joined #openstack-meeting14:26
*** davidkranz_ has joined #openstack-meeting14:27
*** davidkranz has quit IRC14:27
*** maoy has joined #openstack-meeting14:27
*** adalbas has quit IRC14:28
*** egallen has quit IRC14:28
*** mrunge has joined #openstack-meeting14:32
*** jsavak has joined #openstack-meeting14:33
*** joesavak has quit IRC14:37
*** tongli has joined #openstack-meeting14:39
*** diogogmt has joined #openstack-meeting14:40
*** adalbas has joined #openstack-meeting14:43
*** garyTh has joined #openstack-meeting14:44
*** marun has joined #openstack-meeting14:47
*** fnaval has joined #openstack-meeting14:50
*** chmouel_ is now known as chmouel14:50
*** mfaraji has joined #openstack-meeting14:52
*** mfaraji has quit IRC14:54
*** sacharya has quit IRC14:54
*** otherwiseguy has joined #openstack-meeting14:56
*** gordc has joined #openstack-meeting14:58
*** lbragstad has quit IRC14:58
*** llu-laptop has joined #openstack-meeting14:58
*** dwcramer has joined #openstack-meeting14:58
*** gongysh_ has quit IRC14:59
*** DanD has joined #openstack-meeting14:59
*** lloydde has quit IRC14:59
jd__#startmeeting ceilometer15:00
openstackMeeting started Thu Apr  4 15:00:18 2013 UTC.  The chair is jd__. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: ceilometer)"15:00
openstackThe meeting name has been set to 'ceilometer'15:00
jd__#link https://wiki.openstack.org/wiki/Meetings/MeteringAgenda15:00
sandywalsho/15:00
llu-laptopo/15:00
dhellmanno/15:00
n0anoo/15:00
DanDo/15:00
dragondmo/15:01
jd__hi everybody15:01
gordco/15:01
jd__#topic asalkeld to release python-ceilometerclient 1.0.0 and document the release process15:01
*** openstack changes topic to "asalkeld to release python-ceilometerclient 1.0.0 and document the release process (Meeting topic: ceilometer)"15:01
jd__I imagine asalkeld's sleeping tight15:01
*** Yada has joined #openstack-meeting15:02
jd__but I didn't see any release unfortunately15:02
*** mrodden has quit IRC15:02
jd__#action asalkeld to release python-ceilometerclient 1.0.0 and document the release process15:02
jd__#topic jd__ reassign nova-cell/ceilometer session to nova15:02
*** egallen has joined #openstack-meeting15:02
*** openstack changes topic to "jd__ reassign nova-cell/ceilometer session to nova (Meeting topic: ceilometer)"15:02
jd__done, it has been merged with http://summit.openstack.org/cfp/details/14715:02
jd__oh wait15:03
jd__#topic BREAKING NEWS15:03
*** openstack changes topic to "BREAKING NEWS (Meeting topic: ceilometer)"15:03
jd__we released Grizzly https://launchpad.net/ceilometer/grizzly/2013.115:03
*** apmelton has joined #openstack-meeting15:03
ogelbukhcongrats everyone )15:03
dhellmannnice!15:03
llu-laptopwonderful15:03
jd__#info we released Grizzly https://launchpad.net/ceilometer/grizzly/2013.115:03
gordcawesome.15:03
jd__thanks ttx for the release job :)15:04
*** lbragstad has joined #openstack-meeting15:04
*** cp16net|away is now known as cp16net15:04
llu-laptopone question, what does the 1 in 2013.1 mean?15:04
jd__first of the year15:05
llu-laptopok, I used to though it was Jan.15:05
jd__(at least that's my understanding)15:05
jd__llu-laptop: no, Havana will be 2013.2 AFAIK :)15:05
dhellmannright15:05
*** epende has joined #openstack-meeting15:05
jd__#topic Preparing for summit15:06
*** openstack changes topic to "Preparing for summit (Meeting topic: ceilometer)"15:06
*** garyk has quit IRC15:06
*** nealph has joined #openstack-meeting15:06
jd__#info Doc team would like for us to review https://wiki.openstack.org/wiki/Blueprint-restructure-documentation and think about how we fit in15:06
*** Mike656 has joined #openstack-meeting15:06
jd__ideas on that?15:06
dhellmannI looked over that earlier this week. I don't see any issue with us fitting in just like the other projects.15:06
dhellmannThe reorg seems to make sense to me, too.15:07
llu-laptopIs this reorg decided?15:07
dhellmannno, it's under discussion by the doc team15:07
jd__does't shock me either15:08
*** mrodden has joined #openstack-meeting15:08
dhellmannright, no surprises or issues15:08
*** esdaniel-away is now known as esdaniel15:08
jd__dhellmann: should we send a feedback to someone about this?15:08
llu-laptopwhy moving "reference manual" out of "user manual"?15:09
dhellmannno, annegentle just asked us to be prepared to talk about our doc needs in terms of that framework15:09
llu-laptopIs it more logical to put the "options" explanation just in user manual?15:09
dhellmannshe is interested in feedback if we have it, but we don't have to reply formally15:09
jd__llu-laptop: you probably want to ask the doc team, not us :-)15:10
jd__dhellmann: ok, cool15:10
jd__dhellmann: there may be a session we need to attend?15:10
dhellmannjd__: we do have a session in the doc track, let me find the link15:10
jd__ok15:10
esdanielo/ sorry for late arrival15:11
jd__I'm having a hard time tracking session since they're not scheduled yet :)15:11
dhellmann#link restructure documentation session http://summit.openstack.org/cfp/details/12915:11
jd__ack15:11
dhellmann#link documentation for newly integrated projects http://summit.openstack.org/cfp/details/10415:11
dhellmannthe latter is the one we requested15:11
jd__so we should be there indeed :->15:11
dhellmannyes :-)15:11
jd__ok -- anything else about the summit?15:12
llu-laptopwhen will the detailed schedule be ready?15:12
jd__llu-laptop: by Tuesday15:12
llu-laptopI mean for whole summit15:12
sandywalshlooking forward to seeing the schedule15:13
sandywalshThurs is going to be busy15:13
jd__definitely15:14
*** reed has joined #openstack-meeting15:14
jd__#topic Open discussion15:15
*** openstack changes topic to "Open discussion (Meeting topic: ceilometer)"15:15
jd__we're running out of topics :)15:15
sandywalshthat'll all change once we get the CM summit schedule :)15:16
esdanieldhellmann: unless I'm mistaken asalkeld did release v1.0.0, though may not of updated docs it was:15:16
esdanielgit tag -s 1.0.015:17
esdanielgit push gerrit 1.0.015:17
sandywalshdragondm, did you want to give any updates on the nova changes you've been making around notifications?15:17
jd__esdaniel: you're right15:17
dhellmannesdaniel: maybe we need a job to build the lib and push it to pypi, then?15:17
dhellmannoh, no, it's there!15:18
dhellmann#link https://pypi.python.org/pypi/python-ceilometerclient15:18
esdanielyep, it's a little behind after it syncs first with our mirror then pypi i believe15:18
jd__so we didn't get any notification as I though we would, but it's done15:18
jd__fantastic15:18
jd__zigo: https://pypi.python.org/pypi/python-ceilometerclient for you!15:18
dragondmYah, in basic, I've got some changes that should allow nova to publish notifications for all the info that ceiliometer's compute agent emits.15:18
esdanielasalkeld did it 5 mins after you asked him :-)15:18
dhellmannmaybe we can make that job post to irc and/or the mailing list15:18
zigojd__: Tagged? KEWL! :)15:18
esdanieldhellmann +115:19
jd__dragondm: cool15:19
jd__dhellmann: +1 :)15:19
jd__dragondm: under review or merged?15:19
dragondmIsn't up in gerrit yet.15:19
dragondmWill be sometime this week or early next.15:20
dragondm(was waiting for the grizzly branch to cut)15:20
dhellmanndragondm: add me as a reviewer, when you post it, please?15:20
dragondmWill do.15:20
llu-laptopdraondm: does that mean we no longer need the ceilometer.compute.nova_notifier?15:20
dragondmYup, that is the idea.15:20
llu-laptopdragondm: good to hear that15:21
*** pcm_ has quit IRC15:21
dragondmAlso in the pipeline is a lightweight UDP notification mechanism.15:21
jd__dragondm: nice too :)15:22
*** pcm_ has joined #openstack-meeting15:22
jd__does it sound possible that at some point nova can emit Ceilometer meters directly rather than notifications?15:22
jd__or is it still too soon?15:23
dhellmannwould we want that?15:23
dragondmThat should also be up in oslo shortly. I'm still working on the receiving side for cm. Hope to have that before summit.15:23
*** garyk has joined #openstack-meeting15:23
jd__dhellmann: I know what I would want that, why wouldn't you want that? ;)15:23
jd__s/what/why/15:23
dragondmjd__ I'm not to sure about that...15:24
dhellmannjd__: given the amount of trouble we've had tying the two projects together all along, it seems like agreeing on a common format is better than having nova try to use our format15:24
jd__right15:25
jd__by the way, I think that at some point we're going to split the collector15:26
jd__don't know if the subject poped in someone else mind so far15:26
sandywalshpublishing directly to CM isn't really a good idea unless it's going directly into the CM queue. If CM goes down, production will suffer15:26
dhellmannjd__: yeah, it makes sense to split up the 2 parts of the collector15:27
jd__dhellmann: ok, I may tackle that at some point15:27
dragondmAye. Tho that is part of the impetus for udp notifications. The downside is they get dropped if the receiver isn't there. The upside is they don't overload rabbit in that case.15:27
dhellmannjd__: I also had the idea of letting the notification handler just write to the database directly, instead of sending all of the data back out (depending on the pipeline configuration, of course)15:27
zigojd__: Any idea why the Git repo on Alioth has so many tags, like 1.0.1, 1.0.2 and the like?15:27
jd__zigo: url?15:28
jd__dragondm: I imagine it's an operator choice for trade off at this point anywya15:28
dragondmyup.15:28
zigojd__: http://anonscm.debian.org/gitweb/?p=openstack/python-ceilometerclient.git15:28
* zigo don't understand why15:28
jd__dhellmann: depending on the pipeline configuration yeah -- that may be tricky but why not15:28
*** egallen has quit IRC15:29
zigoGosh, it has *cinder* tags in.15:29
zigoWhat a mess.15:29
*** lloydde has joined #openstack-meeting15:29
* zigo will fix.15:29
*** markmcclain has quit IRC15:29
*** ladquin has joined #openstack-meeting15:29
dhellmannjd__: well, the daemon that handles notifications could have a different pipeline config file from the other daemons (specified on the command line when the service starts)15:30
jd__dhellmann: but that'd work against my split idea15:30
dhellmann?15:30
sandywalshdhellmann, +115:30
dhellmannoh, you don't want the notifications handler to touch the database?15:31
*** lloydde_ has joined #openstack-meeting15:31
jd__dhellmann: yeah, that doesn't sound like a good isolation scheme15:31
dragondmyah, also another change I have for oslo is a routing notification driver, that can send notifications to other drivers according to event_type15:31
jd__dhellmann: now you understand why I'd be happy if nova would use ceilometer.pipeline to publish metering15:32
dragondmHaving a separate store (e.g a mongo db) that you throw the notifications into wouldn't be a bad idea.15:32
dhellmanndragondm: is that something the deployer should configure?15:32
dhellmannjd__: we'll have to put it in a separate library for that to work, I think15:33
dragondmdhellmann: Yes. Uses a json config file. It's similar to python's logging confs, but with a better syntax.15:33
*** egallen has joined #openstack-meeting15:33
jd__dhellmann: sure, but would it work (= be accepted) if we do that?15:33
dhellmannjd__: well, it would just need to work as a notification driver, right?15:33
jd__dragondm: better syntax? doesn't sound like a great challenge to me ;-)15:34
dragondmHeh. yah.15:34
*** afazekas has joined #openstack-meeting15:34
*** lloydde has quit IRC15:34
jd__dhellmann: no that you tell it, YEAH! :)15:34
jd__s/no/now/15:34
jd__with dragondm's changes, it could be awesome15:35
*** vipul|away is now known as vipul15:35
dhellmannand if we can make it a small package, so they don't have to install all of ceilometer on the hypervisor...15:35
jd__nova -> multipublisher -> meters over rpc, udp, whatever -> destination15:35
dragondmI will put you folks on as reviewerd when I put those changes up.15:35
*** sacharya has joined #openstack-meeting15:35
jd__dhellmann: we may put pipeline things and drivers in oslo15:35
dhellmannso rip the publishing stuff out of ceilometer and have both nova and ceilometer use it15:35
dhellmannyeah15:36
sandywalshthat's the beauty of the notification driver, operators choice15:36
jd__so we totally kill the ceilometer piece doing the notifications -> meters conversion15:36
*** boris-42 has quit IRC15:36
jd__less round trip15:36
jd__less load on AMQP15:36
jd__more happyness15:36
dhellmannjd__: yep15:36
dragondmAlways good (less load on amqp) The current nova-cells is killing rabbit as-is15:36
jd__good to hear15:37
jd__I'll plan out some bp about that15:37
dragondmAlways in favor of more happyness.15:37
dhellmannI was just about to suggest that :-)15:37
sandywalshthe downside is that notification drivers don't fit in the exception handling chain (they're a nice-to-have)15:37
sandywalshby keeping them simple (like a rabbit publish) the complexity is moved to somewhere that that handle it better15:38
jd__sandywalsh: I don't think it's worth than what we have now15:38
sandywalsh(retries, etc)15:38
sandywalshworst?15:38
*** danwent has joined #openstack-meeting15:38
jd__worst.15:38
sandywalsh:)15:38
jd__:)15:39
sandywalshstill, I don't think complexity belongs in the nova notification driver15:39
sandywalshit a dumb animal15:39
sandywalshit's15:39
esdaniel:-)15:39
sandywalsh(another beer debate I feel :)15:40
jd__sandywalsh: bah I'll be happy to move more close to nova, but I don't feel like I'm the one that can +2 that ;)15:40
*** eglynn_ has joined #openstack-meeting15:41
*** Mike656 has quit IRC15:41
jd__anything else or should I end this madness?15:42
* dhellmann is ready to get off of this crazy train15:42
esdanielot: john o'hara speaking on 18/4 in london if anyone's interested15:42
eglynn_apologies folks, caught up in another meeting15:42
esdanieloops 17/4 my bad15:43
jd__hi eglynn_15:43
eglynn_hey15:43
*** lloydde has joined #openstack-meeting15:43
eglynn_thankfully meetings are logged, I can get caught up ...15:43
jd__eglynn_: it hasn't be too long, but we're closing15:44
jd__eglynn_: something you want to talk about?15:44
eglynn_nope, I'm good thanks ...15:44
*** devananda has quit IRC15:45
tongliHi, guys,15:45
zigojd__: I got something else if you don't mind.15:45
jd__zigo: go ahead15:45
*** devananda has joined #openstack-meeting15:45
zigodistutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('setuptools-git>=0.4')15:45
tonglican I ask you about the gauge on the storage (swift)?15:45
zigoThat's in the clean target.15:45
zigoThat's really annoying for my cowbuilder.15:45
zigoIt would be nice not to have such requirement at clean time.15:46
*** markmcclain has joined #openstack-meeting15:46
*** markmcclain has quit IRC15:46
*** lloydde_ has quit IRC15:46
tongliEnabled ceilometer on swift,15:46
jd__zigo: we only have this listed in test-requires15:46
tongligetting some information back, but could not figure out what these numbers really mean.15:46
jd__zigo: which isn't read by setup.py AFAICT15:47
jd__tongli: which one?15:47
tonglianyone here can help explain how to make sense of these numbers.15:47
tongli@jd__, let me get an example here.15:47
jd__tongli: you may want to ask on #openstack-metering though15:48
tongliyeah, did that yesterday, no response.15:48
tongliI can ask again.15:48
jd__zigo: #openstack-metering ? :)15:48
jd__tongli: we're all there15:48
tonglik15:48
jd__#endmeeting15:48
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"15:48
tonglilet me move to that channel then.15:48
openstackMeeting ended Thu Apr  4 15:48:46 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-04-04-15.00.html15:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-04-04-15.00.txt15:48
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-04-04-15.00.log.html15:48
*** lloydde_ has joined #openstack-meeting15:48
*** gordc has left #openstack-meeting15:49
*** llu-laptop has quit IRC15:50
*** lloydde has quit IRC15:50
*** apmelton has left #openstack-meeting15:51
ewindischdamn. laptop running out of power - finding outlet - shouldn't be too late.15:52
*** ewindisch has quit IRC15:53
zigojd__: ftp://117.121.243.213/debian/pool/grizzly/main/p/python-ceilometerclient/ :)15:53
jd__zigo: works?15:53
zigoPlease be my guess and try...15:53
zigogest15:53
zigoshit15:54
zigoguest15:54
*** egallen has quit IRC15:55
zigojd__: There was no commit between the RC and the release or what?15:56
zigo(of ceilometer, not the client)15:56
*** egallen has joined #openstack-meeting15:56
*** lloydde_ has quit IRC15:56
*** epende has quit IRC15:57
jd__zigo: none15:59
zigo:)16:00
jd__zigo: no bug, no commit16:00
zigoCongrats.16:00
*** rpodolyaka has joined #openstack-meeting16:00
*** colinmcnamara has joined #openstack-meeting16:00
*** colinmcnamara has left #openstack-meeting16:01
*** torandu has joined #openstack-meeting16:02
*** dwcramer has quit IRC16:03
*** mkollaro has quit IRC16:03
*** romcheg has joined #openstack-meeting16:04
*** ewindisch has joined #openstack-meeting16:04
*** tomoe_ has quit IRC16:04
*** garyk has quit IRC16:04
*** tomoe_ has joined #openstack-meeting16:05
ewindischhello16:05
ewindischsorry about the delay16:05
ewindisch#startmeeting16:05
openstackewindisch: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'16:05
ewindisch#startmeeting Python316:05
openstackMeeting started Thu Apr  4 16:05:36 2013 UTC.  The chair is ewindisch. Information about MeetBot at http://wiki.debian.org/MeetBot.16:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:05
*** openstack changes topic to " (Meeting topic: Python3)"16:05
openstackThe meeting name has been set to 'python3'16:05
* dhellmann misread that error message and was worried he was here for the wrong meeting16:05
dhellmanno/16:05
ewindischso, besides me being late again - who do we have ? :)16:05
*** hemna has joined #openstack-meeting16:06
dhellmannhi, sorry I missed the first meeting last week and thanks for getting the ball rolling on this!16:06
ewindischanyone else for the roll-call?16:06
ewindischdhellmann: no problem. Hopefully the momentum can be maintained - I'm a bit concerned nobody seems to be here, though.16:07
dhellmannmarkmcclain had another obligation this week16:07
ewindischbeing release day doesn't help, I'm sure.16:08
dhellmanntrue16:08
ewindisch#topic action items last meeting16:08
rpodolyakaHello, guys! I'm with you :)16:08
*** openstack changes topic to "action items last meeting (Meeting topic: Python3)"16:08
ewindisch1. ewindisch follow up with -infra to discuss gating16:08
ewindischhello rpodolyaka.16:08
*** mattray has joined #openstack-meeting16:09
ewindischhonestly, I didn't have a lot to do with this because markmcclain was still working on a py3 test.16:09
*** tomoe_ has quit IRC16:09
ewindisch2. markmacclain to look at writing a py3 test16:09
ewindischhe isn't here… so16:09
ewindisch#action ewindisch to chase down markmacclain, ask about py3 test16:10
ewindisch3. dripton to dig through oslo deps for version compat16:10
ewindischdripton did this.16:10
ewindisch#link https://wiki.openstack.org/wiki/Python3Deps16:11
dhellmannewindisch: I updated the notes from that to answer the question about stevedore or cliff (I forget which it was)16:11
dhellmannboth should work with 3.316:11
dhellmannwe're targeting 3.3, right?16:11
ewindischdhellmann: that isn't decided. It seems conclusive we need to support at *least* 3.216:12
dhellmannah16:12
dhellmannI misremembered16:12
*** martine_ has joined #openstack-meeting16:12
dhellmannI guess we'll have to see what we can do with the dependencies before making a final call on that.16:12
*** john5223 has joined #openstack-meeting16:12
ewindischIt was intended to review dripton's dependency analysis and use that as part basis for making a recommendation to the TC16:13
ewindisch4. ewindisch to look at PSF sponsorship16:13
dhellmannthe eventlet issue is going to be painful16:13
ewindischdhellmann: yeah.16:13
dhellmannewindisch: did you have any luck with sponsorship?16:14
*** martine has quit IRC16:14
rpodolyakaI filled some missing deps on wiki and tried to make one of the deps (mox) to be compatible with both Python 2.x and Python 3.x but it has turned out to be a bit harder than I thought...16:14
ewindischI did look at this. It seems we could ask for funding, if we have things that we'd want to fund. That would probably be a sprint, or perhaps seeking a PSF sponsorship for eventlet folks ;-)16:14
ewindischreally the question isn't if we can get money, the question is what would we use it for?16:14
dhellmanngood point16:15
dhellmannsprint funding is pretty easy to get, but the OpenStack foundation could probably cover those expenses, too16:15
ewindischI thought it would've been good if we had a sponsored sprint at the summit, but a bit too late for that now.16:15
dhellmannfunding longer term development would also be something to look at, if we can identify someone interested in doing the work on an upstream dependency16:16
ewindischright. eventlet specifically comes to mind.16:16
ewindischand finally…16:17
ewindisch5. dripton create wiki pages16:17
dhellmannI wonder (pie in the sky) if we should just consider moving to tulip instead of porting eventlet. More "modern". 16:17
ewindischcompleted ;)16:17
ewindisch#topic async framework / eventlet16:18
*** openstack changes topic to "async framework / eventlet (Meeting topic: Python3)"16:18
ewindischdhellmann: I'm thinking the same thing.16:18
dhellmannif we're going to make the leap...16:18
ewindischor… porting eventlet to PEP315616:18
*** lbragstad has quit IRC16:18
*** SergeyLukjanov has quit IRC16:18
dhellmannI don't know enough about the implementation to know if that's possible16:19
dhellmannhow much of our code actively knows about eventlet?16:19
ewindischnote that if we decide to use Tulip or PEP3156, that work presently depends on Python3.316:20
romchegThere seems to be only a reference implementation for Tulip...16:20
rpodolyakadhellmann: wsgi modules in every project, some workarounds on DB pooling...16:20
*** mkollaro has joined #openstack-meeting16:20
ewindischdhellmann: the rpc stuff is pretty tied to it, but it could be switched out easily enough, I think.16:20
dhellmannromcheg: yeah, it's early but parts of it will be in python 3.4 when it's done16:20
ewindischthe web parts are probably more tightly coupled16:20
dhellmannrpodolyaka: also the rpc lib, probably?16:20
ewindischdhellmann: yes, rpc.16:20
*** esdaniel is now known as esdaniel-away16:20
dhellmannewindisch: well, that fits with my goal to have us stop using our own wsgi module in favor of pecan and wsme :-)16:21
ewindischdhellmann: if we did that, we could switch off eventlet a whole lot easier.16:21
dhellmannthe rpc bit is more troubling, but at least it is isolated if we have to make major changes16:21
dhellmannewindisch: I will add that to my notes for the summit session16:21
ewindischdhellmann: of course, pecan doesn't support Python 3 either.16:22
dhellmannare you sure?16:22
ewindischwell, not according to the PyPi categories.16:22
dhellmannah, I'll check into that16:23
dhellmannthe intent is certainly to support it, but maybe it's not quite there yet16:23
romchegNeither does wsme — Python 3.3 is not supported16:23
dhellmannchristophe is quite open to patches, so we could get that updated16:23
*** lbragstad has joined #openstack-meeting16:23
ewindischromcheg: it supports python 3.2, and very little changed there. I suspect it probably works on 3.3, or could be made to work easily16:24
dhellmannyeah, that's probably just a matter of updating the tox.ini file16:24
romchegewindisch: yeah, probably easier than porting eventlet to py316:24
ewindischdhellmann: for RPC, we might be able to drop-in replace eventlet with anything else that provides (co)threading.16:26
ewindischHowever, I know that for ZeroMQ, I used patterns that I would've avoided if not for eventlet and its behaviorisms. I'm not certain if that code would need to be rewritten, or if moving to PEP3156  would simply *allow* it to be rewritten.16:26
dhellmannthose modules are pretty small, and the api is well defined. it might actually be simpler to just write new implementations.16:26
dhellmannI'd rather do a little extra work than live with extra layers of indirection16:27
ewindischdhellmann: for 3156?16:27
dhellmannyeah, across the rpc drivers16:27
dhellmannnot just zmq16:27
ewindischI can't imagine rewriting the implementations.16:27
dhellmannthe question is really what the upstream libraries we're using do16:27
dhellmannI just mean openstack.common.rpc, not all of kombu, etc.16:28
*** dwcramer has joined #openstack-meeting16:29
dhellmannit's a lot of work, but the question is whether it's better to do it or live with layers of crud for a while16:29
ewindischdhellmann: I can't see rewriting or even heavily refactoring each of the impl_* files in a single release. Worse, we're talking about trying to stabilize and push these into their own library at some point.16:29
ewindischdhellmann: I think that the eventlet problem has little to do with any cleanup/refactoring effort there.16:30
dhellmannagreed16:30
ewindischanyway, we should have someone look seriously at PEP3156, eventlet, and tulip.16:30
dhellmannyeah, I just wanted to point out that we should consider options besides trying to force-fit eventlet just so we don't have to change our own code :-)16:31
*** garyk has joined #openstack-meeting16:32
*** koolhead17 has joined #openstack-meeting16:32
*** ndipanov has quit IRC16:32
*** jaypipes has joined #openstack-meeting16:32
ewindischdhellmann: I agree. I honestly think that there is a chance PEP3156 could be a good thing. If we supported that, it might be configurable to choose eventlet, gevent, zeromq, or twisted eventloops. (or whatever)16:32
dhellmann+116:32
ewindischnot sure that making that pluggable would work in practice, just as I'm not sure that anything but RabbitMQ works with our Kombu driver, but we can dream. :)16:33
ewindischso if that is wrapped up…16:33
dhellmann:-)16:33
ewindischI'd like to create an action item for someone(s) to look at tulip / pep315616:34
ewindischbut there aren't many people here16:34
ewindischand I think we're all busy with the summit prep16:35
romchegI can do that16:35
dhellmannyeah, I can't really commit to anything until after ODS16:35
dhellmanngreat!16:35
*** lloydde has joined #openstack-meeting16:35
ewindischromcheg: thanks!16:35
*** davidhadas has joined #openstack-meeting16:35
ewindisch#action romcheg investigate PEP3156 / tulip / eventlet issues16:35
ewindisch#topic meeting schedule16:36
*** openstack changes topic to "meeting schedule (Meeting topic: Python3)"16:36
ewindischso one thing I forgot to ask last week was if this time / frequency worked for everyone.16:36
*** zyluo has joined #openstack-meeting16:36
dhellmannit works great for me, it's right after the ceilometer meeting16:36
ewindischit works great for me too, but I set the time :)16:37
ewindischdhellmann: is there a reason the ceilometer meeting was split into alternating schedules?16:37
dhellmannwe have a few core members in the Asia-Pacific region16:38
*** esdaniel-away is now known as esdaniel16:38
dhellmannit's easier for them to attend the meetings on wednesdays16:38
dhellmannwe have to try to span Europe, US, and Australia/China (I think)16:39
ewindischI thought as such.16:39
ewindischwell, the other issue is frequency… I didn't want to overburden people with meetings, so I set it every other week.16:39
ewindischregardless, I wanted to bring this up  in today's meeting, but we don't have enough people to decide.16:40
ewindischdeferring until after ODS16:40
dhellmannI think that makes a lot of sense, too. At least until we make some significant progress, I'm not sure there will be much to talk about every week.16:40
ewindisch#topic open discussion16:40
*** openstack changes topic to "open discussion (Meeting topic: Python3)"16:40
ewindischdhellmann: agreed16:42
dhellmanndo we have any ODS sessions planned? would it make sense to get together for an open space session, at least?16:42
ewindischthere is an ODS session planned.16:42
dhellmanngood, I'll watch for that when the schedule is released16:42
ewindischit is preapproved, unlike my other proposals :)16:43
*** mrodden1 has joined #openstack-meeting16:43
*** john5223 has quit IRC16:43
dhellmannheh16:43
ewindischdhellmann: think it would be valuable if someone did a lightning talk? <unfortunately, I don't have the time>16:44
dhellmannI don't remember lightning talks on the schedule from last time. Did I just miss them?16:44
ewindischyou must have missed them.16:44
ewindischthey've been very badly promoted16:44
ewindischand attended16:45
dhellmannI remember them from the Folsom summit16:45
ewindischhmm. I think they had them?16:45
ewindischI'll follow up with Kathy or Stefano. I really hope they have them again, and better promote them as well.16:46
*** bdpayne has quit IRC16:46
*** mrodden has quit IRC16:46
dhellmannI don't see them on http://openstacksummitapril2013.sched.org/16:46
*** mrunge has quit IRC16:46
*** bdpayne has joined #openstack-meeting16:47
ewindischyeah, I just sent an email to Stefano / Thierry / Kathy16:50
ewindischanyway, unless there is anything else, I'll #endmeeting16:50
* dhellmann has nothing to add16:50
ewindischthanks romcheg, dhellmann!16:51
ewindisch#endmeeting16:51
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:51
openstackMeeting ended Thu Apr  4 16:51:05 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python3/2013/python3.2013-04-04-16.05.html16:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python3/2013/python3.2013-04-04-16.05.txt16:51
openstackLog:            http://eavesdrop.openstack.org/meetings/python3/2013/python3.2013-04-04-16.05.log.html16:51
*** jog0 has joined #openstack-meeting16:51
*** dontalton has joined #openstack-meeting16:53
*** donaldngo_hp has joined #openstack-meeting16:53
*** rahmu has quit IRC16:55
*** esdaniel is now known as esdaniel-away16:55
*** masayukig has joined #openstack-meeting16:56
*** rpodolyaka has left #openstack-meeting16:56
*** ravikumar_hp has joined #openstack-meeting16:56
*** dwalleck has joined #openstack-meeting16:57
*** romcheg has quit IRC16:57
*** chair6 has joined #openstack-meeting16:59
*** jhullinge has joined #openstack-meeting16:59
*** egallen has quit IRC17:01
*** EmilienM has quit IRC17:01
*** davidkranz_ is now known as davidkranz17:01
*** ludo has joined #openstack-meeting17:01
*** salv-orlando has quit IRC17:02
*** ludo is now known as Guest2882117:02
davidkranzAny one here for the qa meeting?17:02
ravikumar_hphi17:02
dwalleckhere17:02
davidkranzsdague, jaypipes : Around?17:02
*** terry7 has joined #openstack-meeting17:03
davidkranzmtreinish: ??17:03
zyluo Hi17:03
jaypipeshi17:03
jaypipesdavidkranz: go ahead and /startmeeting..17:03
*** JoseRaxQE has joined #openstack-meeting17:03
davidkranz#startmeeting qa17:03
openstackMeeting started Thu Apr  4 17:03:43 2013 UTC.  The chair is davidkranz. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
*** nati_ueno has joined #openstack-meeting17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: qa)"17:03
openstackThe meeting name has been set to 'qa'17:03
davidkranz#topic Summit17:03
*** openstack changes topic to "Summit (Meeting topic: qa)"17:04
davidkranzI just saw an email to the qa list about a scenarios session.17:04
ravikumar_hpunreviewed17:04
davidkranzI don't know when that session was submitted.17:04
donaldngo_hphi17:04
davidkranzI don't think it was there when we discussed the sessions.17:05
ravikumar_hpi think 10days ago17:05
JoseRaxQEhey17:05
jaypipesdavidkranz: yeah, I think it was a bit of a latecomer17:05
*** malini has joined #openstack-meeting17:05
davidkranzI am still not sure I understand what the real purpose is.17:05
dwalleckMy understanding was talking about more project integration tests (nova/cinder integration tests, etc)17:06
*** RAX-Sam has joined #openstack-meeting17:06
davidkranzdwalleck: If they are currently deficient they should be improved but that is already a clear part of Tempest's mission.17:07
dwalleckdavidkranz: agreed17:07
jaypipes++17:07
davidkranzSo perhaps this should be discussed as part of the last session which is to discuss missing tests.17:07
davidkranzravikumar_hp: I think you submitted that one.17:08
ravikumar_hpyes. test gaps17:08
jaypipesdavidkranz: either that, or we continue to discuss it in the mailing list thread and make it clear that just because something may be long-running doesn't mean it doesn't belong in tempest17:08
ravikumar_hpto convert to blueprints that will address in Havava .17:08
davidkranzravikumar_hp: I think blueprints for missing tests is the right approach.17:08
*** Mandell has joined #openstack-meeting17:09
ravikumar_hpok.17:09
davidkranzjaypipes: I hope we hash out the whole "what tests should be in tempest" issue at the summit.17:09
ravikumar_hpdavidkranz: no session needed ?17:09
davidkranzravikumar_hp: I don't think so but you can bring this up in your gap session.17:10
*** jhenner has quit IRC17:10
davidkranzravikumar_hp: I just don't see it as a new concept that we need a separate session for.17:10
jaypipesI agree.17:10
ravikumar_hpok17:10
davidkranzravikumar_hp: Great.17:10
davidkranzI think it would be good for session proposers to put up etherpads before the summit.17:11
dwalleckmakes sense]17:11
davidkranzIs there some "official" place to put such etherpads.17:11
*** eglynn_ has quit IRC17:12
dwalleckisn't there an openstack etherpad?17:12
davidkranzdwalleck: Yes, I meant the links so people can find them.17:12
davidkranzdwalleck: to the individual session etherpads. Ideally they would be in the session descriptions online.17:13
*** derekh has quit IRC17:13
davidkranzWe could ask ttx about that.17:13
davidkranzdwalleck: Are you guys going to post the new stuff you talked about before the summit?17:14
dwalleckdavidkranz: we're working out getting it right now. Sam?17:15
RAX-SamHey David. It's been posted to StackForge. I've finished the the zuul, build configuration, etc... and it's waiting on Approval17:15
RAX-Samhttps://review.openstack.org/#/c/25870/17:15
RAX-SamWhen that goes through, the repositories will be hosted on StackForge17:15
davidkranzRAX-Sam: OK, it would be really helpful if we could take a look before the summit so the discussion can be better informed.17:16
RAX-SamAbsolutely. Has been our goal. :-)17:16
davidkranzRAX-Sam: If there is some kind of holdup in the official process perhaps you could point us at an informal link to the code.17:17
*** otherwiseguy has quit IRC17:17
davidkranz#topic General Discussion17:17
*** openstack changes topic to "General Discussion (Meeting topic: qa)"17:17
RAX-SamThere has been some activity and review today. If it hasn't been merged by today I'll email some links around tomorrow17:17
davidkranzRAX-Sam: Thanks!17:17
davidkranzAny one have a topic to bring up?17:18
donaldngo_hphttps://blueprints.launchpad.net/tempest/+spec/update-expected-exception-tests is implemented can someone with previleges close it?17:18
*** mpavlase has joined #openstack-meeting17:18
afazekasrelated to the scenario testing the policy.json mentioned by ykaul17:19
davidkranzdonaldngo_hp: Just did that.17:19
donaldngo_hpthank you17:20
davidkranzafazekas: Not sure what you are pointing at.17:20
afazekasWe should extend the default policy.json 's in-order to have a user type which is member of tenant but does not have permission to do anything17:20
*** chair6 has left #openstack-meeting17:21
afazekasby the default policy many operation is doable by everyone17:21
afazekaswe do not test the code path when the operation rejected by the policy module17:21
davidkranzafazekas: Oh, I see.17:22
afazekasI think the policy module itself is tested by unit test17:22
dwalleckI think the trick is that there's no guarantee in a given environment what the policy.json is17:22
davidkranzafazekas: Doesn't trying to do an admin thing as non-admin cover that?17:22
afazekasI do not thing so17:23
*** mattray has quit IRC17:23
afazekassome cases yes, but in many case it is not17:23
dwalleckYou could do generated tests from a policy.json, but that would definitely need a lot of work17:23
afazekasyes17:23
davidkranzafazekas: Which code path are you saying is not covered? It is potentially different for each project, no?17:23
afazekaswhen the policy module rejects on operation17:24
mtreinishdavidkranz: here now sorry, lunch went long17:24
davidkranzdwalleck: Isn't that unit-test territory?17:24
*** ijw has quit IRC17:24
afazekaswe have test cases for attemting operations from differnt tenent, but it is differnt decision17:24
dwalleckdavidkranz: Not necessarily17:24
*** johnthetubaguy1 has quit IRC17:24
afazekasdavidkranz: the correctness of the policy module itself is a unit test territory imho17:25
*** Kharec has joined #openstack-meeting17:25
afazekasbut the usage of the policy module is not17:25
*** cp16net is now known as cp16net|away17:25
*** DanD has left #openstack-meeting17:25
davidkranzafazekas: So this heads back to the issue of how complete a functional api test tempest is supposed to be.17:25
davidkranzafazekas: There seem to be many opinions about this.17:26
*** bdpayne has quit IRC17:26
afazekashttps://blueprints.launchpad.net/tempest/+spec/add-glance-policy-tests17:26
*** ijw has joined #openstack-meeting17:26
afazekasdavidkranz: yes to policy module allow us to define very crazy polices17:26
davidkranzafazekas: Where would you like to see this discussion end up?17:27
afazekasI would like to add to have two type of "regular" users17:28
dwalleckI think the difference is "Does policy.json work?" vs. "Do I have the expected policy.json deployed and does it enforce the permissions I expect?"17:28
afazekasthe "nobody"  type, who does not have any permission, but can authenticate17:28
afazekasand the "somebody" , who has the same capability what the default users have now17:29
*** Mike656 has joined #openstack-meeting17:29
afazekasand the admin users ..17:29
davidkranzafazekas: The blueprint you pointed to does this with admin/non-admin users.17:30
*** markwash has joined #openstack-meeting17:31
davidkranzafazekas: I must be missing something because I don't understand the difference in code path with nobody/regular user.17:31
afazekasdavidkranz: yes, but compare it with the default devstack policy.json17:31
*** noslzzp has quit IRC17:31
afazekashttp://www.fpaste.org/R9d3/17:32
afazekasI do would like to use different policy than in the blueprint17:32
afazekas"default": "role:sombody",17:32
afazekasthe "demo" user should have this right17:33
afazekasthe policy.json which is in the blueprint is copied from an openstack documantion17:34
afazekashttp://docs.openstack.org/developer/glance/policies.html17:35
davidkranzafazekas: I see that.17:35
davidkranzdwalleck: Do you have a comment about this?17:35
*** jhullinge has quit IRC17:36
davidkranzafazekas: How about you propose something specific.17:36
davidkranzafazekas: I don't think there is any objection, just not clear about what needs to be changed.17:37
dwalleckdavidkranz: I see both sides. I'm thinking. If we have this specific config, then we're really just testing that specific configuration17:37
davidkranzdwalleck: Yes, and for that particular project.17:37
davidkranzBut we could have devstack use a policy file that has more meat for testing.17:38
davidkranzI think that is what afazekas wants.17:38
afazekasI started a longer e-mail about the scenario stress and policy testing .., but I did  not finished it and probably I will rephrase it17:38
*** MarkAtwood has joined #openstack-meeting17:38
afazekasdavidkranz: yes17:39
*** Mike656 has quit IRC17:39
davidkranzafazekas: OK, sounds good. We can continue in email.17:39
afazekasok17:39
*** noslzzp has joined #openstack-meeting17:39
davidkranzAnything else to bring up?17:40
*** spzala has joined #openstack-meeting17:40
davidkranzOK, I guess we are done for today then.17:41
sdaguenot from me, just looking forward for portland17:41
davidkranzsdague: Me too.17:42
davidkranzI hope some of us can take a look at the new RAX stuff.17:42
davidkranzSee you all next week.17:43
davidkranz#endmeeting17:43
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:43
openstackMeeting ended Thu Apr  4 17:43:12 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-04-04-17.03.html17:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-04-04-17.03.txt17:43
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-04-04-17.03.log.html17:43
*** RAX-Sam has quit IRC17:43
*** dwalleck has quit IRC17:44
*** sacharya has quit IRC17:46
*** JoseRaxQE has quit IRC17:47
*** romcheg has joined #openstack-meeting17:47
*** SergeyLukjanov has joined #openstack-meeting17:50
*** ravikumar_hp has quit IRC17:53
*** bdpayne has joined #openstack-meeting17:54
*** fnaval has quit IRC17:55
*** lglenden has joined #openstack-meeting17:56
*** Guest28821 has quit IRC17:56
*** maoy_ has joined #openstack-meeting17:57
*** johnthetubaguy has joined #openstack-meeting17:57
*** maoy has quit IRC17:57
*** maoy_ is now known as maoy17:57
*** fnaval has joined #openstack-meeting17:58
*** fnaval has quit IRC17:59
*** fnaval has joined #openstack-meeting18:00
bdpayne#startmeeting OpenStack Security Group18:00
openstackMeeting started Thu Apr  4 18:00:26 2013 UTC.  The chair is bdpayne. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: OpenStack Security Group)"18:00
openstackThe meeting name has been set to 'openstack_security_group'18:00
bdpaynegood morning everyone18:00
noslzzpMorning..18:00
bdpaynewho do we have here for the OSSG meeing?18:00
noslzzpBasil is here.18:00
lglendenI'm here.18:01
*** EmilienM has joined #openstack-meeting18:01
*** romcheg has left #openstack-meeting18:01
*** rellerreller has joined #openstack-meeting18:01
hyakuheiRob here18:02
*** mpavlase has left #openstack-meeting18:02
bdpayneexcellent, so let's get right to it18:02
bdpaynesummit is getting close18:02
bdpayneI'm looking forward to meeting with people f2f there and would like to have some discussions about how to make OSSG most effective going forward18:03
bdpayneSo, between now and then, please be thinking about that :-)18:03
bdpayne#topic OS Security Guide18:03
*** openstack changes topic to "OS Security Guide (Meeting topic: OpenStack Security Group)"18:03
bdpayne@noslzzp any updates on the efforts with a doc sprint?18:04
hyakuheiThis could be such a good project if we can just get it moving.18:04
noslzzpYes, some..18:04
noslzzpSo I discussed the idea internally here and there is some interest in supporting it.18:04
bdpayneglad to hear it18:04
*** johnthetubaguy has quit IRC18:05
*** maoy has quit IRC18:05
noslzzpI've also discussed this with organizations in the public sector.  They are interested as well.18:05
*** mattray has joined #openstack-meeting18:05
*** mrunge has joined #openstack-meeting18:05
bdpayneok, so what are the next steps?18:05
noslzzpAt minimum we can provide facilities at Red Hat.18:05
zykes-hmmms18:05
*** otherwiseguy has joined #openstack-meeting18:05
noslzzpI'm scheduling a meeting with the public sector folks to discuss just that.18:06
*** afazekas has quit IRC18:06
bdpayneok, feel free to loop me into that -- if appropriate18:06
bdpayneI'm also happy to have you take the lead on putting this together :-)18:06
noslzzpThe reason I am somewhat interested in the public sector side is because there is an avalanche of hardening/security work on OpenStack specifically that has been completed to date.18:07
bdpaynesure18:07
noslzzpWe could immediately leverage those best practices, etc.18:07
bdpayneis that work available for public consumption?18:07
*** maoy has joined #openstack-meeting18:07
bdpayneor in process for being made available?18:07
noslzzpProcess of being made.. :)18:08
bdpaynegreat, very glad to hear that18:08
noslzzpIn fact, that's why there is strong interest here..18:08
*** bru has joined #openstack-meeting18:08
*** eglynn_ has joined #openstack-meeting18:08
noslzzpThis would be a great avenue to share.18:08
*** donaldngo_hp has quit IRC18:08
bdpaynewould love to get such people involved in this effort18:08
bdpayneif possible18:08
noslzzpIt's possible.18:08
noslzzpI'll loop you in ..18:09
*** joesavak has joined #openstack-meeting18:09
bdpayneat this point, do you think it would be possible to announce a date for a doc sprint at the summit?18:09
hyakuheiI'd like to stay involved18:09
noslzzp50/50 on an announcement.  I think we can get a location/date pinned down in time.  We'll need to really push though.18:10
noslzzpHyakukei, where are you physically? (not that it matters, just curious).18:10
*** john5223 has joined #openstack-meeting18:10
*** patelna_ has joined #openstack-meeting18:10
hyakuheiI'm uk based but find myself stateside more times than I care to mention ;)18:10
bdpaynenoslzzp let's aim for that as a goal… would be a great venue to get more involved and concrete plans are often a good way to approach that18:11
hyakuheibdpayne and I have also been working with a few public sector bodies who may like to contribute18:11
noslzzpawesome.18:11
* bdpayne thinks that we are all talking about the same public sector bodies, fyi18:11
noslzzpthere's a few of them.. :)18:11
bdpayneok18:11
bdpayneso...18:12
*** jsavak has quit IRC18:12
bdpayne#action noslzzp to push for a date / location for doc sprint to announce at summit18:12
*** Mandell has quit IRC18:12
noslzzpYep.18:12
bdpayne#topic Emails18:12
*** openstack changes topic to "Emails (Meeting topic: OpenStack Security Group)"18:12
bdpayneYou guys probably noticed that there have been many emails coming out this morning18:13
*** vipul is now known as vipul|away18:13
bdpaynevarious security related bugs18:13
bdpayneare people seeing these?  often from Thierry18:13
*** malini has left #openstack-meeting18:13
*** psedlak has quit IRC18:13
hyakuheiI think Thierry closed out a bunch of Security vulns today18:13
bdpayneyeah18:14
*** maoy has quit IRC18:14
bdpayneso I just wanted to make a general remark that we've taken some effort to get these notifications in place18:14
hyakuheiOpenStack Security Group members on LaunchPad should receive these18:14
hyakuheiyeah18:14
bdpaynethe idea is that OSSG members are a good group to provide feedback18:14
hyakuheiShould also point out that openstack-security@lists.openstack.org is a thing now :)18:14
bdpayneand that's, of course, a great way to have some security impact and increase the group's visibility18:14
bdpayneso I encourage folks to take advantage of that and provide feedback comments18:15
lglendenso the bug reports are sent to the launchpad group, and the listserv is used for more general purpose communication?18:15
bdpaynethat's correct18:15
lglendenokay18:15
*** mkollaro has quit IRC18:15
bdpaynewhether we use the dev list or our own mailing list is a judgement call18:15
bdpaynebut, my hope is that we will identify some work to rally around at the summit, and that the mailing list may be a good place for chatter about such things, planning, etc18:16
hyakuhei+118:16
*** martine_ has quit IRC18:16
bdpayne#topic Other Summit Planning18:17
*** openstack changes topic to "Other Summit Planning (Meeting topic: OpenStack Security Group)"18:17
*** martine_ has joined #openstack-meeting18:17
bdpayneSo it sounds like Rob/HP will be setting up something for OSSG to meeting up on Monday evening over food?18:17
bdpaynesorry… hyakuhei18:18
hyakuheiThat's more or less correct18:18
bdpayneheh, ok18:18
hyakuheiNot sure where or what, reasonably confident on when. Could do with a better picture of 'who'18:18
bdpayne#action hyakuhei will advertise OSSG meeting18:19
bdpaynecount me in18:19
hyakuhei:D18:19
hyakuheiI think HP will have a few, I believe APL are in for a few people too18:19
noslzzpSome good parties that night..18:19
bdpayneI suspect that we may be able to get a few additional to show up as well18:19
hyakuheiimho the mirantis ones are not the best, I'm planning that our meal be out in time for the RH one18:19
hyakuheiwhich I'm expecting good things from ;)18:20
noslzzp+118:20
bdpayne+1 to that18:20
hyakuheiI'm guessing 8-12 people atm18:20
bdpaynesounds good18:20
bdpayneany other chatter about the summit?18:20
bdpayneAnyone interested in seeing the Nebula One cloud controller can swing by our booth :-)18:21
noslzzpI am and will. :)18:21
* bdpayne is happy to finally be shipping a product18:21
noslzzpCongrats, btw..18:21
hyakuheiIndeed18:21
bdpaynethx18:21
hyakuheiI'll be coming by, must play with the pretty lights.18:21
bdpayne#topic Open Discussion18:22
*** openstack changes topic to "Open Discussion (Meeting topic: OpenStack Security Group)"18:22
bdpayneanything else for today?18:22
hyakuheiYep18:22
hyakuheiSo I'd like to get the LXC Security Note out of the door.18:23
hyakuhei#link https://bugs.launchpad.net/osn/+bug/115556618:23
uvirtbotLaunchpad bug 1155566 in osn "Note: Keystone Request / Header Size Limits Required to Avoid DoS" [High,Confirmed]18:23
bdpayneis it not already?18:23
bdpayneoh, the DOS security note?18:23
hyakuheidoh s/LXC/Keystone/18:23
bdpaynegot it18:23
*** Mandell has joined #openstack-meeting18:23
hyakuheiJust needs a couple of lines dropping in regarding Nginx/Apache/Other smart ways of doing http limiting18:23
*** pcm___ has joined #openstack-meeting18:24
bdpaynewould be nice to quantify large, perhaps?18:24
*** Yada has quit IRC18:24
hyakuheiYeah, though that's somewhat relative to the available resources18:24
hyakuheiit's a linear exhaustion18:24
bdpaynegotcha18:25
hyakuheiI'll add that info in18:25
bdpaynegreat18:25
bdpaynealso, perhaps add haproxy to the list?18:25
bdpayneotherwise, lgtm18:25
hyakuheigo ahead18:25
*** mrunge has quit IRC18:26
bdpayneok, can do18:27
bdpayneI'll add that and see if I can get some links for the others18:27
bdpaynesometime today ;-)18:27
*** davidh_ has joined #openstack-meeting18:27
bdpayne#action bdpayne to provide some details for OSN18:27
bdpayneanything else?18:27
*** pcm_ has quit IRC18:27
bruIs the web page for your cloud controller up to date?18:28
bdpaynebru please PM me with additional Nebula questions, but yes18:29
bdpayneok, thanks everyone, have a great week18:29
*** davidhadas has quit IRC18:29
bdpayne#endmeeting18:29
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"18:29
openstackMeeting ended Thu Apr  4 18:29:23 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-04-04-18.00.html18:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-04-04-18.00.txt18:29
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-04-04-18.00.log.html18:29
*** rnirmal has quit IRC18:32
*** spzala has quit IRC18:33
*** radez is now known as radez_g0n318:38
*** darraghb has quit IRC18:44
*** novas0x2a|laptop has joined #openstack-meeting18:46
*** rellerreller has quit IRC18:54
*** esker has quit IRC18:58
*** vipul|away is now known as vipul18:59
*** cp16net|away is now known as cp16net19:03
*** dhellmann has quit IRC19:04
*** lloydde has quit IRC19:05
*** boris-42 has joined #openstack-meeting19:05
*** dhellmann has joined #openstack-meeting19:05
*** jsavak has joined #openstack-meeting19:05
*** woodspa has quit IRC19:08
*** markvan has joined #openstack-meeting19:08
*** joesavak has quit IRC19:08
*** johnthetubaguy has joined #openstack-meeting19:09
*** salv-orlando has joined #openstack-meeting19:10
*** eglynn_ has quit IRC19:12
*** matiu has joined #openstack-meeting19:13
*** vipul is now known as vipul|away19:21
*** jaypipes has quit IRC19:25
*** lloydde has joined #openstack-meeting19:25
*** jaypipes has joined #openstack-meeting19:31
*** SergeyLukjanov has quit IRC19:33
*** SergeyLukjanov has joined #openstack-meeting19:34
*** sandywalsh has quit IRC19:37
*** salv-orlando has quit IRC19:38
*** ttrifonov is now known as ttrifonov_zZzz19:44
*** ewindisch has quit IRC19:47
*** ewindisch has joined #openstack-meeting19:47
*** torandu has quit IRC19:48
*** sandywalsh has joined #openstack-meeting19:49
*** otherwiseguy has quit IRC19:55
*** almaisan` is now known as al-maisan19:55
*** ttrifonov_zZzz is now known as ttrifonov19:56
dansmithvishy: you drivin' this bus?20:01
*** mattray has quit IRC20:01
*** esker has joined #openstack-meeting20:02
*** esker has joined #openstack-meeting20:03
*** noslzzp has quit IRC20:03
*** markvan_ has joined #openstack-meeting20:03
*** markvan has quit IRC20:03
*** johnthetubaguy has quit IRC20:03
*** markvan_ is now known as markvan20:04
*** alexpilotti has joined #openstack-meeting20:04
*** mrodden1 has quit IRC20:04
sdaguedansmith: you are off by an hour :)20:05
dansmithwhat?20:06
dansmithmy enterprise-class PIM software says it's now20:06
krtaylorhehheh20:06
dansmithI really don't understand why it's so damn stupid about timezone crap.. it clearly shows 2100UTC in the details bit20:07
dansmithsigh20:07
*** dwcramer has quit IRC20:07
*** mrodden has joined #openstack-meeting20:08
*** dprince has quit IRC20:08
*** al-maisan is now known as almaisan-away20:09
*** noslzzp has joined #openstack-meeting20:15
*** cp16net is now known as cp16net|away20:16
*** alexpilotti has quit IRC20:16
*** MarkAtwood has quit IRC20:21
*** dwcramer has joined #openstack-meeting20:23
*** pcm___ has quit IRC20:26
*** markmcclain has joined #openstack-meeting20:26
*** arosen has quit IRC20:29
*** arosen has joined #openstack-meeting20:30
*** novas0x2a|laptop has quit IRC20:31
*** reed has quit IRC20:35
*** vipul|away is now known as vipul20:36
*** novas0x2a|laptop has joined #openstack-meeting20:38
*** vipul is now known as vipul|away20:38
*** vipul|away is now known as vipul20:38
*** SergeyLukjanov has quit IRC20:39
*** SergeyLukjanov has joined #openstack-meeting20:40
*** stevemar has quit IRC20:41
*** otherwiseguy has joined #openstack-meeting20:42
*** eglynn_ has joined #openstack-meeting20:44
*** dwcramer has quit IRC20:53
*** esdaniel-away has quit IRC20:55
*** patelna__ has joined #openstack-meeting20:56
*** patelna_ has quit IRC20:59
vishy#startmeeting nova20:59
openstackMeeting started Thu Apr  4 20:59:58 2013 UTC.  The chair is vishy. Information about MeetBot at http://wiki.debian.org/MeetBot.20:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova)"21:00
openstackThe meeting name has been set to 'nova'21:00
vishyoh hai!21:00
mikalDoh!21:00
mikalI wanted to do that!21:00
devananda\o21:00
vishy#chair mikal21:00
boris-42HI21:00
mikalHeh21:00
cyeohhi!21:00
openstackCurrent chairs: mikal vishy21:00
dansmitho/21:00
mikal#link https://wiki.openstack.org/wiki/Meetings/Nova21:00
*** markvan has quit IRC21:00
alaskihi21:00
*** mrodden has quit IRC21:00
mikal#chair russellb21:00
openstackWarning: Nick not in channel: russellb21:00
openstackCurrent chairs: mikal russellb vishy21:00
vishyhe's on vacation :)21:00
mikalI know... russellb asked me to run this meeting because he's currently taking a vacation in an Olive Garden or something. I think his goal is to finish the salad.21:01
mikalBut I am also happy with vishy running it if he wants.21:01
sdagueheh21:01
vishyel oh el21:01
mikalSo, I think this will be relatively short... First agenda item...21:01
mikal#topic backport bug review21:01
*** openstack changes topic to "backport bug review (Meeting topic: nova)"21:01
mikalSo, the only bug I am aware of that we should backport is https://bugs.launchpad.net/nova/+bug/116366021:01
uvirtbotLaunchpad bug 1163660 in nova "nova-manage uses nova.db.fixed_ip_get_all_by_instance_host, which no longer exists" [Medium,In progress]21:01
mikalAny others?21:02
mikalHillariously, that's been broken for over a year.21:02
vishythere are more21:02
vishynote the critical: https://bugs.launchpad.net/nova/+bugs?field.tag=grizzly-backport-potential21:02
vishyand the high21:02
vishythe nova-manage fixed list i think isn't too bad21:03
mikalOh, its not as bad as I first thought it was21:03
vishybut not being able to use memcached is pretty bad21:03
mikalIts embarrassing though21:03
*** masayukig has quit IRC21:03
* mikal is waiting for LP to load that page21:03
dansmiththat's a lot of things to backport21:03
dansmithhow does that compare to folsom?21:03
mikalHalf are "fix committed" at least21:04
*** ijw has quit IRC21:04
mikaldansmith: I'm not sure, I don't remember that far back21:05
ttxwe always had embarrassing bugs showing their heads on release +1h21:05
*** ijw has joined #openstack-meeting21:05
krtayloryeah, there isnt a folsom-backport-potential21:05
mikalSo, it seems we should at least try and get them all assigned to people who are actually working on them...21:05
dansmithso, I guess we don't have one for the system_metadata concern,21:05
dansmithbut is anyone else in a panic over that?21:06
mikalWant to provide more detail?21:06
vishythere is also this: https://review.openstack.org/#/c/26109/21:06
vishyfolsom has has many hundreds of backports21:06
dansmithmikal: apparently comstud is severely concerned about performance related to the system_metadata "explosion"21:07
dansmithvishy: ah, good to know, I've never looked21:07
mikaldansmith: ahhh yeah, that blew up yesterday21:07
dansmithmikal: yeah :/21:07
mikaldansmith: this review looks like it fixes that?21:07
dansmithmikal: this review?21:07
dansmithmikal: you mean 26109? no.. :)21:08
dansmithmikal: it relieves one pressure point that was easy :)21:08
mikalcomstud: you around?21:08
dansmithhe's on a plane21:08
mikaldansmith: hmmm, ok21:08
*** woodspa has joined #openstack-meeting21:09
mikalOk, so it sounds like that needs more work then21:09
dansmithwe've got a few plans for mitigation, but yeah21:09
vishyyeah joining all of the metadata at once is bad21:09
mikalThere are also three bugs in that grizzly-backport-potential list with no assignee21:09
vishyhonestly we should have stuck of the flavor related metadata into one field21:09
vishythen we could have joined it all at once21:10
vishysigh21:10
dansmithvishy: could still do that, but aren't those columns limited to 255 chars?21:10
vishydansmith: yeah we'd have to migrate them to text21:10
dansmithvishy: yeah21:10
*** cp16net|away is now known as cp16net21:10
mikalvishy: I wonder how big those tables are in deploys...21:11
dansmithvishy: well, that's doable since everything is calling the instance_type_extract() to get at it21:11
*** mrodden has joined #openstack-meeting21:11
vishywe could make it join on system_metadata where key = instance_type21:11
dansmithso, that helps because we have fewer things in system_metadata for each instance,21:11
dansmithbut we're still going to be joining the whole thing right?21:11
dansmithoh, we can do that?21:12
vishybut then we have to figure out where all of the other system metadata is being used21:12
vishyand explicitly join it when we need it21:12
dansmithyeah21:12
mikaldansmith: so, this sure sounds like it should have a bug filed if one doesn't already exist21:12
dansmithmikal: yeah, I don't know that comstud doesn't have one, he's usually quick on that21:12
dansmithlooks like not though21:13
* mikal asks his coworkers21:13
*** diogogmt has quit IRC21:14
dansmithso, one thought we had,21:14
dansmithwas to avoid the join entirely,21:14
dansmithand just do another query for the system_metadata items we care about21:14
dansmithwhich we can do in bulk after we get all the instances that we're going after in a given query21:14
dansmiththe thought being that two trips to the db is better than the massive join21:15
dansmithso if that makes a significant improvement, that might be better than trying to do something more invasive21:15
vishydansmith: i'm not convinced that will be faster but it is worth a shot21:15
devanandadansmith: if that means only pulling the metadata a) when it's actually needed, and b) which is desired, not all of it, then I think it'll be big21:16
dansmithvishy: yeah21:16
mikalIsn't that table lacking indexes to make that not suck?21:16
dansmithdevananda: unfortunately, it doesn't mean either of those things necessarily21:16
dansmithmikal: no, apparently the indexes are the only reason it doesn't kill kittens already21:16
*** MarkAtwood has joined #openstack-meeting21:17
mikalI can see an index on instance_uuid, but not key?21:17
dansmithmikal: we don't need a key, right?21:17
devanandaprobably not, since afaik nothing currently fetches only a single key21:17
dansmithmikal: since we're joining only on uuid and taking everything21:17
dansmithright21:17
devanandawe will want an index though :)21:17
mikaldansmith: well, if you're going to cherry pick out specific keys to avoid a full join...21:17
dansmithmikal: that's not what we're talking about in this step21:18
vishydevananda: is there some way to optimize the join so that we don't get quite so many rows back?21:18
devanandaso the eventual query would be WHERE (uuid=X and key in(...)) OR (uuid=Y and key in (...)) ...21:18
vishyfor examle with 24 metadata items we get 24 copies of each instance right?21:18
dansmithright, but we need all of those,21:18
devanandahrmm21:18
dansmithsince we don't know if the caller is going to use system_metadata or not21:19
vishywell we need all of the rows, but we don't need all of the instance data in every row21:19
devanandavishy: i hadn't considered the code was doing that21:19
vishynot sure if it would make any difference21:19
devanandabut you may be right. that'll be a huge waste of network traffic but not necessarily nmake the join any slower21:19
dansmithso, comstud said that it wasn't pegging cpu or anything, just generating a crapton of network traffic,21:19
*** dripton__ is now known as dripton21:19
dansmithso I think that the problem _is_ the extra data, I just can't see how a join would not generate the full result on each row21:19
devanandaif the caller needs 4 pieces of metadata but fetches 20, that slows down the query cause the db has to do 5x more work21:20
*** ryanpetrello has quit IRC21:20
mikalThe resource tracker does know what metadata items it needs, right?21:20
mikalSo it could provide that as a hint to the lookup21:20
devanandaif, otoh, the db returned only those 4 pieces of metadata -- but each ROW also had an identical copy of the instance data -- then it slows down the network and, possibly, python -- but not th DB21:20
dansmithmikal: in a few cases we could micro-optimize, yeah,21:20
mikaldansmith: well, the resource tracker is what is punching comstud in the face21:21
dansmithmikal: but it's hard for things like compute manager where it's going to pass the instance to a bunch of random things21:21
mikaldansmith: its the painful case21:21
dansmithmikal: no, I think that the other patch made that better.. he said the periodic task was the killer now, I thought21:21
mikaldansmith: ahhh, ok21:22
vishyi think the right solution here is to convert metadata and system_metadata into a json blob21:22
vishyunless there are places we are filtering on it21:22
mikalvishy: do you seeing that being backported to grizzly?21:22
dansmithwhat's the impact of the text column?21:22
vishyin which case we should just convert parts of metadata (like flavor info) to blobs21:22
dansmithvishy: that's a helluva migration too, right?21:22
devanandajust to take a step back, where exactly is the performance problem right now?21:22
vishydansmith: negligible afaik21:22
dansmithdevananda: network traffic out of the db server, I believe21:23
vishydevananda: when you have large numbers of instances the joins makes the data transfer crazy21:23
dansmithdevananda: we really should have comstud here21:23
*** rmohan has quit IRC21:23
devanandamoving from a k/v table to using a json blob (one row per uuid) is a dramatic change on db behavior21:23
vishylike 10000 rows turns into 12000021:23
devanandavishy: ok. so in that case, is the issue network traffic or DB time for the JOIN ?21:23
mikaldevananda: I believe comstud's problem was network traffic21:24
vishynetwork traffic + unpacking time21:24
dansmithcomstud made it sound like traffic21:24
dansmithyeah21:24
devanandahas someone separated those by timing the first packet and the last packet of mysql's response?21:24
devanandaok21:24
vishysqlalchemy processing 120000 rows is pretty damn slow as well21:24
devanandaso then change the JOIN to a subquery + CONCAT21:24
devanandaor use an in-memory pivot table21:24
devanandato return only 1 row per instance21:24
vishydevananda: do you have any idea how to do either of those in sqlalchemy?21:25
devanandafrom python's POV, it has the same effect as going to json but doesn't require any db migration21:25
devanandavishy: no clue in sqla ...21:25
vishydevananda: that would be sweet21:25
devanandaboris-42: any thoughts on ^ ?21:25
dansmiththat sounds nice (no migration)21:25
*** rmohan has joined #openstack-meeting21:25
* dansmith pretends he understands what devananda said21:25
*** belliott has joined #openstack-meeting21:25
vishybasically we want to add an extra field to instances that does a subquery on metadata items and sticks them all into a single field.21:26
devanandadansmith: http://stackoverflow.com/questions/4555988/sql-server-pivot-on-key-value-table (first hit on google, haven't read it...)21:26
devanandabut the question there shows an exaple of our problem21:26
vishydevananda: actually we could just add a prefix to the fields right?21:27
devanandaand what a pivot does21:27
devanandavishy: i'm not sure why we'd do that21:27
vishymetadata_key1, metadata_key2 etc.21:27
dansmithdevananda: that looks excellent :)21:27
devanandavishy: ah. yes21:27
devanandavishy: all columns in table 1 + (prefix+key) for all columns in table 221:28
dansmithwe already have a prefix on the type keys, do we need more?21:28
*** topol has quit IRC21:28
devanandavishy: another approach is to use GROUP_CONCAT to return all the key/value pairs in a single text field21:28
devanandaeg, "key1:val1,key2:val2"21:29
vishydevananda: so you concat them with a , and hope none of the vals have a , in them?21:29
devanandaas long as we have separators which are guaranteed not to be present in either key or value ;)21:29
vishyyeah thats the part i'm worried about :)21:29
dansmithdevananda: so is this going to be significantly better than two queries?21:29
dansmithI mean, a little more latency, but is it actually faster for some reason?21:29
vishyhttps://github.com/tomasd/pandas-sqlalchemy-pivot21:30
dansmithbecause I haven't seen anyone speak in SQLA terms yet21:30
devanandadansmith: probably not faster, no.21:30
dansmithokay21:31
dansmithvishy: do I take the README on that project to mean that SQLA can't do this itself?21:31
vishydansmith: so you are saying that we convert all of the instance gets to do a separate query for metadata and shove it in?21:31
devanandadb still has to do the same work to get the entries from system_metadata. returning (uuid,key,val) 10M times or returning (uuid, other fields, concat of keys and values) 100k times... the total byte count will be similar.21:32
dansmithvishy: that's what we want to try, yeah21:32
vishydansmith: i guess that avoids copying the extra data from each row21:32
dansmithvishy: the only problem I have right now is that the Instance SQLA object doesn't want me fscking with its field,21:32
dansmithso I have to do some dirty work to convert it to a dict21:32
dansmithwhich is ugly, and maybe a showstopper, but it works for testing at least21:33
vishydansmith: we already do some similar mucking21:33
vishyfor aggregates21:33
dansmithokay then :)21:33
vishyiirc21:33
dansmithhttps://review.openstack.org/#/c/26136/21:33
*** markvan has joined #openstack-meeting21:33
dansmiththat's just a quick hack to test with, but it appears to pass tests21:33
vishydansmith: dict(inst.iteritems())21:34
vishybtw21:34
dansmithah, okay21:34
*** mtreinish has quit IRC21:34
*** eglynn_ has quit IRC21:34
vishylets get comstud to test taht when he gets off the plane21:34
vishyi think we need a bug report as well21:34
dansmithvishy: yeah21:35
dansmithwell, sorry for dominating the meeting,21:36
mikalHeh21:36
dansmithbut excellent discussion, IMHO :)21:36
vishyno it is important21:36
mikalIt was worthwhile21:36
vishyi will mark the bug critical21:36
vishyand we can get it into stable/grizzly next week21:36
mikalDid we actually find a bug?21:36
dansmithmikal: I didn't see one21:36
mikal(in LP I mean)21:36
vishywe have enough bugs to warrant a quick grizzly.1 i think21:36
vishymikal: can someone report it?21:37
dansmithI can21:37
mikalOk cool21:37
dansmith(I have that ability)21:37
mikalOk, so what about https://bugs.launchpad.net/nova/+bug/1164072 -- is on the backport list but doesn't have an assignee21:37
uvirtbotLaunchpad bug 1164072 in nova "libvirt livemigration warning logger refernces a not defined local varaible" [Medium,Triaged]21:37
mikalStupid locals()21:38
*** patelna_ has joined #openstack-meeting21:38
*** bru has quit IRC21:38
dansmithhttps://bugs.launchpad.net/nova/+bug/116473721:39
uvirtbotLaunchpad bug 1164737 in nova "Instance joins with system_metadata are critically slow" [Critical,Confirmed]21:39
mikalActually, I'll take 116407221:39
boris-42Btw I know probably it is offtop but could we speak little bit about this bp https://blueprints.launchpad.net/nova/+spec/use-db-time21:39
mikalThere are a few things wrong with that log message.21:39
boris-42I have some questions..21:39
mikalboris-42: can we do that in "open discussion"?21:39
vishyyeah that one is super easy :)21:40
mikalThe other unassigned one is https://bugs.launchpad.net/nova/+bug/116044221:40
uvirtbotLaunchpad bug 1160442 in quantum "when boot many vms with quantum, nova sometimes allocates two quantum ports rather than one" [Undecided,Incomplete]21:40
boris-42mikal ok21:40
devanandamikal: is that a race condition in db? (just guessing, still reading)21:40
mikaldevananda: no idea. I'm trying to trick someone into digging into it...21:41
* devananda hides21:41
mikalNo takers?21:42
*** patelna_ has quit IRC21:42
*** patelna__ has quit IRC21:42
*** hemna has quit IRC21:42
*** hemna has joined #openstack-meeting21:42
*** patelna_ has joined #openstack-meeting21:42
mikalFair enough21:43
vishymikal: arosen might be good for that one21:43
mikalvishy: ok, I will ping him21:43
mikalUnless he's here...21:43
vishyi just did in nova21:43
mikalCool21:43
mikalIs there anything else we should discuss backport wise?21:43
vishymikal: I'm going to discuss doing a quick .1 with the stable-backports folks21:44
*** radez_g0n3 is now known as radez21:44
mikalvishy: ok. Do you want to issue a deadline for people to try and get their fixes in to make that release?21:44
*** ryanpetrello has joined #openstack-meeting21:44
vishyif we do it it will probably just be a quick version of all the really important ones21:45
vishyhigh + critical21:45
mikalOk, cool21:45
vishybut i need to discuss with markmc + other stable team to be sure21:45
mikalFair enough21:45
*** radez is now known as radez_g0n321:45
mikalWe're ok to move on to the next topic?21:45
vishyit would be great if everyone could help stay on top of the bug queue21:45
vishyi knocked out about 15 today21:46
vishybut there are still a few left21:46
vishyaddressing bugs quickly right after release is really important21:46
mikalYeah, I see 26 bugs needing triage as well21:46
vishybecause a lot of people don't try the rcs21:46
vishymikal: refresh, its only 1221:46
vishy:)21:46
mikalAhhh, I think we're counting differently. I'm including incomplete bugs as untriaged.21:47
vishyoh gotcha21:47
vishyi set bugs back to incomplete if i need more info from the reporter21:47
mikalYeah, that's fine. I think that's you doing the right thing.21:47
mikalI do the same21:47
mikalBut in my mind its still a bug we need to categorize, even if we're waiting for someone21:48
mikalOtherwise if they never reply it sits around forever21:48
mikalWe really should move on...21:48
mikal#topic design summit21:48
*** openstack changes topic to "design summit (Meeting topic: nova)"21:48
mikalIIRC russellb has now let people know about session acceptance21:49
mikalHmmm, there are still a fair few marked as "unreviewed" though21:49
mikalDoes anyone have anything they want to say about the summit?21:50
mikalMoving on then21:51
mikal#topic open discussion21:51
*** openstack changes topic to "open discussion (Meeting topic: nova)"21:51
mikalboris-42: now is your time to shine...21:51
boris-42mikal thanks21:51
mikalSo, reading that blueprint...21:52
mikaltimeutils.utcnow() is super useful for unit testing21:52
boris-42So we discussed that using local time on nodes is bad idea..21:52
mikalI'd expect a bunch of unit tests to need work if we removed it and used DB time21:52
devanandaindeed21:52
vishyboris-42: that seems like a huge amount of work for very little benefit21:52
boris-42vishy it seems only =)21:53
devanandait's a pretty common problem in distributed systems21:53
vishyboris-42: it seems like a lot of places we use utcnow we are not actually needing to compare against db objects21:53
devanandaif the clock gets out of sync somewhere, all kinds of issues crop up21:54
beaglesdevanada: +121:54
devanandaeg, if one compute host's ntpd dies and it drifts, pretty soon it may appear "dead" to the scheduler21:54
boris-42Yes but there is also a lot of places where we are comparing21:54
boris-42I have problems with only 70 nodes =)21:54
*** ryanpetrello has quit IRC21:54
beaglesjust about any  middleware "environment" ends up with some concept of system time (OMG Time Service, etc)21:54
devanandabecause the compute host is writing it's localtime to the db updated_at value, which the scheduler compares to it's localtime21:55
boris-42So the idea is pretty simple to add methods in db and conductor21:55
boris-42and use it instead of timeutils.utcnow()21:55
vishyi'm just worried about adding a whole bunch of unneded db calls21:55
*** jkyle has quit IRC21:55
boris-42They are pretty simple for DB21:55
mikalI wonder how much extra load it will be on conductor as well?21:55
devanandaif done right, i don't think it'll result in more db calls at all21:55
vishyi guess we could specifically split out system_time and local_time21:55
mikalDo we know how often we ask for the time?21:55
devanandait's only a matter of when something writes a timestamp TO the db that the problem occurs21:56
devanandaer, correcting myself. that's half21:56
vishywe use it for caching and things as well21:56
devanandathe other half is when somethig reads a time from the DB and compares to local time. but again, it can ask the DB for its time21:56
*** jkyle has joined #openstack-meeting21:56
devanandaah, hrm21:57
vishythere are a lot of places that this will not scale21:57
vishymaking a db call every time we need to check if a cache item is valid is rediculous21:57
vishyso we will need two versions of time21:57
vishyone where we just need a locally consistent time21:58
vishyand one where we need a globally consistent time21:58
boris-42vishy +121:58
devananda++21:58
mikalSo, what about a periodic task which checks db time against system time?21:58
dripton++, but while we're changing everything, we should always use UTC rather than local.21:58
mikalEvery ten minutes or something21:58
vishydevananda: any idea about db systems that have master/master21:58
*** lbragstad has quit IRC21:59
vishydripton: sorry i don't mean local as in timezone local21:59
devanandamikal: of what benefit is that?21:59
vishyi mean local as in local to this machine21:59
vishystill in utc time21:59
devanandavishy: when there are >1 DB at play (whethe rmaster,master or galera or ..) it's extra important for their clocks to be in sync21:59
mikaldevananda: well, we could at least log that we've detected an error condition. It would help with diagnosis from an operator.21:59
devanandavishy: in my former db consulting hat, i saw lots of issues creep up from that21:59
*** eharney has quit IRC21:59
vishyfor example this: https://github.com/openstack/nova/blob/master/nova/openstack/common/memorycache.py#L6221:59
vishyshould never talk to the db22:00
*** ayoung has quit IRC22:00
vishydevananda: ok so we are assuming that keeping the db clocks in sync is easier than keeping all of the nodes in sync?22:00
*** zyluo has quit IRC22:00
*** flaper87 has quit IRC22:00
devanandamikal: if there is a clear separation between things that need to track distributed-time and things that need to track local/relative-time, then i don't think such a check would be meaningful22:00
dansmithI'm skeptical of anything where we have to consult the db for the current time,22:01
devanandavishy: yes. there are probably a lot less db's than nova nodes, and a lot more attention should be spent on them :)22:01
mikaldevananda: well, I'm thinking of ways to avoid asking the db for the time all over the place22:01
vishydevananda: I buy that22:01
*** sacharya has joined #openstack-meeting22:01
devanandai dont see this as "ask the db for the time"22:01
vishydevananda: i just want to make sure we aren't limiting db choices by forcing the db to handle global time for us22:01
*** dwcramer has joined #openstack-meeting22:02
vishywe could instead do something like use the nova-conductor time for everything but a lot of the time comparisons are against db objects so we do get some performance benefits by doing it concurrently with db requests22:02
*** lglenden has quit IRC22:02
mikalGiven we're now over time, do we want to discuss this at the summit?22:03
vishysure22:03
beaglesis there value in having an openstack system time that has a source from "somewhere"... start there, maybe have it initialized and periodically verified from whatever source?22:03
vishyI'm still not convinced that running a robust ntp solution isn't easier22:03
vishybeagles: that is ntp22:03
vishybut yeah we are out of time22:03
vishysummit discussion!22:04
beaglesvishy: :) of course it could grab it from there ;)22:04
vishy#endmeeting22:04
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:04
openstackMeeting ended Thu Apr  4 22:04:17 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-04-04-20.59.html22:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-04-04-20.59.txt22:04
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-04-04-20.59.log.html22:04
mikalThanks people22:04
vishythanks mikal!22:04
*** patelna_ has quit IRC22:04
boris-42thanks22:04
boris-42=)22:04
*** jsavak has quit IRC22:04
mikal:)22:04
*** ewindisch has quit IRC22:05
devanandao/22:05
*** dwcramer has quit IRC22:08
*** ewindisch has joined #openstack-meeting22:08
*** beagles has quit IRC22:08
*** patelna_ has joined #openstack-meeting22:09
*** mrodden has quit IRC22:13
*** masayukig has joined #openstack-meeting22:13
*** masayukig has quit IRC22:18
*** fnaval has quit IRC22:19
*** topol has joined #openstack-meeting22:21
*** Gordonz has quit IRC22:24
*** Gordonz has joined #openstack-meeting22:25
*** beagles has joined #openstack-meeting22:25
*** ogelbukh has quit IRC22:25
*** ewindisch has quit IRC22:26
*** digitalsanctum has joined #openstack-meeting22:26
*** mrodden has joined #openstack-meeting22:31
*** reed has joined #openstack-meeting22:32
*** dprince has joined #openstack-meeting22:35
*** Gordonz has quit IRC22:37
*** ewindisch has joined #openstack-meeting22:40
*** Kharec has quit IRC22:45
*** noslzzp has quit IRC22:46
*** cody-somerville has quit IRC22:52
*** ewindisch has quit IRC22:54
*** ryanpetrello has joined #openstack-meeting22:57
*** boris-42 has quit IRC23:02
*** sdake_ has quit IRC23:03
*** sdake_ has joined #openstack-meeting23:03
*** diogogmt has joined #openstack-meeting23:03
*** ewindisch has joined #openstack-meeting23:04
*** ryanpetrello has quit IRC23:05
*** jaypipes has quit IRC23:05
*** boris-42 has joined #openstack-meeting23:06
*** markmcclain has quit IRC23:07
*** otherwiseguy has quit IRC23:13
*** mrodden has quit IRC23:16
*** sandywalsh has quit IRC23:17
*** gongysh_ has joined #openstack-meeting23:25
*** diogogmt has quit IRC23:26
*** topol has quit IRC23:26
*** noslzzp has joined #openstack-meeting23:27
*** dprince has quit IRC23:28
*** Kharec has joined #openstack-meeting23:29
*** lloydde has quit IRC23:32
*** sandywalsh has joined #openstack-meeting23:32
*** lloydde has joined #openstack-meeting23:33
*** boris-42 has quit IRC23:36
*** fifieldt has quit IRC23:38
*** markwash has quit IRC23:47
*** ewindisch has quit IRC23:49
*** rmohan has quit IRC23:50
*** rmohan has joined #openstack-meeting23:51
*** MarkAtwood has quit IRC23:53
*** HenryG_ has joined #openstack-meeting23:53
*** otherwiseguy has joined #openstack-meeting23:53
*** patelna_ has quit IRC23:54
*** HenryG has quit IRC23:56
*** rmohan has quit IRC23:57
*** rmohan has joined #openstack-meeting23:57
*** sandywalsh has quit IRC23:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!