Wednesday, 2014-12-03

*** baoli has quit IRC00:00
*** dconde has quit IRC00:05
*** etoews has quit IRC00:08
*** tomoe_ has joined #openstack-meeting-300:08
*** david-lyle is now known as david-lyle_afk00:08
*** mwagner_lap has joined #openstack-meeting-300:09
*** Sukhdev has joined #openstack-meeting-300:10
*** ivar-laz_ has joined #openstack-meeting-300:11
*** xuhanp has joined #openstack-meeting-300:13
*** tomoe_ has quit IRC00:13
*** ivar-lazzaro has quit IRC00:14
*** tomoe_ has joined #openstack-meeting-300:14
*** safchain has quit IRC00:14
*** MarkAtwood has quit IRC00:15
*** MarkAtwood has joined #openstack-meeting-300:16
*** natarajk has left #openstack-meeting-300:18
*** jemangs has quit IRC00:25
*** jemangs_ has joined #openstack-meeting-300:25
*** Piet has quit IRC00:26
*** emagana_ has quit IRC00:32
*** hurgleburgler has quit IRC00:32
*** etoews has joined #openstack-meeting-300:34
*** pballand has joined #openstack-meeting-300:35
*** yamamoto has joined #openstack-meeting-300:36
*** xuhanp has quit IRC00:38
*** yamamoto has quit IRC00:40
*** sandr8_ has joined #openstack-meeting-300:42
*** sandr8 has quit IRC00:44
*** pballand has quit IRC00:58
*** pballand has joined #openstack-meeting-300:59
*** pballand has quit IRC01:02
*** emagana has joined #openstack-meeting-301:03
*** hinnant has quit IRC01:06
*** emagana has quit IRC01:08
*** etoews has quit IRC01:08
*** Sukhdev has quit IRC01:09
*** baoli has joined #openstack-meeting-301:15
*** yamamoto_ has joined #openstack-meeting-301:18
*** dconde has joined #openstack-meeting-301:20
*** dconde has quit IRC01:21
*** emagana has joined #openstack-meeting-301:23
*** dboik has joined #openstack-meeting-301:24
*** Longgeek has joined #openstack-meeting-301:25
*** dboik_ has joined #openstack-meeting-301:27
*** dboik has quit IRC01:29
*** Longgeek has quit IRC01:30
*** stanzgy has joined #openstack-meeting-301:39
*** markmcclain has quit IRC01:39
*** jaypipes has quit IRC01:39
*** lhcheng_ has joined #openstack-meeting-301:40
*** lhcheng has quit IRC01:43
*** nelsnelson has quit IRC01:43
*** yamamoto_ has quit IRC01:47
*** emagana has quit IRC01:48
*** emagana has joined #openstack-meeting-301:48
*** emagana has quit IRC01:52
*** emagana_ has joined #openstack-meeting-301:52
*** emagana_ has quit IRC01:57
*** sarob has quit IRC01:59
*** clu_ has quit IRC02:01
*** etoews has joined #openstack-meeting-302:04
*** sigmavirus24 is now known as sigmavirus24_awa02:12
*** bpokorny has joined #openstack-meeting-302:12
*** yamamoto_ has joined #openstack-meeting-302:14
*** alexsyip has quit IRC02:19
*** etoews has quit IRC02:38
*** s3wong has quit IRC02:42
*** etoews has joined #openstack-meeting-302:51
*** sigmavirus24_awa is now known as sigmavirus2402:52
*** salv-orlando has quit IRC02:53
*** etoews has quit IRC03:00
*** shwetaap has joined #openstack-meeting-303:01
*** ivar-laz_ has quit IRC03:03
*** ivar-lazzaro has joined #openstack-meeting-303:04
*** seizadi has joined #openstack-meeting-303:07
*** seizadi has quit IRC03:08
*** dboik_ has quit IRC03:08
*** seizadi has joined #openstack-meeting-303:08
*** ivar-lazzaro has quit IRC03:09
*** Longgeek has joined #openstack-meeting-303:14
*** dboik has joined #openstack-meeting-303:18
*** Longgeek has quit IRC03:19
*** sunrenjie has joined #openstack-meeting-303:21
*** rzang has joined #openstack-meeting-303:21
*** ivar-lazzaro has joined #openstack-meeting-303:24
*** vkmc has quit IRC03:26
*** ivar-lazzaro has quit IRC03:26
*** ivar-lazzaro has joined #openstack-meeting-303:27
*** Sukhdev has joined #openstack-meeting-303:30
*** david-ly_ has joined #openstack-meeting-303:32
*** david-lyle_afk has quit IRC03:33
*** rzang_ has joined #openstack-meeting-303:33
*** etoews has joined #openstack-meeting-303:34
*** rzang_ has quit IRC03:35
*** etoews has quit IRC03:39
*** rzang has quit IRC03:41
*** ivar-laz_ has joined #openstack-meeting-303:41
*** ivar-lazzaro has quit IRC03:45
*** ivar-laz_ has quit IRC03:46
*** jaypipes has joined #openstack-meeting-303:48
*** bpokorny has quit IRC03:48
*** bpokorny has joined #openstack-meeting-303:49
*** dboik has quit IRC03:57
*** seizadi has quit IRC04:04
*** etoews has joined #openstack-meeting-304:35
*** MaxV has joined #openstack-meeting-304:39
*** etoews has quit IRC04:40
*** lhcheng_ has quit IRC04:46
*** bobmel has quit IRC04:46
*** sunrenjie has quit IRC04:46
*** david-ly_ has quit IRC04:48
*** david-lyle_afk has joined #openstack-meeting-304:49
*** carl_baldwin has joined #openstack-meeting-304:51
*** sunrenjie has joined #openstack-meeting-304:53
*** amotoki has joined #openstack-meeting-304:53
*** sunrenjie has quit IRC04:56
*** sunrenjie has joined #openstack-meeting-304:57
*** sunrenjie has quit IRC04:59
*** sunrenjie has joined #openstack-meeting-305:01
*** lhcheng has joined #openstack-meeting-305:02
*** Longgeek has joined #openstack-meeting-305:03
*** Guest79999 has quit IRC05:04
*** sunrenjie has quit IRC05:06
*** sunrenjie has joined #openstack-meeting-305:07
*** Longgeek has quit IRC05:08
*** sunrenjie has quit IRC05:10
*** alexiz has quit IRC05:15
*** sigmavirus24 is now known as sigmavirus24_awa05:15
*** jacalcat1 has left #openstack-meeting-305:15
*** sunrenjie has joined #openstack-meeting-305:16
*** Sukhdev has quit IRC05:29
*** marun has quit IRC05:30
*** Longgeek has joined #openstack-meeting-305:33
*** sarob has joined #openstack-meeting-305:36
*** evgenyf has joined #openstack-meeting-305:41
*** seizadi has joined #openstack-meeting-305:42
*** Sukhdev has joined #openstack-meeting-305:50
*** sarob has quit IRC06:02
*** jpomero_ has joined #openstack-meeting-306:06
*** jpomero has quit IRC06:10
*** seizadi has quit IRC06:15
*** Ark has joined #openstack-meeting-306:15
*** Ark is now known as Guest1360806:15
*** Guest13608 has quit IRC06:19
*** Longgeek has quit IRC06:20
*** k4n0 has joined #openstack-meeting-306:20
*** carl_baldwin has quit IRC06:20
*** Longgeek has joined #openstack-meeting-306:22
*** carl_baldwin has joined #openstack-meeting-306:31
*** carl_baldwin has quit IRC06:33
*** etoews has joined #openstack-meeting-306:37
*** etoews has quit IRC06:41
*** Longgeek has quit IRC06:49
*** Longgeek has joined #openstack-meeting-307:02
*** MaxV has quit IRC07:02
*** wuhg has joined #openstack-meeting-307:13
*** david-ly_ has joined #openstack-meeting-307:15
*** david-lyle_afk has quit IRC07:16
*** lhcheng has quit IRC07:17
*** mrunge has joined #openstack-meeting-307:25
*** mrunge has quit IRC07:25
*** belmoreira has joined #openstack-meeting-307:28
*** dynarro has joined #openstack-meeting-307:30
*** mrunge has joined #openstack-meeting-307:33
*** bpokorny has quit IRC07:33
*** etoews has joined #openstack-meeting-307:37
*** etoews has quit IRC07:42
*** dynarro has quit IRC07:44
*** Sukhdev has quit IRC07:50
*** armax has quit IRC08:10
*** matrohon has joined #openstack-meeting-308:19
*** MaxV has joined #openstack-meeting-308:20
*** devvesa has joined #openstack-meeting-308:20
*** salv-orlando has joined #openstack-meeting-308:25
*** sergef has joined #openstack-meeting-308:28
*** Longgeek has quit IRC08:33
*** Longgeek has joined #openstack-meeting-308:34
*** jcoufal has joined #openstack-meeting-308:38
*** etoews has joined #openstack-meeting-308:38
*** etoews has quit IRC08:42
*** jtomasek has joined #openstack-meeting-308:48
*** Longgeek has quit IRC08:49
*** safchain has joined #openstack-meeting-308:49
*** hareeshp has joined #openstack-meeting-308:51
*** iovadia has joined #openstack-meeting-308:52
*** Longgeek has joined #openstack-meeting-308:53
*** iovadia has quit IRC08:56
*** stanzgy_ has joined #openstack-meeting-309:02
*** sarob has joined #openstack-meeting-309:03
*** stanzgy has quit IRC09:05
*** sarob has quit IRC09:08
*** stanzgy_ has quit IRC09:08
*** iovadia has joined #openstack-meeting-309:12
*** aleksandr_null has quit IRC09:21
*** jcoufal has quit IRC09:40
*** yamamoto_ has quit IRC09:44
*** sergef has quit IRC09:51
*** sergef has joined #openstack-meeting-309:52
*** belmorei_ has joined #openstack-meeting-309:54
*** iovadia1 has joined #openstack-meeting-309:54
*** evgenyf has quit IRC09:55
*** iovadia2 has joined #openstack-meeting-309:56
*** belmoreira has quit IRC09:57
*** iovadia has quit IRC09:58
*** iovadia1 has quit IRC09:59
*** stanzgy has joined #openstack-meeting-310:00
*** stanzgy has quit IRC10:04
*** yamamoto_ has joined #openstack-meeting-310:11
*** alexpilotti has joined #openstack-meeting-310:12
*** Longgeek has quit IRC10:27
*** stanzgy has joined #openstack-meeting-310:29
*** Longgeek has joined #openstack-meeting-310:30
*** Longgeek has quit IRC10:35
*** belmorei_ has quit IRC10:39
*** Longgeek has joined #openstack-meeting-310:40
*** iovadia2 has quit IRC10:40
*** yamamoto_ has quit IRC10:41
*** shwetaap has quit IRC10:42
*** jcoufal has joined #openstack-meeting-310:42
*** Longgeek has quit IRC10:50
*** Longgeek has joined #openstack-meeting-310:52
*** iovadia has joined #openstack-meeting-310:54
*** belmoreira has joined #openstack-meeting-310:55
*** stanzgy has quit IRC10:56
*** k4n0 has quit IRC11:23
*** tomoe__ has joined #openstack-meeting-311:28
*** vkmc has joined #openstack-meeting-311:29
*** vkmc has quit IRC11:29
*** vkmc has joined #openstack-meeting-311:29
*** tomoe__ has quit IRC11:30
*** tomoe__ has joined #openstack-meeting-311:30
*** tomoe_ has quit IRC11:31
*** gholler has joined #openstack-meeting-311:32
*** yamahata has joined #openstack-meeting-311:38
*** yamamoto has joined #openstack-meeting-311:42
*** devvesa has quit IRC11:44
*** devvesa has joined #openstack-meeting-311:45
*** yamamoto has quit IRC11:47
*** beagles has quit IRC11:52
*** beagles has joined #openstack-meeting-311:53
*** yamahata has quit IRC11:57
*** julim has joined #openstack-meeting-312:18
*** Longgeek has quit IRC12:28
*** Longgeek has joined #openstack-meeting-312:30
*** shwetaap has joined #openstack-meeting-312:45
*** shwetaap has quit IRC13:00
*** jacalcat has joined #openstack-meeting-313:02
*** MaxV has quit IRC13:08
*** tomoe__ has quit IRC13:12
*** xuhanp has joined #openstack-meeting-313:17
*** mestery has quit IRC13:17
*** tomoe_ has joined #openstack-meeting-313:28
*** shwetaap has joined #openstack-meeting-313:32
*** jaypipes is now known as jaypipes-afk13:34
*** etoews has joined #openstack-meeting-313:47
*** markmcclain has joined #openstack-meeting-313:51
*** sigmavirus24_awa is now known as sigmavirus2413:54
*** jcoufal has quit IRC13:55
*** jcoufal has joined #openstack-meeting-313:56
*** thomasem has joined #openstack-meeting-313:58
*** thomasem has quit IRC13:58
*** thomasem has joined #openstack-meeting-313:59
*** dboik has joined #openstack-meeting-314:10
*** mestery has joined #openstack-meeting-314:10
*** dboik_ has joined #openstack-meeting-314:11
*** dboik has quit IRC14:15
*** dboik_ has quit IRC14:21
*** jacalcat has left #openstack-meeting-314:22
*** Longgeek has quit IRC14:29
*** etoews has quit IRC14:35
*** jpomero_ is now known as jpomero14:40
*** jaypipes-afk is now known as jaypipes14:41
*** dboik has joined #openstack-meeting-314:44
*** dboik has quit IRC14:45
*** dboik has joined #openstack-meeting-314:45
*** mestery has quit IRC14:46
*** Longgeek has joined #openstack-meeting-314:49
*** david-ly_ is now known as david-lyle15:00
salv-orlandoaloha?15:01
salv-orlandono meeting, no cry15:02
*** armax has joined #openstack-meeting-315:02
salv-orlandomeh meh meh15:02
*** uschreiber has joined #openstack-meeting-315:05
salv-orlandomeh meh meh I forgot yet another time that the meeting is at 1530UTC15:05
*** yamamoto has joined #openstack-meeting-315:10
*** mestery has joined #openstack-meeting-315:10
*** marun has joined #openstack-meeting-315:17
*** belmoreira has quit IRC15:20
*** pc_m has joined #openstack-meeting-315:21
*** MaxV has joined #openstack-meeting-315:23
*** jacalcat has joined #openstack-meeting-315:24
*** shwetaap has quit IRC15:25
*** shwetaap has joined #openstack-meeting-315:27
*** pc_m has left #openstack-meeting-315:28
*** shakamunyi has joined #openstack-meeting-315:29
*** shakamunyi has quit IRC15:29
mesteryhi15:29
mesterymarkmcclain armax amotoki salv-orlando: neutron-drivers meeting15:29
salv-orlandoaloha15:29
*** dboik_ has joined #openstack-meeting-315:29
armaxmestery: yo15:29
* mestery waits for a minute for amotoki and markmcclain to appear15:30
*** nelsnelson has joined #openstack-meeting-315:30
*** thangp has joined #openstack-meeting-315:30
*** wpward has joined #openstack-meeting-315:31
* armax thinks he has more time for more coffee15:31
*** etoews has joined #openstack-meeting-315:31
mesterylol15:31
armax:)15:31
mestery#startmeeting neutron-drivers15:31
openstackMeeting started Wed Dec  3 15:31:39 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.15:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:31
*** openstack changes topic to " (Meeting topic: neutron-drivers)"15:31
openstackThe meeting name has been set to 'neutron_drivers'15:31
mestery#link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers Agenda15:31
mesteryMostly today I wanted to highlight a few specs, and then more generally look at where we're at for approving specs.15:32
mesterySound good?15:32
mestery#topic Subnet API specs for Kilo15:32
*** openstack changes topic to "Subnet API specs for Kilo (Meeting topic: neutron-drivers)"15:32
mestery#link https://review.openstack.org/#/c/135771/15:32
mesterysalv-orlando: I think you've looked at this one a bit, along with myself.15:32
salv-orlandomestery: I did.15:32
armaxmestery: that’s next on my list15:32
mesterycarl_baldwin indicated he has an assignee for htis now, which is great!15:32
*** dboik has quit IRC15:33
mesteryI think we should work to get this into Kilo, salv-orlando, what do you think?15:33
salv-orlandomestery: we can but the priorities are a bit subtle15:33
salv-orlandowe need this partially implemented for doing pluggable IPAM15:33
salv-orlandoso it’s partially a requirement - at least according to the plan currentl laid out15:34
mesterysalv-orlando: Yes, I think it's a straightforward change as well, though it is an API change15:34
salv-orlandoThe full support for subnet pools, exposed through the API can then come after pluggable IPAM is introduced15:34
salv-orlandono API change is every straigthforward ;)15:34
mesteryMakes sense to me15:34
mesterylol15:34
salv-orlandobut the point is that for kilo we absolutely need that bit that allows us to do pluggable IPAM15:35
markmcclainhi… sorry call ran long15:35
salv-orlandoso I think it’s ok to approve.15:35
mesteryRight15:35
mesteryGood15:35
salv-orlandoonce of course we do all the nitpicking as usual15:35
mestery:)15:35
*** dboik_ has quit IRC15:35
salv-orlandowe love to nitpick after all, don’t we?15:35
*** etoews has quit IRC15:35
armaxsalv-orlando: give me the chance to review15:35
*** hareeshp has quit IRC15:35
mesteryarmax: Of course15:35
mesteryNext one15:35
mestery#link https://review.openstack.org/#/c/135453/15:35
*** dboik has joined #openstack-meeting-315:36
mesteryPaul Ward asked me to have us look at this one too15:36
mesteryAlong with carl_baldwin15:36
wpwardThanks for adding it, Kyle15:36
mesterywpward: Sure, happy to highlight it!15:36
mesterywpward: I have not reviewed this one yet, but will do so today15:36
*** thorst1 has joined #openstack-meeting-315:37
*** uschreiber has quit IRC15:37
mesteryLooks like salv-orlando has already reviewed15:37
mesterywpward: We'll look at this one and go forward from there.15:37
salv-orlandoI have reviewed the spec this morning. Carl did it as well. I have nothing against it, but on the other hand I am still wary of seeing new attributes popping up in core resources.15:37
salv-orlandoI will talk about this with carl_baldwin because it seems he had already plans for introducing a feature like this15:37
wpwardsalv-orlando: an understandable concern.... is there a different way to accomplish it?15:37
wpwardYes, Carl mentions a few BPs that are related.  This one is a smaller subset but would be a good start to get his going as well.15:38
salv-orlandowpward: subnet-level dhcp options, or we’ll talk to carl to see how it fits in the changes proposed for spec #13577115:38
salv-orlandoanyway, this is something we can keep discussing on the gerrit review page (also becase Carl is not here). So mestery, if you want to move to the next one I’m ok with it15:39
wpwardsalv-orlando: Ok.  I think one thing we want to maintain is the ability to do this for static networks as well, where dhcp is not in the picture.15:39
mesterysalv-orlando: Ack15:39
mestery#topic Blueprint Tracking15:39
*** openstack changes topic to "Blueprint Tracking (Meeting topic: neutron-drivers)"15:39
*** xuhanp has quit IRC15:39
*** zz_jgrimm is now known as jgrimm15:39
mestery#link https://review.openstack.org/#/c/136835/15:39
mesteryServices split15:40
mesteryI think it's very close15:40
mesteryAnd I had 3 new repositories created with infra yesterday as well15:40
mesterysalv-orlando markmcclain armax amotoki: What do you folks think?>15:40
mesteryI mean, we could keep nit picking it, but at some point I think we can call it baked.15:40
salv-orlandomestery: I think it needs a rewiew from armax at least!15:40
mesterylol15:40
armaxmestery: I had the same feeling15:40
mesteryarmax: OK, lets wait on this one.15:41
armaxsalv-orlando: I did15:41
salv-orlandoI’m pretty sure after his review it will be a lot farther from being ready15:41
markmcclainhaha15:41
mesteryWait, you reviewed it armax?15:41
salv-orlandoarmax: yes he did.15:41
armaxsalv-orlando: but not one on a fresh  ps15:41
mesteryRegardless, lets wait on this one then.15:41
salv-orlandoI searched comments for armax, I forgot we use real names on gerrit!15:41
mesterylol15:41
armaxsalv-orlando: I make people’s lives easier having a simple nick15:41
mesteryOK next one15:41
mestery#link https://review.openstack.org/#/c/134680/15:42
armaxnot like salv-orlando15:42
armax:)15:42
mesteryThis is armax and marun's decomposition spec15:42
mesteryIt's been nit picked, looks ready to me. Thanks for addressing my last pedantic nit armax. :)15:42
salv-orlandoI’m soft ok with it.15:42
salv-orlandomeaning that I’m ok as long as the other folks in the core team don’t have a grudge with it15:42
armaxmestery: no worries15:42
mesteryI'm good with this one, I think the plan is laid out well and like I said, my last nit was addressed.15:43
*** amotoki_ has joined #openstack-meeting-315:43
* salv-orlando waits for somebody to speak against this spec....15:43
* dougwig puts split spec back in the oven at 425 degrees.15:43
mesteryGoing once ...15:44
salv-orlandoif nobody opposes it anymore, the lazy consensus principle tells us what to do15:44
armaxmestery: if there’s rejection later, it won’t be the first time that a merged bp fails to complete :)15:44
mesterylol15:44
markmcclainsorry was looking over who's commented on it15:44
armaxmarkmcclain: you havent :)15:44
amotoki_sorry i am late. I am just back to home.15:44
markmcclainI think I've said enough in person :)15:44
*** baoli has quit IRC15:44
mesteryamotoki_: No worries :)15:44
mesterymarkmcclain: lol15:44
armaxmarkmcclain: true enough, in fact I am not complaining, I figured you were tired to hear the same stuff over and over again :P15:45
salv-orlando/me is fairly sure no spec high-fiving is occurring this release cycle15:45
mesteryOK, lets assume htis one will merge by Friday and move on.15:45
mesteryI don't see any huge blockers right now.15:45
maruner15:45
mestery?15:45
marunthe way it reads the work has to be done in kilo15:46
marunmestery: weren't you advocating for more time?15:46
maruni.e. done by the end of L15:46
mesterymarun: The wording was adjusted by armax, I am happy with the new wording.15:46
armaxmarun: let’s say that the work has to start in Kilo for sure15:46
mesterymarun: I only meant that if people put in a good effort for K, but fail to reach the goal, we are lenient with them.15:46
mesterymarun: If people do no work, then it's a different story.15:46
mesteryarmax addressed my comments in the latest version15:46
mesteryI'm good15:46
armaxmestery: yes, that’s the gist of it15:46
salv-orlandoI think plugin maintainers are hiring lawyers to understand what they can and what they can’t do ;)15:46
*** etoews has joined #openstack-meeting-315:47
mesteryrofl15:47
marun'required to be rewritten in kilo' seems pretty definitive15:47
armaxsalv-orlando: nice one!15:47
marunI'm not complaining, just making sure that was your intent.15:47
armaxmarun: it is, but at the same time we can open up the possibility of reevaluating where we are a couple of months down the rouad15:47
salv-orlandoarmax: that where a guy like our old friend Donal would come handy. He was both a lawyer and an engineer15:47
mesterymarun: Line 35415:47
mesteryStart there for the new wording15:48
*** dboik has quit IRC15:48
*** dboik has joined #openstack-meeting-315:48
armaxmestery: truth to be said, if you started…it should be possible for you to complete as well15:49
armaxmestery: but one never knows15:49
mesteryarmax: Yes, I was just looking out for folks here.15:49
marunmestery: I guess I see 339 as conflicting with 354.  maybe 354 should simply be removed15:49
*** thorst1 has left #openstack-meeting-315:49
mesteryI've already had a few talk to me privately about this, not defending folks, just looking to balance things a bit.15:49
marunbut I'm niggling.  probably nobody will care.15:49
mesterymarun: Your point is valid15:49
*** Sukhdev has joined #openstack-meeting-315:50
armaxI can say ‘should’ instead of will?15:50
amotoki_I think "should" or "strongly recommended" is an appropriate wording based on our discussion so far.15:50
armaxok15:50
mesteryamotoki_: ++15:50
marun+115:50
armaxanother rev coming up15:50
mesteryarmax: Cool15:50
armaxdougwig: you said your is at 425F?15:50
armaxI’ll put mine at 390F15:50
mesterylol15:50
dougwigarmax: yes, but it's a convection oven15:50
mesteryOK, lets move on15:50
mesteryNext up: rootwrap15:50
*** matrohon has quit IRC15:50
mestery#link https://review.openstack.org/#/c/93889/15:50
mesterysalv-orlando: A nrew rev was done, I think we can just approve now.15:50
mesteryYou had already done so in fact15:51
mestery:)15:51
armaxdougwig: :)15:51
markmcclainmestery: +115:51
salv-orlandomestery: doing that now15:51
mesteryExcellent! That was easy.15:51
* mestery looks out for the trap15:51
salv-orlandopretty sure there is hidden line saying that people +2ing that spec will become enslaved to the spec author15:52
mesteryrofl15:52
salv-orlandoanyway, next one15:52
mestery#link https://review.openstack.org/#/c/10566015:52
mesteryDHCP Agent Refactor15:52
mesteryThis one hasn't been updated in a long while15:52
mesteryWait15:53
mesteryThis is relay not refactor15:53
mesteryhold on15:53
markmcclaindo we have bandwidth for this?15:53
salv-orlandomestery: you have to do a bit of refactor for doing a relay15:53
* mestery needs more coffee15:53
mestery#undo15:53
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x3c050d0>15:53
salv-orlandobut I would also say that I have not seen a blueprint for “refactoring the DHCP agent"15:54
mestery#link https://review.openstack.org/#/c/137808/15:54
mesteryL2 Agent Improvements15:54
mesteryFrom rossella_s15:54
mesteryThis one I haven ot reviewed yet15:54
mesteryLooks like armax has at least :)15:54
armaxyay!15:54
mesterylol15:54
armaxI am first, for once15:54
salv-orlandoarmax: are you sure?15:54
rossella_sI think salv-orlando was first15:54
armaxcan’t compete with you guys I am slooooow15:54
armaxdamn15:54
armaxI thought I had it for a sec15:55
* mestery gives salv-orlando a gold star15:55
salv-orlandoarmax: thanksgiving played to my advantage15:55
armaxbut salv-orlando and I are technically interchangeable15:55
salv-orlandoanyway it’s getting in good shape. We just need a sync-up with otherwiseguy to separate responsabilities15:55
salv-orlandoand a contribution from marios for functional testing15:55
armaxI’ll look at it again15:55
mestery++15:55
mestery#action neutron-drivers team to review L2 Agent Improvements spec15:56
salv-orlandoanyway, if this should miss the deadline I guess nobody would object ane xception15:56
marun:/15:56
mesteryAck15:56
markmcclainsalv-orlando: +115:56
amotoki_agree15:56
mesteryOK next up15:56
mestery#link https://review.openstack.org/#/c/97967/15:56
mesteryPluggable IPAM15:56
*** carl_baldwin has joined #openstack-meeting-315:57
mesteryAgain, salv-orlando and armax are on the ball here15:57
salv-orlandoI think this one is close.15:57
markmcclainoh .. I was going to say the opposite15:57
salv-orlandoHowever, it needs a counterpart which I’m writing now.15:57
salv-orlandomarkmcclain: I think you want to rewrite it, I know.15:57
*** etoews_ has joined #openstack-meeting-315:58
salv-orlandoJust let us know if you think it’s done in a terrible way, so that we’ll just move it out early of our Kilo goal15:58
markmcclainI think this is something we should work on next week15:58
salv-orlandoalso because it potentially clashes a lot with plugin interface refactoring15:58
*** dboik has quit IRC15:59
mesteryOK, so sounds like this one will require a bit more review then15:59
salv-orlandomarkmcclain, mestery: sounds like we should freeze this15:59
markmcclainyeah it's part the conflict and part the lack of specifics15:59
*** banix has joined #openstack-meeting-315:59
mesterymarkmcclain: Can you comment in the spec on these aspects too?15:59
markmcclainyes will do16:00
mesteryCool16:00
salv-orlandoyeah just to inform the other people16:00
mesteryOK, last one I wanted to highlight16:00
mestery#link https://review.openstack.org/#/c/12825716:00
mesteryFull-stack white-box test framework16:00
mesteryThis is part of the testing effort16:00
salv-orlandoI had a long chat with marun on these.16:00
mesteryNice :)16:00
salv-orlandoI am ok with this effort going on.16:00
salv-orlandoI waited honestly a bit for some feedback from the QA team, but since there isn’t any16:01
mesteryI reviewed a much earlier version, I'll circle back on the latest one16:01
marunI'll need to review as well.16:01
mesterymarun: Excellent16:01
mestery#topic Open Discussion16:01
*** openstack changes topic to "Open Discussion (Meeting topic: neutron-drivers)"16:01
*** etoews has quit IRC16:01
mesteryAnything else this week?16:01
mesteryAny other BPs people want to highlight?16:01
*** hurgleburgler has joined #openstack-meeting-316:01
salv-orlandonothing major… but i wanted to understand what we’re supposed to do with l2 gateway16:01
*** dboik has joined #openstack-meeting-316:02
armaxsalv-orlando: yes, and I also wanted to spend a few words on the vsphere ones16:02
*** pballand has joined #openstack-meeting-316:02
mesteryL2 gateway, armax will have something to say there :)16:02
salv-orlandowe have 3 related API specifications under review. I don’t want to pick a winner, also because I don’t feel like I have the technical authority too16:02
salv-orlandobut I wonder why this topic is so contentious that it’s been 2 years that we’re trying to get to a sort of consensus on the shape of the API16:03
armaxsalv-orlando: to be honest I am now in one of the final stages of the kubler-ross model16:03
salv-orlandoso at this stage I’d let independent competing effort to go ahead16:03
armaxacceptance16:03
armax:)16:03
salv-orlandoand let the users pick a winner16:03
salv-orlandothere will be only one16:03
salv-orlandolike highlander, you know16:04
armaxI think the best course of action would be to allow these to bake a little more16:04
amotoki_re: L2 gateway  it needs more descripiton on how it covers use cases by the proposed model (though I haven't commented yet)16:04
armaxultimately the one effort that I think is the most attainable should be developed out of neutron16:05
salv-orlandoso my opinion is that if teams want to go ahead and implement out of tree versions of l2 gateway APIs I’m happy with it, but we aren’t able as a community to define a L2 gateway API which can be deemed “official"16:05
armaxat least until the feature is fully backed16:05
armaxbaked16:05
salv-orlandowhy everyone wants to bake everything today? Is that because christmas is coming?16:05
marungo ahead -> go ahead outside of tree?16:05
armaxsalv-orlando: that’s my thinking progress, at least for now16:05
salv-orlandomarun: yes.16:06
marun+116:06
*** safchain has quit IRC16:06
mestery+116:06
armaxwe could consider l2gw api, another example of a service api16:06
armaxand revisit progress later on16:06
mesterystackforge it is!16:06
armaxhaving said that I am making the effort of reviewing the specs to provide guidance16:06
markmcclainsalv-orlando: what is the recommended baking temp?16:06
salv-orlandook I suggest to -2 the relevant blueprints explaining what we have said here16:07
armaxbut no committment about reviewing code if it targets the neutron repo16:07
salv-orlandoand wait for the furious reaction from the owners16:07
armaxsalv-orlando: I don’t think a -2 is appropriate16:07
salv-orlandowith the usual trail of threats and stuff like that16:07
mesteryThreats before Christmas, nice.16:07
mesterySomeone is getting coal this year16:07
mesteryAnything else, or shall we close this meeting early today?16:08
armaxabout vsphere...16:08
salv-orlandoarmax had the vsphere thing16:08
mesteryah16:08
mesteryvsphere16:08
mesteryyeah16:08
mesteryplease go ahead armax :)16:08
armaxsimilar discussion we had on l2gw16:09
armaximo this is a clear example of a new effort that should follow the model marun and I have been pushing for16:09
marunwhy isn't -2 appropriate for things that are not going to go forward in the tree?16:09
*** peristeri has joined #openstack-meeting-316:09
*** safchain has joined #openstack-meeting-316:10
armaxmy opinion is that if stuff is out of tree but still have a viable integration path into neutron16:10
armaxwhy would they need to be blocked?16:10
salv-orlandocrossing wires...16:10
*** pballand has quit IRC16:10
armaxthe spec then becomes just a matter of visibility16:10
salv-orlandofor the vsphere effort I just think that in light of spec #136480 the umbrella blueprint is superseded16:11
salv-orlandoit seemed to me it was an attempt of forcibly building a community. But this is just my opinion16:11
armaxthe umbrella is there to give a context about what’s going on as far as vsphere efforts are concerned16:11
salv-orlandoit does not necessarily reflect the community or my employers’s view ;)16:11
armaxbut point taken16:11
marunI think the spec process if first and foremost to in-tree development effort.16:11
marunBut that's just me.16:11
marunif -> is16:12
marunarg.16:12
armaxmarun: that model is evolving imo16:12
armaxand we have stuff that’s infligh16:12
armaxt16:12
marunI think the spec process is first and foremost to gate in-tree development effort.16:12
marunIf we don't focus it, we're going to waste cycles on non-essentials.16:12
marunThere are lots of other avenues for feedback that don't gum up mainline development.16:12
amotoki_from user perspective, isn't it also important to coordinate similar efforts like vspher works.... even though it is not in-tree.16:13
armaxmy point being that spec serve a useful documentation purpose16:13
mestery++ to what marun is saying16:13
mesteryMy opinion is if we let things which aren't in-tree have specs, we'll drown fast16:13
marunamotoki_: I'm not sure why that has to happen in the spec repo.16:14
salv-orlandoso neutron-specs should actually be the place not just for neutron specs but for all specs concerning development related to openstack networking. Still, it should not be used to ask the drivers/core team approval for what amount to “experiments” which can live in stackforge without any oversight imho16:14
marunamotoki_: And if it does, a -2 makes it clear where the spec stands without preventing people from collaborating.16:14
*** SumitNaiksatam has quit IRC16:14
*** Longgeek has quit IRC16:14
salv-orlandobut I agree with marun that anything that goes in neutron specs must be related to things that get then implemented in code16:14
mesterySo, we're ok taking on extra overhead in neutron-specs for things which won't land in-tree and will live out of tree?16:14
armaxin lieu of a new pmechanism that allows to raise visibility, I am not sure what’s the best course of action16:14
mesteryThat's what I'm reading this as .16:14
amotoki_marun: I agree only if we are talk about spec reviews.16:15
anteayasalv-orlando: just as a piece of info stackforge is the wild west on purpose16:15
salv-orlandomestery: I think wires are crossed. I don’t understand if we’re talking about the l2 gw specs or the vsphere umbrella blueprint16:15
marunamotoki_: so, use spec repo for reviewing potential work that won't land in tree, but -2 to indicate that status?16:15
anteayaI agree in spirit but the mechanics aren't there16:15
armaxperhaps we can tweak the template for now, to add a section that describes the relationship of the work with Neutron16:15
mesterysalv-orlando: I thought we were talking in general about things which will live out of tree, but are networking related, having specs in neutron-specs?16:16
markmcclainI'd really like to keep specs focused on in tree work16:16
markmcclainwe're trying to tell the operators this is what we're working on16:16
*** Longgeek has joined #openstack-meeting-316:16
markmcclainand if something does not stand a chance of merging we should be explicit about it16:16
mesteryI worry about bandwidth and expectations if we allow specs to open up for code which isn't in tree too16:16
armaxmarkmcclain: ok but what about work that’s happening on the side, that can still make meaningful progress?16:16
mesterymarkmcclain: Right16:16
amotoki_I agree we should focus spec reviews on in-tree works.16:16
mesteryarmax: Why do they need a spec for on the side work?16:16
armaxmarkmcclain: we’d need to have a away to capture that somehow16:16
marunwell, if we -2 doesn't it make it clear to everyone what's going on?16:16
dougwigif you want it to be specs for neutron, but want the community to have a place in gerrit for "non-neutron" specs, make a new specs repo for that.  neutron-incubator-specs or something16:17
marunnothing stopping iteration even with -216:17
markmcclainarmax: side work can always continue on the ML, stackforge, etc16:17
amotoki_vendor split-out brings users a question on how to coordinate competing efforts.... it is antoher problem.16:17
marunamotoki_: not sure what you mean?16:17
armaxmarkmcclain: my point being -2 gives the wrong signal to the eyes that look at it16:17
marunarmax: which eyes?16:17
*** pballand has joined #openstack-meeting-316:17
markmcclainit we allow anyone to discuss anything I'm afraid we'll return to the problem we had at past design summits16:17
marunarmax: and if so, dougwig's suggestion of a separate repo makes sense imho16:18
amotoki_there are many proposals on vsphere supports. how do we coordinate these efforts? this is my question.16:18
anteayasounds like education needs to happen, we can't keep changing our process to fit the expections of the lowest thereof16:18
armaxyes, that could be a viable alternative16:18
dougwig-2 does not mean "not in neutron, but keep on!".  to the community, it means, "here, enjoy this 2x4 to the face!"  sorry, but it's overloaded at this point.16:18
mesterydougwig: lol16:18
markmcclainwhere folks mis-read the officialness/ready for production of the things and then we paid for it in complaints16:18
salv-orlandopersonally I am not a bull, so seeing a red cross does drive me mad16:18
marundougwig: it's a pretty handy 2x416:19
anteayamarkmcclain: going back to what was at past design summits would be a huge step backward16:19
marunanteaya: +116:19
markmcclainsaying not yet is hard… but honestly we've got to say it more16:19
marun+116:19
salv-orlandook, let’s say no -2… we’ll put those spec back in WIP status (workflow -1)16:19
mesteryIf it's not in-tree or proposed as in-tree in neutron, it doesn't need a spec in neutron-specs.16:19
marunsalv-orlando: but wip can be removed on a new patch submission :/16:19
armaxmestery: so I am unclear about the outcome of this discussion16:19
mesteryIf people can't find other ways to discuss things than neutron-specs, we've failed as a community.16:19
salv-orlandomarun: just trying to find a way out from this discusion…. sorry16:20
markmcclainwell the specs are for kilo so if it is clearly not going to make it we should -2 with a comment that says "discussion deferred to kilo"16:20
mesterymarkmcclain: Right16:20
marun-2 is 'this ain't gonna merge' from a gerrit perspective16:20
marunentirely appropriate here16:20
markmcclain^H^H^H^HLemming16:20
mesteryBut my point is, if I'm developing "rabbit out of a hat as a service" in stackforge, don't file a neutron-spec for it16:20
mesteryIt's not in neutron16:20
armaxwould it make sense to go over the specs and select the ones that can be developed outside of neutron and still capture them somewhere else?16:20
mesteryif you propose it to neutron later, file a spec then16:21
armaxlike dougwig suggested?16:21
mesteryarmax: My concern is that we don't have authority for "outside of neutron"16:21
mesterywe can say "do it outside neutron"16:21
mesteryBut once that happens, they can do it however they want outside neutron16:21
marunstackforge/neutron-specs16:21
salv-orlandoarmax: ok, but why? Just to have a place where people can know things are happening?16:21
marun--> specs ghetto ;)16:21
mesterymarun: But don't we then validate things and move the old problem to stackforge/neutron-specs?16:21
armaxsalv-orlando: primarely yes16:22
marunmestery: I'm for simply -2'ing.16:22
mesterymarun: Me too16:22
mesteryIt's simple and clear16:22
*** sigmavirus24 has left #openstack-meeting-316:22
marunmestery: that can mean 'not yet' or 'not ever', depending.16:22
markmcclainisn't that the ML?16:22
armaxmestery: ok, I was unable to convince why it isn’t, but ok16:22
markmcclainbasically post and say I'm working on FooaaS ping me and we'll collaborate16:22
mesteryyes16:22
anteayaif folks don't understand -2 then they need to learn, not change giving a -2 when it is needed16:22
mesteryanteaya: ++16:23
marunmestery: but the takeaway is 'we don't have to treat this as something to review on a priority basis.  only if you care about the topic.16:23
marunanteaya: ++16:23
mesteryRight, that sounds like a -2 to me16:23
armaxML does not sound like the best way to document things16:23
marunarmax: we don't need process for things that we aren't managing16:23
marunarmax: process for process sake -> nobody's friend16:24
salv-orlandoarmax: ok, but we don’t need to put those through a review process then, do we?16:24
armaxmarun: I am not advocating for process16:24
salv-orlandomarun: I think it’s also called bureaucracy16:24
marunarmax: if someone wants to pursue an out-of-tree effort, because neutron isn't appropriate for it right now, they should do so unencumbered by us in any way.16:24
marunarmax: our job is done when a consensus is reached that a -2 is appropriate16:24
mesterymarun: ++16:24
anteayamarun: that is my defintion of out-of-tree16:24
armaxmarun: ij16:25
armaxmarun: ok16:25
anteayathat doesn't prevent those people from attending meetings and leraning and listening16:25
mesteryRight16:25
anteayaand guiding their efforts so they will be accepted16:25
armaxarmax: at this point I’d be just tempted to say ‘abandon the spec’16:25
anteayait jus tmeans they can't take review resources16:25
marunarmax: I think that's reasonable.16:26
armaxand do it somewhere else if you wanted to…but do we want to provide that ‘somewhere’ else, to help the discoverability of the effort?16:26
mestery++16:26
armaxML is not appropriate16:26
* mestery notes 4 minutes left16:26
armaxpeople complain about ML16:26
* mestery wants to manage less, not more16:26
armaxnot me, but people do16:26
armax:)16:26
mesterystackforge16:26
marunarmax: our new meeting format should be a good place16:27
salv-orlandopeople complain about stackforge. not me, but people do.16:27
*** melwitt has joined #openstack-meeting-316:27
salv-orlandojust kidding16:27
marunarmax: 'hey, i'm working on this, if you're interested talk to me!'16:27
anteayaarmax: what would happen if you take the material in the spec and use that for documentation in the repo?16:27
* mestery slaps salv-orlando 16:27
mestery;)16:27
armaxanteaya: not sure I fully understand what you mean16:27
*** wpward has left #openstack-meeting-316:27
*** shwetaap1 has joined #openstack-meeting-316:27
*** aleksandr_null has joined #openstack-meeting-316:27
anteayaif you have a bunch of information currently in a spec that is homeless16:27
anteayawould the repo itself be a potential home16:28
mesteryFolks, we have < 2 minutes left.16:28
*** shwetaap has quit IRC16:28
mesteryLets look at continuing this discussion at some point if we need to16:28
mesteryMaybe on the ML16:28
marunanteaya: even abandoned changes live forever in gerrit16:28
salv-orlandoone more quick thing from me… can I?16:28
anteayathey do16:28
* mestery runs for cover :)16:28
mesterysalv-orlando: yes16:28
salv-orlandospec for consolidarting neutron core: https://review.openstack.org/#/c/136760/ - I sense there is an intention of reading as a renaming of extension into feature, and leaving the core - intenteded as the API every deployment must provide - as simple as it is today.16:28
mesteryyou have 40 seconds16:28
salv-orlandoif that is the intention, I will just abandon the spec16:29
mesterysalv-orlando: Will look, please, others look as well.16:29
amotoki_as a consensus, now -2 on neutron-specs means two things: that  it is deferred out of Kilo (for things appropriate for neutron in-tree) andthat it does not fit in-tree neutron. we are looking for a place to discuss out-of-tree neutron-related tipics..16:29
amotoki_right?16:29
salv-orlandobecause the point for me is that we shoul stop thinking that the backend defines the ip16:29
mesteryOK, we're out of time now folks.16:29
salv-orlandothat’s all fromme16:29
mesteryThanks for the lively discussion, see you all again soon!16:29
mestery#endmeeting16:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:29
salv-orlandoadieuuuuuu16:29
openstackMeeting ended Wed Dec  3 16:29:45 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-12-03-15.31.html16:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-12-03-15.31.txt16:29
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-12-03-15.31.log.html16:29
armaxamotoki: I think people see -2 as cease and desist16:30
armaxI think it’s bad16:30
marunarmax: I think we should change that perception16:30
armaxmarun: riiight...16:30
marunarmax: -2 is also used for 'not now'16:30
armaxgood luck16:30
amotoki_armax: yeah. agree that people feel so.16:30
amotoki_-2 is very disappointing :-(16:30
*** mwagner_lap has quit IRC16:31
*** melwitt has quit IRC16:31
amotoki_bye16:31
armaxamotoki_: right, so I think we should use it carefully16:31
armaxand perhaps devise other ways to encourage people to progress alternatively16:32
amotoki_totally agree. we need to find appropriate place to discuss neutron related topics.16:32
armaxright, most contributors just feel gutted of a -2 and give up, some don’t, but most do16:33
marunarmax: look, we used to never give out -1's either16:33
armaxI think we should make an effort to prevent that from happening16:33
marunarmax: I argued for a -1 being a good way of communicating that issues needed addressing pre-merge.16:33
marunarmax: And now, that's the way people think of it.16:33
marunarmax: people can change.16:33
marunit just takes time.16:34
armaxmarun: let’s talk some more offline, but for now I’d say let’s ponder on this a bit before we reach to any conclusion16:34
*** baoli has joined #openstack-meeting-316:36
*** bpokorny has joined #openstack-meeting-316:37
*** Sukhdev has quit IRC16:39
*** markmcclain1 has joined #openstack-meeting-316:40
*** markmcclain has quit IRC16:42
*** markmcclain1 has quit IRC16:44
*** vineetmenon_ has joined #openstack-meeting-316:45
*** belmoreira has joined #openstack-meeting-316:48
*** dheeraj-gupta-4 has joined #openstack-meeting-316:49
*** shwetaap1 has quit IRC16:56
*** Sukhdev has joined #openstack-meeting-316:57
*** shwetaap has joined #openstack-meeting-316:57
*** mriedem has joined #openstack-meeting-316:59
*** melwitt has joined #openstack-meeting-316:59
mriedemhi!17:00
mriedemcellz!17:00
alaski#startmeeting nova_cells17:00
bauzaslike DBZ ?17:00
openstackMeeting started Wed Dec  3 17:00:29 2014 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
bauzas30 years of Dragon Ball !17:00
alaskiHi everyone17:00
melwittHello cellz17:00
mriedemnothing like DBZ17:00
belmoreirahi17:00
dheeraj-gupta-4hi17:00
bauzas\o17:00
vineetmenon_hi17:01
alaski#topic cells manifesto17:01
*** openstack changes topic to "cells manifesto (Meeting topic: nova_cells)"17:01
alaskihttps://etherpad.openstack.org/p/kilo-nova-cells-manifesto17:01
bauzasLGTM17:01
alaskicool17:01
mriedemoo nice17:01
* mriedem needs to read it17:01
*** vishwanathj has joined #openstack-meeting-317:01
alaskiit wasn't clear if anyone had looked at it yet17:01
*** lhcheng has joined #openstack-meeting-317:01
edleafeo/17:01
bauzasyeah, EU people have an advantage because we were not eating Turkey :)17:02
alaskiI think I have a few changes I'd like to put in for discussion, but due to a short week haven't gotten to it17:02
bauzasalaski: I'm +1 on it17:02
mriedemthat's a disadvantage right?17:02
alaskiseems like it to me17:02
mriedemalaski: so once we're good with the etherpad, where does that go?17:02
mriedemdevref? blog? other? beuler?17:02
bauzasdevref IMHO17:03
bauzas+ blog17:03
dansmithI think it needs to hit the mailing list, but not in etherpad form17:03
alaskimriedem: devref ultimately, also an operator list post, and a blog would be good as well17:03
mriedemok, yeah, ML would be good (and not in etherpad so random joe can mark it up)17:03
dansmithdo we want to just propose that as a devref thing, perhaps with alaski's diagrams,17:03
dansmithand send that to the ML?17:03
mriedemi'd be good with that17:03
alaskiyeah, sounds good17:04
bauzas+117:04
mriedemif i'm going to read it, i might as well do it in gerrit17:04
belmoreiradansmith: +117:04
alaskidansmith: you want to take that?17:04
vineetmenon_mriedem : +117:04
dansmithalaski: heh, was just about to make you do it17:04
alaskiheh17:04
dansmithbut sure, we'll do it somehow17:04
alaskiyeah, I don't mind proposing it17:05
dansmithshow your diagrams17:05
alaski#action propose manifesto to devref17:05
alaskihttp://paste.openstack.org/show/144068/17:05
alaskiI forgot to add this to the agenda17:05
alaskibut I drew a few pictures17:05
*** MaxV has quit IRC17:05
alaskiI would love feedback17:05
dansmithgood ascii diagrams are like geek porn17:05
vineetmenon_alaski: nice17:06
alaskiand want to include them in appropriate specs, and the manifesto if that helps17:06
*** jacalcat1 has joined #openstack-meeting-317:06
dansmithI think they should go with the manifesto as well, yeah17:06
bauzasalaski: volunteering for creating yet another etherpad for diags ?17:06
alaskibauzas: I tried that...17:06
bauzasalaski: oh, fonts are getting you mad ?17:06
alaskithe pads aren't monospaced17:06
*** SridharRamaswamy has joined #openstack-meeting-317:07
*** wdutch has quit IRC17:07
bauzasalaski: eh17:07
alaskiit's a client side setting to change it17:07
*** Sukhdev has quit IRC17:07
alaskiso I'm happy to put them in a pad, with instructions on how to actually view them17:07
bauzasalaski: agreed17:07
*** jacalcat has quit IRC17:07
mriedemwell,17:08
mriedemdevref can link to images right?17:08
mriedemonce we're happy with the diags we could just put into an image file and store with the docs17:08
dansmithdevref can include these eaasily17:08
alaskibauzas: https://etherpad.openstack.org/p/nova-cells-flow-diagram I need to add the last one17:08
dansmithbecause they're ascii17:08
bauzasmriedem: IIRC, there are even diagrams in devref17:08
mriedembauzas: yeah for the rpc stuff17:08
bauzasmriedem: they would need some updated btw. :d17:08
vineetmenon_alaski: etherpad just broke your diagram17:08
bauzas*updates17:09
mriedembauzas: yeah, devref doesn't mention objects i'm pretty sure...17:09
bauzasmriedem: think about betting...17:09
mriedemwhat's next?17:09
dansmithalaski: shall we move on?17:09
bauzasalaski: that sounds acceptable for reviewing, I mean the client change in the etherpad17:09
alaskiyep, distracted by etherpad17:10
alaski#topic testing17:10
*** openstack changes topic to "testing (Meeting topic: nova_cells)"17:10
alaskihttps://etherpad.openstack.org/p/nova-cells-testing17:10
alaskiI've added a bunch of info there17:10
dansmithooh nice17:10
alaskithere are some reviews linked with fixes as well17:10
alaskihelping to categorize/fix the remaining failures would be a huge help17:11
vineetmenon_since we are on testing, has anyone looked into this? https://blueprints.launchpad.net/nova/+spec/cells-tempest17:11
vineetmenon_quite an old BP17:11
dansmithwhat about it?17:11
alaskiheh, that's basically what we're doing17:11
alaskibut realistically that should be an infra bp if anything17:12
dansmithqa17:12
vineetmenon_dansmith, alaski: yes exactly... aren't we repeating it.. I mean that BP was basically abandoned17:12
mriedemyeah qa17:12
alaskior that...17:12
dansmithor tempest or whatever, but yeah17:12
sdaguealaski: can we organize that into a list of reviews that are: merged, ready for review, wip?17:12
mriedembut they've been fine with the patches so far it seems17:12
dansmithvineetmenon_: it was never started17:12
dheeraj-gupta-4alaski: very nice info17:12
alaskisdague: yes, I can do that17:13
mriedemsdague: yeah i was going through that list now17:13
sdaguealaski: thanks17:13
alaski#action alaskiorganize testing etherpad into reviews that are: merged, ready for review, wip17:13
alaskivineetmenon_: I think that bp is fine being abandoned.  if we need a new one we'll create it17:14
mriedemhttps://review.openstack.org/#/c/135285/ is going through the gate17:14
mriedemwhich will take awhile17:14
sdaguewill definitely help on getting them reviewed in a more timely manner if we have a concise list. It would also be really nice to call out which repo the reviews are against so people will know if it's something they have +2 on before following the link17:14
vineetmenon_alaski: sure.. I just thought mentioning it here..17:14
alaskivineetmenon_: appreciated.  if it was a qa bp I would feel different, but most of the work isn't in nova17:15
dansmithaye17:15
alaskisdague: cool, we can do that too17:15
*** vishwanathj has quit IRC17:15
alaskianything else on testing?17:15
*** clu_ has joined #openstack-meeting-317:15
mriedemhow much are we waiting on https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/flavor-from-sysmeta-to-blob,n,z now?17:16
alaskia little17:16
alaskiI'm eager for it, but there are plent of other things to tackle still17:16
mriedemok, just figuring out nova review priorities since the one nova patch in there is approved, just needs gate babysitting17:17
mriedemi've sucked at nova reviews since the break17:17
dansmithflavors have been keeping me from reviews too17:17
mriedemonce a couple of these get in, we can go back and check test results again17:17
alaskiit will become more urgent as the list of failing tests dwindles17:17
dansmithI need to just put it down for a day17:17
mriedemmoving on?17:17
alaski#topic analysis of tables17:17
*** openstack changes topic to "analysis of tables (Meeting topic: nova_cells)"17:18
alaskihttps://etherpad.openstack.org/p/nova-cells-table-analysis17:18
dansmithokay, big disclaimer:17:18
alaskidansmith put some lists together17:18
dansmiththis is just a first, uninformed pass at sorting things into global/cell scope17:18
bauzasjust one comment, could we maybe put all the etherpads in a wikipage ?17:18
mriedemmaybe you want to put that into the etherpad :)17:18
dansmiththere are a bunch I don't know what to do with, mostly because I need to look at how they're used, but some are opinion calls17:18
*** dconde has joined #openstack-meeting-317:18
mriedembauzas: was thinking the same17:18
mriedemglobal cell == global wiki page17:18
bauzasmriedem: agreed17:19
alaskibauzas: yeah17:19
bauzastime for opening a wikipage, eh ?17:19
alaskiI should also be linking all of these...17:19
alaski#link https://etherpad.openstack.org/p/nova-cells-table-analysis17:19
bauzasalaski: yeah, I'm pretty worried of loosing focus on all etherpads17:19
bauzasI can't track them like in Gerrit17:19
bauzasand I'm pretty bad in making shortlinks17:19
vineetmenon_bauzas: +117:20
alaskiok, I'll corral everything into a wiki17:20
bauzasalaski: awesome17:20
alaskias far as the tables go17:20
mriedemalaski: feel free to delegate a bit :) if you want i can do the wiki tedium17:20
bauzas:)17:20
bauzas\o too17:21
alaskiit would be good to get some feedback on the preliminary organization, and thoughts on what to do with the uncategorized one17:21
bauzasyeah, the unsure section needs debating a bit IMHO17:21
dheeraj-gupta-4alaski do we put our comments in the etherpad itself?17:21
alaski#action mriedem bauzas set up a wiki page to corral etherpad links for cells work17:21
bauzaswoah, 2 people on that heavy task :)17:22
dansmithdheeraj-gupta-4: comments about the table split you mean?17:22
dheeraj-gupta-4yes for the table split17:22
*** mwagner_lap has joined #openstack-meeting-317:22
dansmithI think this is going to be a worksheet, so lets see how it goes with people putting comments in here17:22
dansmithjust please try to keep the list readable by people as well17:22
bauzasyeah, I'm just concerned about grouping some tables17:22
bauzaslike aggregates and instancegroups17:22
alaskicomments in the etherpad seems like a good place to start17:23
bauzasboth of them are related to scheduler17:23
bauzasalaski: agree17:23
melwittcomments on any etherpad content in general maybe, make comments at the bottom or something?17:23
dheeraj-gupta-4yes comments section is a good idea17:23
dansmithmelwitt: sure, or at the bottom of a section17:23
alaskithis is very preliminary so we'll likely have to adjust how we approach this, but this is a good starting place17:23
vineetmenon_bauzas alaski: for heated tables, I'm afraid etherpad would may become illegible..17:23
bauzasyeah, we can do both inline and at the end of the doc, sure17:24
dansmithvineetmenon_: that's why people need to be on their best behavior and keep the doc readable17:24
*** lhcheng has quit IRC17:24
dansmithif you want to argue about something, etherpad isn't the place anyway17:24
alaskimaybe just call out controversial tables17:24
alaskiand we can discuss here or in another medium17:24
dansmithafter we make a few passes at this, we could do another devref and argue the minutia in gerrit17:24
dansmiththe biggest problem I see here is actually the nova-network tables17:25
vineetmenon_dansmith: +117:25
bauzasalaski: well, even the 2nd table about a global CellsV2 DB is debatable IMHO (compute_nodes)17:25
dheeraj-gupta-4bauzas: +117:25
dansmithbecause I don't want to spend a bunch of time making nova-network split-able just to deprecate it17:25
mriedembauzas: https://wiki.openstack.org/wiki/Nova-Cells-v217:25
dansmithbauzas: what does that mean?17:25
*** s3wong has joined #openstack-meeting-317:25
bauzasdansmith: I mean that I'm not sure that compute_nodes should be global if we consider a scheduler per cell17:26
alaskischeduling is a whole other can of worms right now17:26
*** devvesa has quit IRC17:26
bauzasalaski: yeah, hence my worries17:26
dansmithbauzas: ah, well, I don't know that I think scheduling should be per-cell anyway, which is why I put it there :)17:26
alaskibut I think we should consider it orthogonal for now17:26
belmoreiradansmith: nova-newtwork may be a requirement... depends in neutron migration progress17:26
bauzasalaski: agreed17:26
dansmithbelmoreira: I know, that's my point17:26
dansmithhow about this17:27
bauzasalaski: but in that case aggregates should be orthogonal, and here comes the discussion17:27
dansmithif there are things in one or the other section, lets move them to a "contentious" section and explain why17:27
dansmithunsure will continue to be "needs more investigation"17:27
alaskidansmith: +117:27
bauzasanyway, let's put our thoughts on the etherpad, for sure17:27
alaskiit will be nice to get a list of low hanging fruit tables, like flavors and keypairs17:28
alaskifrom there we can move into the contentious ones17:28
*** yalie has joined #openstack-meeting-317:28
dansmithyep17:28
bauzasalaski: I think the sections are trying to do this17:28
bauzasalaski: maybe some of the items need adjustment17:29
vineetmenon_dansmith is already done with low handing fruit tables, right17:29
dansmithvineetmenon_: this is just a proposal, it needs review and sign-off17:29
alaskibauzas: sure, lets capture that on the pad for now17:29
vineetmenon_dansmith: ack17:29
dansmithlike, compute_nodes was one I assumed was low hanging, but it's not17:29
dansmithso let's see next week if people have more issues with these17:29
dansmithafter thinking/reading17:30
*** jcoufal has quit IRC17:30
*** lhcheng has joined #openstack-meeting-317:30
bauzas+117:30
alaskiagreed17:30
dansmithand it would be great if folks could look at the unsure ones and try to evaluate where they belong, or at least add comments about the implications17:30
belmoreira+117:30
*** iovadia has left #openstack-meeting-317:30
alaskimoving on17:30
mriedemi need to read back through alaski's 2 specs first i think17:30
alaski#topic scheduling requirements17:31
*** openstack changes topic to "scheduling requirements (Meeting topic: nova_cells)"17:31
* dansmith runs17:31
alaski#link https://etherpad.openstack.org/p/nova-cells-scheduling-requirements17:31
alaskidansmith: you're off the hook for this one17:31
dansmithwoot17:31
alaskijohnthetubaguy couldn't make it today, but he put some thoughts down17:31
*** mattfarina has joined #openstack-meeting-317:32
alaskihe added some possible solutions at the bottom, but what I'm more interested in currently is what are the needs17:32
dansmithso, belmoreira should add some things? :)17:32
alaskiI know what Rackspace needs, but I don't know about CERN/Nectar and non cells users17:33
alaskidansmith: right :)17:33
dansmithso let's specifically call out the holes17:33
*** wuhg has quit IRC17:33
belmoreiradansmith: I need to read it...17:33
bauzasmmm, that still relates to the discussion about a global scheduler or not17:34
alaskibauzas: it will inform that discussion17:34
bauzasI agree with johnthetubaguy about the scaling concerns17:34
bauzasalaski: agreed17:34
dansmithbauzas: it does, but we need to know what the current at-scale folks need/want/think is important17:35
alaskibelmoreira: sure, we'll touch back on this next week or after17:35
dansmithwhat about some people at scale not using cells?17:35
bauzasdansmith: yeah, I totally understand17:35
dansmithlike phil or paul?17:35
alaskiyeah, that would be great info17:35
bauzasdansmith: I discussed with john about some scaling issues they had with the existing nova scheduiler17:35
belmoreiraalaski: for next weeks can you publish the links before the meeting?17:35
alaskibelmoreira: yes17:36
alaskiI'll add links to the agenda17:36
bauzasdansmith: that's basically IO problems with context switching the greenthreads17:36
alaski#action add links to the agenda before a meeting17:36
bauzasdansmith: when they were accessing the DB IMHO17:36
dansmithbauzas: yeah17:36
mriedemwiki is here now: https://wiki.openstack.org/wiki/Nova-Cells-v217:36
bauzass/IMHO/IIRC17:36
mriedemalaski: ^17:36
mriedemso we could just throw that in the meeting agenda17:36
alaskimriedem: ahh, good point.  I can add them there too17:36
bauzasdansmith: so I'm a little concerned about a "global scheduler" wishlist17:37
alaski#link https://wiki.openstack.org/wiki/Nova-Cells-v217:37
alaskibauzas: what's your concern?17:37
dansmithbauzas: I put "as it relates to cells" in the page, but I think we need to hear this17:37
bauzasalaski: I just want to make sure that the scheduler can scale :)17:38
alaskithis shouldn't be a wishlist, but a list of what the current usage is17:38
bauzasalaski: hence the CachingScheduler that john provided17:38
alaskibauzas: so do I :)17:38
dansmithbauzas: we don't have to do everything that is posted here, and certainly not things that aren't achievable or compatible with the overall goal :)17:38
bauzasalaski: but I don't want to speak on behalf of him :)17:38
*** sergef has quit IRC17:39
bauzasdansmith: \o/17:39
bauzassounds like the voice of reason17:39
dansmithnext?17:39
alaskiyep, had to find my agenda tab...17:39
alaski#topic Connection info in database or config file?17:39
bauzasopens ?17:39
*** openstack changes topic to "Connection info in database or config file? (Meeting topic: nova_cells)"17:39
* dansmith cracks the whip17:39
bauzasoh17:40
alaski#link https://review.openstack.org/#/c/135424/17:40
bauzasthanks for having raised it17:40
dansmithso, I definitely think that the connection info needs to be in the DB17:40
alaskiand I agree with that17:40
bauzaseh eh17:40
bauzasnext then ? :)17:40
belmoreira:)17:40
bauzasnah, just saying it was a configuration problem17:40
alaskiI'd like to understand why a config would be useful17:40
vineetmenon_then are you planning every config to reside in DB? or something in DB and something in file?17:40
*** armax has quit IRC17:41
bauzasalaski: I'm just thinking of something that is operator-related17:41
alaskivineetmenon_: all of it in the db17:41
alaskivineetmenon_: regarding what's in the spec17:41
*** VW_ has joined #openstack-meeting-317:41
vineetmenon_so it will need complete overhaul of existing things as well, right17:41
dansmithvineetmenon_: not all of nova.conf of course, just this tiny piece17:42
bauzasalaski: atm, connection URIs are stored in a conffile17:42
alaskibauzas: I think a config makes operation more difficult as it can't be done online17:42
bauzasalaski: well, it requires a service restart I agree17:42
vineetmenon_dansmith, alaski: ack17:42
bauzasalaski: do we consider autoscaling for cells ?17:42
alaskibauzas: and for cells v1, we do store the cell relationships in the db and the mq connection info17:43
bauzasalaski: I still need to remember my little knowledge about Heat resources17:43
bauzasalaski: but you agree that's only for cells, not for Nova ?17:43
bauzasin general I mean17:43
alaskibauzas: I'm not sure autoscaling and cells go well together17:43
dansmithbauzas: what do you mean "only for cells" ?17:43
alaskibecause there's a physical component involved17:44
belmoreiraalaski: there is also the file option17:44
bauzasalaski: so is the service restart really a problem ?17:44
dansmithbauzas: yes17:44
vineetmenon_bauzas: well, nova is part of cell, in one way or another.. So, I guess both17:44
bauzasbelmoreira: that's what I'm mentioning as conf file17:44
bauzasbut OK, I don't want to bikeshed things17:44
bauzasseems like there is a large majority17:44
alaskibauzas: yes, this is only for cells17:45
*** yamamoto has quit IRC17:45
*** vishwanathj has joined #openstack-meeting-317:45
bauzasand that's something manageable thru a nova-manage thing17:45
dansmithalaski: but every nova deployment will have at least one of these in the table17:45
alaskidansmith: right17:45
*** jaypipes has quit IRC17:45
belmoreirausing configuration management tools is much more easy to manage configuration files17:45
dansmithwhich is why I don't want to say things like "only for cells"17:45
bauzasso, I'll change my vote and ask for something manageable, that's it17:45
dheeraj-gupta-4If we move the connection and DB to a file, we probably won't need a cells table :)17:45
alaskidansmith: fair enough17:45
alaskidheeraj-gupta-4: sure, but then I have to restart my apis to add a new cell17:46
dheeraj-gupta-4or to delete one17:46
bauzasalaski: actually policy files are not requiring a service update17:46
*** hinnant_ has joined #openstack-meeting-317:46
bauzasalaski: so, that's maybe an implementation detail ?17:47
bauzass/service update/service restart17:47
* bauzas dammit17:47
mriedemi think being able to refresh config options on the fly is a wishlist for everyone for a long time17:47
dansmithwe could do it in a config file without requiring restarts, of course17:47
alaskibelmoreira: if you're currently using config I don't want to break that for you.  perhaps we can look into a way to make them both work17:47
dansmithI don't really see the point, TBH17:48
alaskibelmoreira: but operationally I think a db is easier17:48
mriedemwe could read the config file only for the cells group and reload the options in memory17:48
mriedemyeah17:48
dansmithmriedem: everything is doable, nothing about a config file requires static-ness17:48
bauzasyeah...17:48
dansmiththe thing is, however,17:48
dansmithif you want an API to add a cell17:48
bauzasso the question is, what's better for cells operators ?17:49
dansmithdoing it in the config file means you really can't have that17:49
*** hurgleburgler has quit IRC17:49
alaskiwhat I'm thinking is that we could load from a config into a db on startup17:49
bauzasdansmith: that's really my question, do we envisage something orchestrating cells ?17:49
alaskibut have the db be what's actually used17:49
* bauzas not saying the word "Heat"17:49
belmoreiraalaski: I think that we should go only for one solution17:49
dansmithalaski: slightly more potentially confusing I think17:49
alaskibauzas: I don't17:49
dansmithyeah17:49
alaskiokay17:49
dansmithwe can change this later without too much trouble if it turns out to be a huge problem17:50
alaskibelmoreira: can you comment on the spec again with your thoughts17:50
*** armax has joined #openstack-meeting-317:50
belmoreiraalaski: sure17:50
alaskithanks17:51
mriedemanything left?17:51
alaskilet's bring the discussion back to the review, but maybe we're a bit closer now to consensus17:51
*** alexsyip has joined #openstack-meeting-317:51
alaski#topic open discussion17:51
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"17:51
bauzasalaski: yeah, as said, I'll amend my comment17:51
alaskibauzas: thanks17:51
alaskianything for open discussion?17:52
mriedemi'm hangry17:52
vineetmenon_alaski: do you have anything to do for minions (me) ? specifically in testing?17:52
mriedemlet's close17:52
vineetmenon_or specs, either17:52
mriedemvineetmenon: scour through the testing etherpad17:52
*** armax has quit IRC17:52
mriedemvineetmenon: alaski calls out the need for investigation into other failing tests17:53
alaskivineetmenon_: mainly we could use help understanding the current failures17:53
alaskithere's a review linked with the full logs17:53
*** melwitt has quit IRC17:53
vineetmenon_alaski, mriedem: okay17:53
alaskior I can put up some info on getting cells running in devstack17:53
alaskito run locally17:53
bauzasyeah, some instructions would be awesome17:54
mriedemalaski: don't you have a wip for that or something in devstack?17:54
*** melwitt has joined #openstack-meeting-317:54
vineetmenon_alaski: that I am able to, with local cell17:54
bauzaseverytime I'm changing something in the cell namespace, I'm crossing fingers... :/17:54
alaskivineetmenon_: cool17:54
alaskimriedem: it's just some localrc settings17:54
vineetmenon_region and child, right17:54
alaskidevstack does the rest already17:54
bauzasalaski: nova-net ?17:55
bauzasalaski: I beg your pardon, my knowledge is poor17:55
*** DuncanT has joined #openstack-meeting-317:55
belmoreirabauzas: yes17:55
bauzasbelmoreira: ack17:55
alaskialright, closing up early17:55
alaski#endmeeting17:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:56
openstackMeeting ended Wed Dec  3 17:55:59 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2014/nova_cells.2014-12-03-17.00.html17:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2014/nova_cells.2014-12-03-17.00.txt17:56
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2014/nova_cells.2014-12-03-17.00.log.html17:56
bauzasthanks17:56
alaskithanks everyone!17:56
vineetmenon_bye guys..17:56
*** Swami has joined #openstack-meeting-317:56
* bauzas heading off to dinner :)17:56
belmoreirathanks17:56
*** melwitt has quit IRC17:56
*** mriedem has left #openstack-meeting-317:56
*** dboik has quit IRC18:03
*** dboik has joined #openstack-meeting-318:04
*** emagana has joined #openstack-meeting-318:05
*** dheeraj-gupta-4 has left #openstack-meeting-318:05
*** Sukhdev has joined #openstack-meeting-318:06
*** tomoe_ has quit IRC18:06
*** VW_ has quit IRC18:08
*** vineetmenon_ has quit IRC18:08
*** belmoreira has quit IRC18:08
*** jacalcat1 has left #openstack-meeting-318:09
*** shwetaap has quit IRC18:11
*** markmcclain has joined #openstack-meeting-318:17
*** etoews_ has quit IRC18:18
*** hareeshpc has joined #openstack-meeting-318:18
*** dboik has quit IRC18:19
*** etoews has joined #openstack-meeting-318:19
*** cuddyt has joined #openstack-meeting-318:20
*** shwetaap has joined #openstack-meeting-318:21
*** RuiZang has joined #openstack-meeting-318:21
*** SumitNaiksatam has joined #openstack-meeting-318:23
*** LouisF has joined #openstack-meeting-318:24
RuiZangHi Sumit18:24
SumitNaiksatamRuiZang: hi18:25
*** etoews has quit IRC18:25
*** SridarK has joined #openstack-meeting-318:28
*** pc_m has joined #openstack-meeting-318:29
SumitNaiksatamSridarK: pc_m: hi18:29
pc_mhey18:30
SridarKSumitNaiksatam: pc_m: Hi18:30
vishwanathjhi18:30
SridarKvishwanathj: hi18:30
yalieHi Rui18:30
SumitNaiksatamlooks like we have most folks18:31
SumitNaiksatamlets get started18:31
RuiZangHi Yalei18:31
SumitNaiksatam#startmeeting Networking FWaaS18:31
openstackMeeting started Wed Dec  3 18:31:18 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:31
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:31
openstackThe meeting name has been set to 'networking_fwaas'18:31
SumitNaiksatam#info SPD: Monday 12-8-2014 SAD: Monday 12-15-201418:31
SumitNaiksatam#info Kilo-1 is 12-18-201418:31
SumitNaiksatamany other related announcements anyone would like to share for the benefit of the team?18:32
SumitNaiksatam#topic Bugs18:32
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:32
SridarKSumitNaiksatam: nothing new18:33
SumitNaiksatamSridarK: yes18:33
SumitNaiksatami did a quick review on this: #link https://review.openstack.org/#/c/104132/18:33
Swamihi18:33
SridarKSwami: hi18:34
SridarKSumitNaiksatam: yes u beat me to it - i was trying to understand when i saw ur review go by :-)18:34
SumitNaiksatamSwami: hi18:34
SumitNaiksatamSridarK: ah ok, do you disagree with the change?18:35
SridarKSumitNaiksatam: seems fairly straight forward18:35
SridarKSumitNaiksatam: no was just trying compare the change with the original18:35
SridarKSumitNaiksatam: it is good18:35
SumitNaiksatamSridarK: i thought the change was trying to make things consistent18:35
SridarKSumitNaiksatam: yes18:36
SumitNaiksatami however did not have a chance to actually test it out18:36
SumitNaiksatamit would be nice if some actually can18:36
*** armax has joined #openstack-meeting-318:36
SridarKSumitNaiksatam: i will try to get to this later today18:36
SumitNaiksatamSridarK: sweet18:36
SumitNaiksatami guess we are missing badveli not sure if anything showed up on his bug triage radar18:36
SumitNaiksatam#topic Docs18:37
*** openstack changes topic to "Docs (Meeting topic: Networking FWaaS)"18:37
SumitNaiksatami guess we have three pending items here18:37
*** armax has quit IRC18:37
SridarKSumitNaiksatam: yes - i could not even look at any of this trying to get specs out18:37
SumitNaiksatamSwami: anything for us to review or contribute in terms of DVR?18:37
SumitNaiksatamSridarK: np, that definitely is high priority too18:38
SwamiSumitNaiksatam: I have created a document for the documentation folks to consume.18:38
*** armax has joined #openstack-meeting-318:38
SwamiI have added a section for the services and added a high level note for all the services.18:39
Swami#link https://docs.google.com/document/d/1qmKoP4GVdjeEEVvqf3tYptVuvUzVIeQmJiTPWPoi_E0/edit18:39
SwamiIf you can take a look at the services part and if you feel like I have missed anything please fill in the gap.18:39
SwamiI am working with "Elke Vorgheise" on the documentation. I think she is the tech writer for the networking guide.18:40
*** banix has quit IRC18:40
SumitNaiksatamSwami: ah ok18:40
SumitNaiksatamthanks for the link18:40
*** hurgleburgler has joined #openstack-meeting-318:40
*** gholler_ has joined #openstack-meeting-318:40
*** bpokorny_ has joined #openstack-meeting-318:41
SridarKSwami: thx - overview on services covers major points - will see if we need to add any more details18:41
SumitNaiksatamSwami: perhaps we need to add some notes on the migration to the legacy mode (or the lack of when using FWaaS)18:41
SridarKSwami: over the the quick scan of the doc for DVR - looks really good and comprehensive18:41
SumitNaiksatambut the team here can this a little more detailed read, and provide feedback18:41
SumitNaiksatamSridarK: +1, great job Swami!18:42
SwamiYes, we can add a section on migration and how the services are handled.18:42
SwamiI will take a first stab at it and you can add your feedback or data to this document.18:42
SridarKSwami: i see a book deal coming :-) Swami signing DVR books at Vancouver :-)18:42
SwamiSumitNaiksatam: sure.18:42
SumitNaiksatamlol!18:43
SwamiSridarK: Sure, I like the idea.18:43
SumitNaiksatamSwami: also, conf is missing, not sure that is meant for this document thought18:43
SridarK:-)18:43
*** gholler__ has joined #openstack-meeting-318:43
*** bpokorny has quit IRC18:43
SwamiSumitNaiksatam: When you say config, are you talking about multinode config or single node config.18:44
*** gholler has quit IRC18:44
SwamiI think I had a section on configuration that deals with the DVR specific configurations.18:44
SumitNaiksatamyeah, and specifically in the context of FWaaS what needs to be set on which node18:44
*** etoews has joined #openstack-meeting-318:45
SumitNaiksatami dont think that is terribly different from the DVR base configuration, but i vaguely recall that we had one or two extra things in there18:45
SumitNaiksatamjust need to confirm18:45
SridarKSumitNaiksatam: i don't think we need to set anything specific for FWaaS18:45
SumitNaiksatamSridarK: okay18:45
*** yamahata has joined #openstack-meeting-318:45
SwamiFor DVR there is no specific action that is required for Firewall configuration. As far as the firewall service is enabled, it should work.18:45
*** yamamoto has joined #openstack-meeting-318:45
SridarKFWaaS just looks at the 'distributed' flag18:46
SumitNaiksatamnext doc item - #link https://bugs.launchpad.net/openstack-manuals/+bug/137367418:46
SumitNaiksatamSridarK: okay18:46
SumitNaiksatami am not sure if we need address the “openstack-api-site” related documentation18:46
SumitNaiksatamthird doc item was: #link https://bugs.launchpad.net/openstack-manuals/+bug/134698618:47
SumitNaiksatami believe there isnt an update on this18:47
*** gholler_ has quit IRC18:47
*** dboik has joined #openstack-meeting-318:47
SridarKSumitNaiksatam: not sure on that the second one - but i recall last week we saw that it was fixed18:47
SumitNaiksatamSridarK: it was fixed in one of the documents but it shows open in the other18:48
SridarKSumitNaiksatam: hmm ok18:48
SridarKsorry missed that18:48
SumitNaiksatamSridarK: if this doesnt swap out of my memory i will try to ping the guy :-)18:48
*** ivar-lazzaro has joined #openstack-meeting-318:48
SumitNaiksatam#topic Kilo Blueprints18:48
*** openstack changes topic to "Kilo Blueprints (Meeting topic: Networking FWaaS)"18:48
SumitNaiksatamwe have to post the blueprints by Dec 8th18:48
SridarKSumitNaiksatam: badveli just sent an email - he is running late18:49
SumitNaiksatamSridarK: thanks, yeah i saw that earlier, was hoping he would make it18:49
SumitNaiksatammake it before we get to security groups18:49
SumitNaiksatam*service groups18:49
RuiZangwhat do you mean by "post the blueprints by Dec 8th"?18:50
vishwanathjSumitNaiksatam, SridarK: I will upload a patch later today to address your comments18:50
SridarKI pushed some comments out on service groups a little early today18:50
SumitNaiksatamcommute is bad today!18:50
SumitNaiksatamRuiZang: i meant post a gerrit spec for review; i think you are good since you already posted your blueprint18:50
SumitNaiksatamvishwanathj: sure, np18:50
SumitNaiksatamSridarK: nice, i did not notice that18:51
SridarKSumitNaiksatam: mostly nits on service groups18:51
SumitNaiksatamso lets take one bp at a time18:51
SridarKSumitNaiksatam: oops sorry - are we on service groups ?18:51
RuiZangSumitNaiksatam> Oh OK18:51
*** yamamoto has quit IRC18:51
SumitNaiksatamlets start with hot spec of the day - FWaaS Insertion Model on a Single Router - #link https://review.openstack.org/#/c/138672/18:52
SridarK:-)18:52
SumitNaiksatamSridarK: your baby :-)18:52
SridarKSumitNaiksatam: thanks for the comments18:52
SumitNaiksatamhot spec puts you in the hot seat ;-P18:52
SridarK:-)18:52
SumitNaiksatamSridarK: sure18:52
SumitNaiksatamprobably folks havent had a chance to review it18:52
SumitNaiksatamplease do so and provide comments at the earliest18:52
SridarKSumitNaiksatam: i think i have tried to capture most of the discussions from the summit and also in the mtgs18:53
SumitNaiksatamthis is probably the most important bp/spec for FWaaS for Kilo18:53
SumitNaiksatamSridarK: and very articulated at that!18:53
SridarK:-)18:54
*** badveli has joined #openstack-meeting-318:54
badvelihello all18:54
badvelisorry delayed due to weather18:54
SridarKI am hoping that if we get most things thrashed out this week - next week can get some core attention18:55
SridarKbadveli: hi18:55
SumitNaiksatambadveli: yes, glad you could make it, and pretty much at the right time18:55
badvelihello sridark18:55
badvelioh..thanks18:55
SridarKSumitNaiksatam: of course thanks of the core attention from u18:55
SridarK*for18:55
SumitNaiksatamSridarK: yeah, i would say we pre-emptively approach some of the other cores18:56
SridarKSumitNaiksatam: ok sounds good - will do that18:56
SumitNaiksatamSridarK: i think we should add all the cores to the review18:56
SumitNaiksatamSridarK: you want me to do that?18:56
*** rcleere is now known as rcleere_away18:56
SridarKSumitNaiksatam: ok sure18:56
SumitNaiksatamSridarK: ok done :-)18:56
SumitNaiksatamdid anyone else get a chance to look at Sridar’s spec?18:57
SumitNaiksatamin case we want to spend a few mins discussing here18:57
SridarKSumitNaiksatam: definitely want to thrash out some of the extensions related areas - i have left that a bit open as i am not sure how to proceed there with all the changes18:57
badvelijust going through18:57
SumitNaiksatamis glebo here?18:58
badvelino i do not see him here18:58
SumitNaiksatamthe next bp is Service group and Service Object for firewall as a service: #link https://review.openstack.org/#/c/13159618:58
SumitNaiksatambadveli: looks like we again have some formatting and grammar nit issues18:59
SridarKbadveli: i provided some comments earlier today18:59
*** dboik has quit IRC18:59
SumitNaiksatamlooking at SridarK’s comment18:59
SumitNaiksatam*comments18:59
SumitNaiksatamideally we should have been way past this point now18:59
SridarKbadveli: mostly looks good except for the nits18:59
badvelitaking a look18:59
*** emagana has quit IRC19:00
SumitNaiksatambadveli: did you or glebo hear from any of the other cores that glebo had approached to review this?19:00
*** dboik has joined #openstack-meeting-319:00
*** emagana has joined #openstack-meeting-319:00
badveliwe did not get anything19:00
badveliwe are still waiting19:00
SumitNaiksatambadveli: hmmm19:00
SumitNaiksatambadveli: once you get a new rev out, i will review immediately19:01
*** Sukhdev has quit IRC19:01
SridarKbadveli: possibly the 2 issues i have listed - if u change the wording on that or clarify and with the nits fixed - i am good19:01
SumitNaiksatambadveli: would appreciate if you can send a headup when you do to the entire team19:01
*** emagana_ has joined #openstack-meeting-319:01
*** dthakkar has joined #openstack-meeting-319:01
SumitNaiksatam*headsup19:01
badveliok19:01
badvelii will give a heads up on the new review19:02
SumitNaiksatamthe third bp is regarding FWaaS for E-W traffic when deploying DVR19:02
SumitNaiksatambadveli: thanks19:02
SumitNaiksatamSwami sent out a proposal last week: #link https://docs.google.com/document/d/11Gp62Yfyi1WH6yM6E_308OB4CC9A6xhxKZJ8B5jOwLc/edit19:02
SumitNaiksatamand we had a brief discussion19:02
*** baoli has quit IRC19:03
SumitNaiksatamSwami: have you identified a preferred path in terms of what is feasible on the DVR side of things?19:03
*** dthakkar_ has joined #openstack-meeting-319:03
SwamiSumitNaiksatam: I was counting on vivek to give me some feedback on proposal 1.19:03
*** mwagner_lap has quit IRC19:03
SumitNaiksatamSwami: ah ok19:03
SwamiBut he was busy on something else.19:03
SumitNaiksatamso i am a bit concerned that we are cutting too close to the SPD, since we dont have a spec in place yet19:04
SumitNaiksatamhow do we want to go about pursuing this?19:04
SwamiSumitNaiksatam: So I have to take up the task to investigate the pros and cons of option 1>19:04
SwamiOption 2: is prety much straight forward and DVR will not have any impact.19:04
SwamiBut I personnally like option1 since the firewall rules will be in one single place.19:04
*** emagana has quit IRC19:04
badveliyes swami, i think option 1 is looking good19:05
SumitNaiksatamwe need to firm on both - (1) the technical path that we want to take, and (2) the logisitics of who will post the spec19:05
SwamiDid you guys do a round table discussion on both options? If so what do you like or see as a valuable going forward.19:05
*** dthakkar has quit IRC19:05
SumitNaiksatamon (2) we need to decide whether we need 2 specs (one for DVR and another for FWaaS) or 119:05
SumitNaiksatamSwami: a  meeting dedicated to this would definitely be helpful, lets take that offline and set up one for the earliest19:06
*** rcleere_away is now known as rcleere19:06
SridarKSumitNaiksatam: Swami: Yes i think that will be good19:06
SwamiIn either case, if we choose either of the options mentioned above, this addition of a new bridge or addition of a new rule to redirect the packets to the router should only happen if there is a firewall enabled.19:06
SumitNaiksatam#action SumitNaiksatam to setup DVR E-W traffic discussion meeting19:06
SumitNaiksatamSwami: so seems like we are shooting for two specs?19:07
SwamiSumitNaiksatam: Yes I agree with you on having a separate chat on this.19:07
*** yamahata has quit IRC19:07
SwamiSumitNaiksatam: No at this point let us keep the implementation decision out of the spec.19:07
*** safchain has quit IRC19:07
SwamiLet us file a blueprint of applying the firewall rules for the DVR East-West.19:08
SwamiI don't think we are going to introduce any API change at this time or any database change for this feature.19:08
*** baoli has joined #openstack-meeting-319:09
SridarKSwami: A sort of tangential but related question19:09
SumitNaiksatamSwami: okay lets discuss further in the meeting19:09
badvelito me it lloked like option 1  is better19:09
SwamiYes sounds good.19:09
SumitNaiksatamSwami: do you think Vivek needs to attend the meeting or you would sync up offline with him? (that will help to set the time for the meeting)19:09
*** gholler_ has joined #openstack-meeting-319:09
SumitNaiksatambadveli: Swami: yes i agree19:09
SridarKSwami: With DVR is there some significance for an  interface that carries the E -W traffic ?19:10
badveli thanks sumit19:10
SwamiSumitNaiksatam: Yes I will investigate it further and if we need viveks help we can pull in as required. He seems to busy in some other work.19:10
*** baoli has quit IRC19:10
SridarKSwami: or is the interface just a logical entity and we cannot discriminate or associate E - W traffic with a specific Router interface ?19:11
SumitNaiksatamSwami: okay some i am shooting for 9 AM PST tomorrow (if that works for everyone)19:11
*** MaxV has joined #openstack-meeting-319:11
SwamiSridarK: I don't think there is any significane on interface that is driving traffic for E-W. But we can easily sort out there are different ports that direct traffic for North-South and for East-West.19:11
badveli19:11
SwamiTomorrow 9 a.m should work.19:11
badveli19:12
badveli  sumit, can we do a bit late19:12
vishwanathj9AM PST works19:12
SridarKSwami: ok lets discuss more on this, i am trying to think in terms of the router insertion work that we are planning to see if we can leverage that for handling this case19:12
SridarKSumitNaiksatam: i am okay with any time in the morning19:13
*** gholler has joined #openstack-meeting-319:13
SwamiSridarK: Yes we can discuss this in futher details in the meeting tomorrow.19:13
*** gholler__ has quit IRC19:13
SumitNaiksatamokay i will send out an invite accordingly19:14
SumitNaiksatamnext vendor blueprints19:14
badveli       i have a doctor appointment in the morning19:14
SumitNaiksatambadveli: okay lets discuss offline19:14
badveli  i will try to attend it19:14
SumitNaiksatamwe currently have only one vendor spec posted on the wiki: #link https://wiki.openstack.org/wiki/Meetings/FWaaS#Vendor_Blueprints19:15
SridarK#link https://review.openstack.org/#/c/129836/19:15
SumitNaiksatamhowever we have at least a couple of more19:15
SumitNaiksatamSridarK: ah i guess we need to update the link19:15
RuiZangDo I have to post the review on wiki by myself?19:15
*** gholler_ has quit IRC19:15
SridarKSumitNaiksatam: ok will do19:15
SumitNaiksatamvishwanathj: RuiZang: can you update the wiki page19:15
RuiZangSorry, I am totallynew to this19:15
RuiZangSure, I can19:15
SumitNaiksatamRuiZang: no worries, it wil be great if you can update the wiki19:15
vishwanathjSumitNaiksatam, will update19:16
*** gholler_ has joined #openstack-meeting-319:16
SumitNaiksatamRuiZang: this not a required step, its a nice to have since it will be visible to other FWaaS team member for ready reference and they can provide reviews19:16
SridarKRuiZang: pls feel free to reach out if u have any questions19:16
SumitNaiksatamwe will also track every week19:16
SumitNaiksatamRuiZang: i did a quick read through, and provided a couple of high level comments19:16
SumitNaiksatamRuiZang: but mostly looks good to me19:17
RuiZangSumitNaikstam: Sridark: thanks you guys, I will update the wiki19:17
*** MaxV has quit IRC19:17
SumitNaiksatamRuiZang: are you the one shepherding this spec or is it isaku?19:17
RuiZangIsaku is on relocation to U.S19:17
SumitNaiksatamRuiZang: sorry, i know you have two specs19:17
RuiZangSo currently it is me19:17
SumitNaiksatamRuiZang: i was referring to the first one, which is the L3 plugin19:17
SumitNaiksatamRuiZang: i have not yet read through the fwaas driver19:18
RuiZangSumitNaiksatam: yes I am responsible for both of them19:18
SumitNaiksatamRuiZang: great19:18
*** MaxV has joined #openstack-meeting-319:18
SumitNaiksatamRuiZang: as SridarK mentioned please feel free to reach out to this team if you need any help19:18
SumitNaiksatamvishwanathj: any blockers for your spec?19:19
*** gholler has quit IRC19:19
RuiZangSumitNaiksatam: Sridark: Sure, thanks very much19:19
vishwanathjSumitNaiksatam, None at this time, I need to upload the next patch set addressing SridarK and your comments19:19
SumitNaiksatamvishwanathj: ok great19:20
SumitNaiksatambtw, Spec for introducing Brocade Vyatta Firewall solution using a new vendor specific device driver for Neutron L3 agent: #link https://review.openstack.org/13695319:20
SumitNaiksatamand Ruiz’s specs are: l3-router: add mcafee ngfw l3 router plugin #link https://review.openstack.org/13419819:21
vishwanathjSumitNaiksatam, I have updated the wiki and added link to brocade vyatta firewall spec19:21
SumitNaiksatamand, firewall: add mcafee ngfw driver support: #link https://review.openstack.org/#/c/91286/19:21
SumitNaiksatamvishwanathj: nice, thanks!19:21
SumitNaiksatamthe other blueprint/work we need to discuss with high priority is the L3 agent refactoring19:22
SumitNaiksatam#topic L3 Agent refactoring19:22
*** openstack changes topic to "L3 Agent refactoring (Meeting topic: Networking FWaaS)"19:22
*** dboik has quit IRC19:22
*** dboik has joined #openstack-meeting-319:22
*** sarob has joined #openstack-meeting-319:23
SumitNaiksatam#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/restructure-l3-agent,n,z19:23
SumitNaiksatamthis will affect the firewall agent19:23
SumitNaiksatamso just want to confirm who signed up for this19:24
SumitNaiksatamSridarK: was it you and pc_m?19:24
pc_myup19:24
SumitNaiksatampc_m: okay great, thanks!19:24
pc_mI'm doing VPN19:24
SumitNaiksatampc_m: ah okay19:24
pc_mAnd have started on the refactoring.19:24
SumitNaiksatampc_m: who is doing firewall?19:24
pc_mI thought SridarK signed up.19:25
SumitNaiksatampc_m: okay19:25
SumitNaiksatambadveli: i vaguely recall glebo mentioning that you were going to look at this too19:25
SumitNaiksatampc_m: i am guessing that the scope of this work in the context of fwaas is pretty limited, right?19:26
badveli  sumit, i am planning to do the e-w spec side19:26
SumitNaiksatambadveli: ah okay, got it19:26
pc_mSumitNaiksatam: yes.19:26
badveli i will get the details from pc_m19:26
pc_mSumitNaiksatam: Mostly will be determining the hook points for L3 agent notifications to the services19:27
*** SridarK_ has joined #openstack-meeting-319:27
SumitNaiksatampc_m: right19:27
*** sarob has quit IRC19:27
badveli19:27
SumitNaiksatami think we lost SridarK for a bit there19:27
SridarK_sorry network glitch19:27
pc_mSumitNaiksatam: And of course, teasing apart the inheritance tree19:27
SumitNaiksatamSridarK: np19:27
pc_m#link https://review.openstack.org/#/c/13153519:28
pc_mIs the BP spec.19:28
SumitNaiksatamSridarK: we were discussing the l3 agent refactor and its implications for the fwaas agent19:28
Swamipc_m: is there design doc for this hook points19:28
SumitNaiksatamSridarK: trying to nail down who signed up for this at our end19:28
SumitNaiksatamSridarK: did you?19:28
SridarK_on this L3 refactor, Carl pinged me on the fwaas side to see if i can take a look - so will look into that19:28
pc_mSwami: no. There was some discussion on the ML and some info in the BP19:28
SridarK_SumitNaiksatam: so i have signed up19:28
pc_mPlease look at the BP spec and comment from a FW POV19:29
* pc_m just check - it's approved19:29
SumitNaiksatampc_m: yeah, was going to say :-)19:29
pc_mStill would give the main points.19:29
*** matrohon has joined #openstack-meeting-319:30
SumitNaiksatamso i think we proposed  in the adv services’ meeting yesterday we will target this for Kilo-219:30
SumitNaiksatamok folks we are out of time19:30
SumitNaiksatamhope we didnt miss anything19:30
SumitNaiksatamthanks for joining19:30
*** SridarK has quit IRC19:30
SumitNaiksatambye!19:30
SumitNaiksatam#endmeeting19:30
SridarK_bye19:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:30
openstackMeeting ended Wed Dec  3 19:30:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-12-03-18.31.html19:30
SwamiSumitNaiksatam: SridarK_ : pc_m : I have a suggestion19:30
badveli  bye19:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-12-03-18.31.txt19:30
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-12-03-18.31.log.html19:30
SridarK_Swami: yes pls19:30
SumitNaiksatamSwami: sure19:31
SwamiI have this patch up for review again.19:31
SwamiThis is the services check for migration.19:31
SridarK_Swami: on my list19:31
SwamiCan you guys review it again.19:31
SumitNaiksatamSwami: the one i had +2’ed earlier? :-)19:31
SwamiOur mgiration patch already merged.19:31
SwamiBut this one was left out.19:31
Swami#link https://review.openstack.org/#/c/123273/19:32
Swamipc_m: I saw your comment, but this exception message is specific to migration.19:32
SwamiSumitNaiksatam: Yes.19:32
SwamiI had to rebase it because of the parent patch got merged and changed a little bit.19:32
Swamithat's all I had.19:33
SumitNaiksatamSwami: sure19:33
*** vishwanathj has quit IRC19:33
SwamiSumitNaiksatam: thanks19:34
*** MarkAtwood has joined #openstack-meeting-319:34
pc_mSwami: OK. Did you have resolution on the check_router_in_use()?19:34
* pc_m should we go to openstack-neutron?19:34
Swamipc_m: As I mentioned in my comment, I did go that route, but the exception message was not specific to the action and that's why I moved in this direction.19:34
SumitNaiksatambtw, there is a #openstack-fwaas channel19:35
pc_mSwami: Reading... I see. Will respond.19:35
SumitNaiksatamand i am the only one on it right now! :-)19:35
Swamiok.19:36
*** neillc has joined #openstack-meeting-319:36
Swaminothing else. Thanks for your time.19:36
*** jacalcat has joined #openstack-meeting-319:36
badveli  thanks all19:36
Swamibye19:36
badvelibye19:37
*** jemangs_ has quit IRC19:37
*** pc_m has left #openstack-meeting-319:37
*** shwetaap has quit IRC19:37
*** jemangs has joined #openstack-meeting-319:38
*** sergef has joined #openstack-meeting-319:39
*** gholler__ has joined #openstack-meeting-319:40
*** Swami has left #openstack-meeting-319:40
*** cuddyt has quit IRC19:40
*** mestery is now known as mestery_afk19:42
*** gholler has joined #openstack-meeting-319:43
*** sarob has joined #openstack-meeting-319:43
*** sarob has quit IRC19:44
*** dboik has quit IRC19:44
*** dboik has joined #openstack-meeting-319:44
*** gholler_ has quit IRC19:44
*** gholler__ has quit IRC19:45
*** dboik has quit IRC19:46
*** armax has quit IRC19:47
*** SridarK_ has quit IRC19:49
*** armax has joined #openstack-meeting-319:51
*** mwagner_lap has joined #openstack-meeting-319:51
*** Longgeek has quit IRC19:54
*** r1chardj0n3s has joined #openstack-meeting-319:54
*** RuiZang has quit IRC19:55
*** markvoelker has joined #openstack-meeting-319:55
*** ongk has joined #openstack-meeting-319:56
*** TravT has joined #openstack-meeting-319:56
*** hareeshpc has quit IRC19:56
*** hareeshpc has joined #openstack-meeting-319:57
*** hareeshpc has quit IRC19:57
*** armax has quit IRC19:57
*** rbertram has joined #openstack-meeting-319:59
david-lyle#startmeeting Horizon20:00
openstackMeeting started Wed Dec  3 20:00:01 2014 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: Horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
david-lyledid anyone make the new time?20:00
mrungemorning20:00
rbertramhey20:00
TravTHello!20:00
neillcI did :)20:00
r1chardj0n3shi david-lyle :)20:00
mrungeand no, nobody made it ;-)20:00
*** doug-fish has joined #openstack-meeting-320:00
r1chardj0n3scoffee's on the stove :)20:00
rbertramr1chardj0n3s is on a bit earlier than usual20:00
mrungeanybody tea?20:01
clu_hi!20:01
lhchengo/20:01
*** dboik has joined #openstack-meeting-320:01
clu_(not looking forward to waking up at 4 am next week ;p)20:01
david-lylelet a few more roll in20:01
TravTmrunge: I'll take some.20:01
david-lyleI see tqtran is still good with time20:02
david-lylealright, let's get rolling20:02
david-lyleFirst a general announcement, I've heard back from a majority of cores and would like to formally welcome Thai and Cindy to horizon-core20:03
david-lyleThank you for all your efforts!20:03
r1chardj0n3s\o/20:03
clu_thanks david-lyle!20:04
neillccongrats Thai and Cindy!20:04
doug-fishcongrats clu_ and Thai!20:04
clu_i'm accepting on behalf of tqtran because he's traveling right now :)20:04
TravTCongratulations!20:04
rbertramcongrats!20:04
asahlinCongrats!20:04
lhchengcongrats!20:04
*** dboik has quit IRC20:04
*** dboik has joined #openstack-meeting-320:05
david-lyleI'll make all the appropriate group, role, list, etc changes in the next day or so20:05
clu_:)20:05
david-lyleBeyond that, I still have a stable branch liaison slot open for the #link https://wiki.openstack.org/wiki/CrossProjectLiaisons20:06
david-lyleI and many others were thinking mrunge you might be interested20:06
david-lyledo you have time and interest20:06
mrungeheh20:06
david-lyleand what it entails, I don't full know20:06
mrungeyes, I can do that20:06
*** SridharRamaswamy has quit IRC20:06
david-lylecan you pencil yourself in on the wiki page please?20:07
david-lyleand thank you20:07
david-lyleI think you're the only other stable team member we have on Horizon, so it makes sense20:07
mrungedavid-lyle, yes, will do that20:07
*** dboik has quit IRC20:07
*** badveli has quit IRC20:07
david-lyleBeyond that, Kilo-1 is on Dec 1820:07
*** dboik has joined #openstack-meeting-320:08
david-lyle#link https://launchpad.net/horizon/+milestone/kilo-120:08
*** esp has joined #openstack-meeting-320:08
david-lyleI think everything is on track, except maybe the split20:08
david-lylebut I think we have an agenda item to dig into that in a bit20:09
mrungeyes, exactly20:09
david-lyleso we'll hold off on diving in yet20:09
r1chardj0n3swe still haven't settled on a colour20:09
david-lyleit will only take approx 90 emails to narrow it down20:10
david-lylewant to start that one too r1chardj0n3s?20:10
*** TravT has quit IRC20:10
r1chardj0n3sdavid-lyle: for k-1, I think tqtran wanted to try to get the identity rework in20:10
*** TravT has joined #openstack-meeting-320:10
david-lyler1chardj0n3s: doesn't it involve new dependencies?20:11
r1chardj0n3sdavid-lyle: not yet20:11
r1chardj0n3sdavid-lyle: (and unlikely to)20:11
david-lylewhat about the external js reference20:11
david-lyleor did that get removed?20:11
r1chardj0n3sdavid-lyle: though we haven't got a solid outcome from the bower discussion which would involve new deps20:12
david-lyleI can't merge in links to random js from the web20:12
r1chardj0n3sright, ok20:12
r1chardj0n3sso yes, new deps20:12
david-lylea lot of people run behind firewalls that prevent such things20:12
r1chardj0n3syep20:13
mrungeor build systems not connected to the net20:13
mrunge;-)20:13
david-lyleok, we'll hope for K-1, if not k-2 is just the next day :)20:13
r1chardj0n3s:)20:13
r1chardj0n3sfine by me20:13
david-lyleOpenStack where the milestones are meaningless, but help keep time20:13
r1chardj0n3s(I was wondering what they were for :)20:14
david-lylewell, meaningless is an overstatement20:14
david-lylebut fairly apt20:14
david-lyleI don't have any other general items20:14
*** markmcclain has quit IRC20:15
david-lyleso the agenda for today can be found at #link https://wiki.openstack.org/wiki/Meetings/Horizon20:15
*** EmilyW has joined #openstack-meeting-320:15
david-lyle#topic Moved blueprint review list20:15
*** openstack changes topic to "Moved blueprint review list (Meeting topic: Horizon)"20:15
david-lyleThat's mine20:15
david-lyleI created a wiki page to track bps for review20:16
david-lylethat's the good news20:16
david-lylethe second part with adding a new list didn't happen yet20:16
david-lyleso stay tuned20:16
david-lylei think most of those on the current list are ready to approve and schedule20:16
david-lyleso I'll start doing that20:17
*** Sukhdev has joined #openstack-meeting-320:17
rbertramI've been thinking about basing filtered-client-side-table BP on the Angular work by tqtran and r1chardj0n3s, but I noticed that there is no angular BP. Thoughts?20:17
r1chardj0n3srbertram: the angular work is tied into the identity bp ... https://blueprints.launchpad.net/horizon/+spec/angularize-identity-tables20:18
mrungeis it still too early for a bp for all that angular stuff?20:18
r1chardj0n3sdavid-lyle: that should be added to the list pls20:18
r1chardj0n3s(or should go through whatever process is appropriate to get onto the list pls :)20:18
rbertramr1chardj0n3s: tqtran suggested I start with users rather than instances, since it is easier. Still considering.20:19
r1chardj0n3srbertram: yep, that BP is users20:19
david-lyleadded to the page20:19
r1chardj0n3srbertram: there's a half-dozen changesets already hanging off that bp, and will likely be a few more before we're done20:19
david-lyleforgot to link the page #link https://wiki.openstack.org/wiki/Horizon/Blueprint_Reviews20:19
*** TravT_ has joined #openstack-meeting-320:20
TravT_It would be great if we could land that sooner than later20:20
rbertramr1chardj0n3s: what's your point? that it won't stabilize soon enough?20:21
r1chardj0n3sagreed20:21
TravT_because right now your rest utlitity is in that patch20:21
r1chardj0n3sbut the individual changes can be merged along the way, yes?20:21
david-lyleseparate patches on the same bp can merge at any time20:21
david-lyleso the rest work should go first20:21
*** ChuckC has quit IRC20:21
r1chardj0n3srbertram: it's partly that, but also that there's a couple of puzzle pieces missing, most notably the packaging20:21
david-lylethat unblocks several others20:22
rbertramThe rest utility will be very handy for the fitlered-client-side-table20:22
r1chardj0n3sagreed, hence I've an agenda item to discuss it ;)20:22
david-lyle+1 foresight20:22
TravT_ok, will digress until then20:22
david-lylealright, just to close on the current topic, the best way to get your bp for review is to schedule it for a milestone20:23
*** TravT has quit IRC20:23
david-lylemoving on20:23
david-lyle#topic Repo split and names20:24
*** openstack changes topic to "Repo split and names (Meeting topic: Horizon)"20:24
david-lylemrunge: was that yours?20:24
mrungeah yes, that'll be me, I guess20:24
mrunge;-)20:24
david-lylelucky you20:24
mrungewe still don't have names20:24
TravT_Maybe a dumb question, but won't this repo split mean we can't have dependent patches in Gerrit across them?20:24
r1chardj0n3suse the github random name generator20:25
david-lyleTravT_: yes20:25
mrungeTravT_, you're right20:25
TravT_uggh20:25
mrungeand when splitting the repo, we will have to sync contributions to horizon and openstack_dashboard20:25
mrungemeaning: slowing down the process20:25
TravT_to be that annoying guy asking yet again... why are we doing this?  just to simplify packaging?20:26
mrungewhen we decided to split, we thought, horizon (the module) is settled20:26
david-lylemrunge: I ultimately think splitting the repo is the right thing to do, but I worry we'll cause more turmoil than it's worth20:26
mrungeTravT_, we're doing this, because horizon (the module) is useful outside of OpenStack20:26
*** ycombinator_ has joined #openstack-meeting-320:27
mrungedavid-lyle, I have two issues with the split currently20:27
mrungeor even more20:27
david-lyleand I like to waffle on things20:27
r1chardj0n3shas anyone proposed an alternative, which is to just merge them? is anyone actually using horizon-the-module outside of openstack?20:27
*** Piet has joined #openstack-meeting-320:27
david-lyler1chardj0n3s: used to be they wanted to, but had to pull on openstack_dashboard too20:28
mrunger1chardj0n3s, we had so many folks coming up, saying: this is useful20:28
david-lyles/on/in/20:28
r1chardj0n3scool, was just wondering :)20:28
mrungewhen continuing on the route having a django app, this is just the right thing to do20:28
mrungebut: given we're throwing everything away, I could use my time better20:29
*** markmcclain has joined #openstack-meeting-320:29
david-lyleoption 3, fork horizon-lib onto github and continue dismantling the part remaining in horizon.git20:29
*** hareeshpc has joined #openstack-meeting-320:29
r1chardj0n3sooh, I like the sound of that20:29
mrungehmm, sounds good.20:30
mrungehow would that part be updated?20:30
david-lylewhich part?20:30
mrungeor do we accept, horizon-lib and integrated horizon-lib diverting?20:30
mrungeI mean, forked off horizon-lib?20:31
r1chardj0n3sI do have a concern about the new angular work landing in the horizon "lib" ... if they're truly independent components (independent of openstack_dashboard) then I believe they should be truly separate things out of horizon-lib otherwise no-one in the angular space will ever consider using them20:31
david-lyleI think we accept divergence and if something useful goes into horizon-lib, we create a patch by hand20:31
mrungeugh.20:31
mrungeI fear, we will just loose interest in horizon-lib20:32
mrungeand that part becomes abandoned more sooner than later20:32
*** obondarev_ has joined #openstack-meeting-320:32
*** dconde has quit IRC20:33
mrungeso, to make a plan here:20:33
mrunge1. do we still want this?20:33
mrunge2. names? everybody ok with horizon (for horizon lib) and openstack_dashboard?20:33
mrunge3. when?20:33
david-lyleI take 2. sure20:34
doug-fishwith regard to 1, I haven't seen the need for this.  Everyone I interact with who wants to extend Horizon wants some/all of the dashboard panels as well.20:34
*** peristeri has quit IRC20:34
doug-fishbut that could just be me and the sort of people I interact with.20:34
david-lyledoug-fish: the need in the past was greater because we didn't have the plugin story worked out yet20:34
*** obondarev has quit IRC20:35
TravT_on 1), I'd ask what is the primary intent of the dashboard program?  Is it to provide a framework for other UIs or to provide a dashboard for Horizon?  Or maybe that's too much of a simplification.20:35
david-lyleand extending horizon was take the code and heavily edit openstack_dashboard or replace it20:35
mrungeyes, the request to split was louder in the past20:35
mrungenow those folks moved on (or so)20:35
doug-fishIMO providing a framework is a big job by itself.  I feel like we are stretched thin already.20:36
david-lylemrunge: have you tried using horizon-lib outside of Horizon?20:36
mrungedavid-lyle, nope, I haven't20:36
david-lyleI'm wondering if there are actually enough pieces there20:36
mrungedue lack of time :(20:36
david-lyleunderstood20:36
*** hareeshpc has quit IRC20:36
david-lyleI think my vote is to drop the split20:37
mrungeI wouldn't be sad or unhappy, if we just drop it20:38
david-lyleI think doing the split could be beneficial to some people, but ultimately will hurt us more than it helps them20:38
david-lyleanyone else?20:39
TravT_so, we've used the horizon framework in HP a few times and it keeps coming up... but TBH I don't know that status on a clear statement of intent on using it as a standalone framework.20:39
david-lyleanymore, I think it's just a framework to operate inside OpenStack20:40
*** thangp has quit IRC20:40
david-lylelike an oslo library20:40
david-lyleI don't think competing OpenStack UIs will be using horizon-lib20:40
mrungedavid-lyle, it was intended to provide a framework to build a dashboard based on restful services20:40
david-lylemrunge: I understand that, but that was why I asked if anyone had tried20:41
david-lyleI'm wondering if you really can20:41
mrungeit's not necessarily connected to OpenStack at all...20:41
david-lyleas written20:41
mrungeagreed.20:41
david-lylethen you start a ton of refactoring to make it work as such which ripples through the openstack_dashboard20:41
mrungeI think Gabriel had a demo20:41
TravT_to that point, a lot of the current movement is putting RESTful APIs into OpenStack Dashboard.20:41
david-lyleof extending horizon.git20:42
TravT_and a clear pattern is just emerging.20:42
mrungeputting restful apis into openstack_dashboard is just... silly20:42
r1chardj0n3smrunge: could you explain that pls?20:43
mrunger1chardj0n3s, we already have apis in place, why do we write software to access them?20:43
mrungeor to provide those restful apis another time?20:44
r1chardj0n3sthe APIs are ... imperfect :)  openstack_dashboard has a bunch of code that makes the underlying APIs far nicer to consume20:44
mrungeso, you're hacking around those imperfect apis rather than fixing them?20:44
r1chardj0n3sso it made sense to leverage that and provide a new API on top, rather than rewrite everything in the consumer layer (ie javascript)20:45
*** crobertsrh has joined #openstack-meeting-320:45
mrungewow.20:45
*** LouisF has quit IRC20:45
r1chardj0n3smrunge: I don't control those apis, and the imperfections often have been fixed through versioning, but old versions still exist in production20:45
r1chardj0n3sopenstack_dashboard's api code often just smooths over differences between api versions20:45
mrunger1chardj0n3s, I understand your issue. still I don't like the solution20:45
mrungeas it's not that clean as I'd like it20:46
r1chardj0n3smrunge: oh, I'm not thrilled by it either20:46
r1chardj0n3smrunge: but in the interest of being practical about it, and choosing battles etc...20:46
r1chardj0n3swe have enough to do already :)20:46
mrunger1chardj0n3s, or anyone else: I'm not saying, anyone is doing a bad job20:46
*** sergef has quit IRC20:47
mrungeon the other side, I would try to prevent those compromises20:47
rbertramI think the existing APIs are consuming REST from keystone and other services. r1chardj0n3s is providing REST to browser. Seems like they APIs are looking in different directions. r1chardj0n3s: true?20:47
neillcmrunge: unfortunately compromises seem to be unavoidable20:47
mrungerbertram, something which could be fixed by a proxy, right?20:48
neillcIt's perhaps a matter of picking the least worst option :)20:48
mrungeneillc, I'm expecting those compromises to live forever20:48
r1chardj0n3sthere existing code in openstack_dashboard (ok, that's a *lot* to keep typing ;) is client code over the service APIs (keystone, nova) and the REST API in "Horizon" (aka openstack_dashboard) is built over that client code20:48
r1chardj0n3syou can't just "fix if with a proxy" .. go have a look at the complexity in the openstack_dashboard/api directory20:49
mrunger1chardj0n3s, I did20:49
rbertrammrunge: yeah - we are winding up w/ a proxy, which does more than passthrough - does processing between keystone and browser20:49
r1chardj0n3sif you replace that code with a proxy, you have to rewrite all that code in Javascript, which we're trying to avoid20:49
r1chardj0n3sand the proxy still has to do some processing, as anyone who's written one finds out :)20:49
TravT_There is also the whole notion of making incremental progress in client side code which can be done each release.20:50
mrungeare we slowly progressing to the next topic?20:50
mrungedavid-lyle, ?20:50
david-lylewe seemed to have jumped yes20:51
david-lyleso we'll skip one and20:51
mrungeshortly back to split: it's cancelled?20:51
*** vishwanathj has joined #openstack-meeting-320:51
david-lyle#topci State of REST API - how much should be implemented20:51
david-lyle#topic State of REST API - how much should be implemented20:51
*** openstack changes topic to "State of REST API - how much should be implemented (Meeting topic: Horizon)"20:51
david-lyleand go20:51
TravT_mrunge: maybe "tenatively postponed"?20:52
r1chardj0n3scurrent REST API WIP is at https://review.openstack.org/#/c/136676/1920:52
david-lyleI don't think we can take another postponement20:52
mrungeTravT_, well, up to the point, that it doesn't make sense any more?20:52
david-lylemrunge: unless you really want to drive it, I think we should forget it20:53
r1chardj0n3sat this point, it seems uncontroversial, and it implements enough to support the identity angular work, but it's obviously not a "complete" API  and certainly doesn't have a complete unit test coverage20:53
doug-fish+1 on cancelling the split20:53
r1chardj0n3sso, how much more should be done on it before it's merged so others can start work on fleshing it out to their needs?20:53
*** gholler_ has joined #openstack-meeting-320:54
david-lyler1chardj0n3s: certainly needs tests before merging, but beyond that it doesn't need to be complete20:54
r1chardj0n3sdavid-lyle: so, full test coverage of the code as-is20:55
r1chardj0n3sI was also mulling over how this new API is to be documented20:55
doug-fishjust to be clear, we aren't really going to create an "API" are we?  Like with stability?  We just want an interface for our code.20:56
TravT_doug-fish: +120:57
mrunge:D20:57
mrungemy point!20:57
rbertramdoug-fish: meaning we don't want 3rd parties to use it?20:57
doug-fishright20:57
r1chardj0n3shm20:57
TravT_mrunge: ahh! now I see your point.20:57
doug-fishwe want to retain full rights to change this often and without warning20:57
r1chardj0n3syep20:57
*** gholler has quit IRC20:57
*** sunnyr has joined #openstack-meeting-320:58
r1chardj0n3ssorry mrunge I totally didn't catch that from what you were saying!20:58
r1chardj0n3syes, the intention is that this API exists to support Horizon-the-angular-application20:58
r1chardj0n3sand should be free to change to suit that purpose without repurcussion20:58
david-lylenothing else20:58
r1chardj0n3syep20:58
TravT_+10020:59
david-lyleyes, we're not publishing an API20:59
DuncanTApologies for butting in, but there's only a few minutes left. We added an API to cinder to allow the policy for the current tenant to be cheacked via REST. This was suggested by a Horizon dev at the cinder mid-cycle meetup. The link is in the minutes, and there's a discussion thread on openstack-dev but no feedback yet. We believe it is good enough to allow20:59
DuncanTthe CLI to offer better help etc, but wondered if you guys could cast an eye over it before we merged it?20:59
david-lyleDuncanT: I will take a look20:59
DuncanTThanks20:59
DuncanTI'm thinking about proposing it for other projects if it seems useful21:00
david-lyleDuncanT: my main concern would be fragmentation across services, but let me look in more detail21:00
r1chardj0n3sok, so in terms of documenting the API, how about I try to set some good docstring pracises in the patch I'm authoring and we'll try to hold people to that?21:00
david-lyleah, seems you're on the same page21:00
*** dconde has joined #openstack-meeting-321:00
david-lyler1chardj0n3s: +121:00
*** ycombinator_ has quit IRC21:01
r1chardj0n3sok, I think I have a clear path forward for that. I should be able to knock those remaining tasks off pretty quickly21:01
david-lylegreat21:02
*** sunnyr has quit IRC21:02
*** sarob has joined #openstack-meeting-321:02
TravT_thanks r1chardj0n3s21:02
david-lyleout of time and missed the third party item, apologies21:02
david-lyleThanks everyone!21:02
david-lyle#endmeeting21:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:02
openstackMeeting ended Wed Dec  3 21:02:47 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-12-03-20.00.html21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-12-03-20.00.txt21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-12-03-20.00.log.html21:02
r1chardj0n3sshucks!21:02
mrungethanks!21:02
r1chardj0n3sI'll take it to the ML :)21:03
david-lyleopenstack-horizon is always open and we can continue there21:03
*** DuncanT has left #openstack-meeting-321:03
r1chardj0n3sthanks everyone!21:03
*** rbertram has left #openstack-meeting-321:03
neillcthanks all21:03
*** armax has joined #openstack-meeting-321:03
*** neillc has left #openstack-meeting-321:03
*** jtomasek has quit IRC21:06
*** igordcard has joined #openstack-meeting-321:11
*** igordcard has quit IRC21:14
*** gholler__ has joined #openstack-meeting-321:15
*** dboik has quit IRC21:15
*** dboik has joined #openstack-meeting-321:16
*** esp has left #openstack-meeting-321:16
*** MarkAtwood has quit IRC21:16
*** mrunge has quit IRC21:17
*** gholler_ has quit IRC21:18
*** ChuckC has joined #openstack-meeting-321:18
*** mestery_afk is now known as mestery21:18
*** carl_baldwin has quit IRC21:24
*** emagana_ has quit IRC21:28
*** emagana has joined #openstack-meeting-321:28
*** hareeshp has joined #openstack-meeting-321:32
*** carl_baldwin has joined #openstack-meeting-321:32
*** emagana has quit IRC21:33
*** dconde has quit IRC21:35
*** baoli has joined #openstack-meeting-321:36
*** emagana has joined #openstack-meeting-321:37
*** alexpilotti has quit IRC21:40
*** jgrimm is now known as zz_jgrimm21:46
*** SridharRamaswamy has joined #openstack-meeting-321:47
*** hareeshp has quit IRC21:48
*** bpokorny has joined #openstack-meeting-321:52
*** bpokorny_ has quit IRC21:55
*** ycombinator_ has joined #openstack-meeting-321:57
*** sunnyr has joined #openstack-meeting-321:58
*** crobertsrh has left #openstack-meeting-321:59
*** emagana has quit IRC22:02
*** sunnyr has quit IRC22:03
*** emagana has joined #openstack-meeting-322:03
*** dconde has joined #openstack-meeting-322:03
*** ycombinator_ has quit IRC22:10
*** MaxV has quit IRC22:14
*** baoli has quit IRC22:15
*** baoli has joined #openstack-meeting-322:16
*** Sukhdev has quit IRC22:17
*** sunnyr has joined #openstack-meeting-322:18
*** dthakkar_ has quit IRC22:18
*** yamamoto has joined #openstack-meeting-322:19
*** armax has quit IRC22:20
*** MaxV has joined #openstack-meeting-322:22
*** marun has quit IRC22:25
*** gholler_ has joined #openstack-meeting-322:27
*** gholler has joined #openstack-meeting-322:29
*** mattfarina has quit IRC22:30
*** gholler__ has quit IRC22:30
*** gholler_ has quit IRC22:32
*** banix has joined #openstack-meeting-322:37
*** MaxV has quit IRC22:40
*** matrohon has quit IRC22:46
*** yamamoto has quit IRC22:47
*** yamamoto has joined #openstack-meeting-322:50
*** vkmc has quit IRC22:51
*** banix has quit IRC22:54
*** Longgeek has joined #openstack-meeting-322:55
*** Ark has joined #openstack-meeting-322:58
*** Ark is now known as Guest6349522:59
*** EmilyW has left #openstack-meeting-322:59
*** banix has joined #openstack-meeting-323:00
*** Longgeek has quit IRC23:00
*** sarob has quit IRC23:00
*** dboik has quit IRC23:02
*** gholler_ has joined #openstack-meeting-323:04
*** gholler has quit IRC23:07
*** gholler_ has quit IRC23:08
*** carl_baldwin has quit IRC23:09
*** etoews_ has joined #openstack-meeting-323:10
*** armax has joined #openstack-meeting-323:11
*** etoews has quit IRC23:14
*** emagana has quit IRC23:18
*** tomoe_ has joined #openstack-meeting-323:19
*** doug-fish has left #openstack-meeting-323:19
*** igordcard has joined #openstack-meeting-323:24
*** julim has quit IRC23:27
*** etoews_ has quit IRC23:27
*** Piet has quit IRC23:28
*** etoews has joined #openstack-meeting-323:30
*** TravT_ has quit IRC23:32
*** SridharRamaswam1 has joined #openstack-meeting-323:34
*** SridharRamaswamy has quit IRC23:36
*** baoli has quit IRC23:37
*** emagana has joined #openstack-meeting-323:37
*** marun has joined #openstack-meeting-323:38
*** baoli has joined #openstack-meeting-323:38
*** sarob has joined #openstack-meeting-323:47
*** banix has quit IRC23:48
*** marun has quit IRC23:48
*** SridharRamaswam1 has quit IRC23:49
*** r1chardj0n3s is now known as r1chardj0n3s_afk23:52
*** sarob has quit IRC23:55
*** banix has joined #openstack-meeting-323:55
*** SridharRamaswamy has joined #openstack-meeting-323:56
*** baoli has quit IRC23:59

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