Wednesday, 2014-11-19

*** baoli has quit IRC00:03
*** carl_baldwin has joined #openstack-meeting-300:04
*** banix has quit IRC00:06
*** david-lyle is now known as david-lyle_afk00:06
*** devlaps has quit IRC00:09
*** SridharRamaswamy has quit IRC00:17
*** johnbelamaric has joined #openstack-meeting-300:17
*** johnbelamaric has quit IRC00:18
*** mwang2 has joined #openstack-meeting-300:22
*** mwang2 has quit IRC00:25
*** SridharRamaswamy has joined #openstack-meeting-300:25
*** yamamoto has joined #openstack-meeting-300:25
*** sicarie has left #openstack-meeting-300:30
*** yamahata has joined #openstack-meeting-300:30
*** hurgleburgler has joined #openstack-meeting-300:30
*** banix has joined #openstack-meeting-300:31
*** MarkAtwood has quit IRC00:31
*** nelsnelson has quit IRC00:32
*** banix has quit IRC00:32
*** carl_baldwin has quit IRC00:33
*** gholler has joined #openstack-meeting-300:33
*** hurgleburgler has quit IRC00:35
*** SridharRamaswamy has quit IRC00:35
*** hurgleburgler has joined #openstack-meeting-300:35
*** yamahata has quit IRC00:36
*** banix has joined #openstack-meeting-300:37
*** yamahata has joined #openstack-meeting-300:37
*** hurgleburgler has quit IRC00:37
*** yamamoto has quit IRC00:38
*** hurgleburgler has joined #openstack-meeting-300:38
*** hurgleburgler has quit IRC00:38
*** gholler_ has joined #openstack-meeting-300:38
*** hurgleburgler has joined #openstack-meeting-300:38
*** Sukhdev has joined #openstack-meeting-300:40
*** hurgleburgler has quit IRC00:40
*** gholler__ has joined #openstack-meeting-300:41
*** hurgleburgler has joined #openstack-meeting-300:41
*** banix has quit IRC00:41
*** gholler has quit IRC00:41
*** SridharRamaswamy has joined #openstack-meeting-300:43
*** hurgleburgler has quit IRC00:44
*** gholler_ has quit IRC00:44
*** gholler__ has quit IRC00:45
*** hurgleburgler has joined #openstack-meeting-300:45
*** banix has joined #openstack-meeting-300:47
*** hinnant_ has quit IRC00:54
*** hurgleburgler has quit IRC00:59
*** hurgleburgler has joined #openstack-meeting-300:59
*** hurgleburgler1 has joined #openstack-meeting-301:01
*** hurgleburgler has quit IRC01:01
*** hurgleburgler1 has quit IRC01:02
*** banix has quit IRC01:02
*** hurgleburgler has joined #openstack-meeting-301:03
*** Longgeek has joined #openstack-meeting-301:07
*** hurgleburgler has quit IRC01:08
*** bpokorny_ has quit IRC01:08
*** hurgleburgler has joined #openstack-meeting-301:09
*** yamamoto_ has joined #openstack-meeting-301:09
*** Longgeek has quit IRC01:12
*** hurgleburgler has quit IRC01:13
*** hurgleburgler has joined #openstack-meeting-301:14
*** banix has joined #openstack-meeting-301:14
*** hurgleburgler has quit IRC01:15
*** hurgleburgler has joined #openstack-meeting-301:15
*** hurgleburgler has quit IRC01:16
*** hurgleburgler has joined #openstack-meeting-301:16
*** hurgleburgler has quit IRC01:18
*** hurgleburgler has joined #openstack-meeting-301:19
*** hurgleburgler has quit IRC01:20
*** hurgleburgler has joined #openstack-meeting-301:21
*** hurgleburgler has quit IRC01:21
*** sarob has quit IRC01:33
*** etoews has joined #openstack-meeting-301:34
*** jacalcat has joined #openstack-meeting-301:35
*** jacalcat has left #openstack-meeting-301:35
*** seizadi has joined #openstack-meeting-301:35
*** mwagner_lap has joined #openstack-meeting-301:36
*** Sukhdev has quit IRC01:37
*** etoews has quit IRC01:41
*** dboik has joined #openstack-meeting-301:41
*** dboik_ has joined #openstack-meeting-301:42
*** ycombinator_ has joined #openstack-meeting-301:42
*** ChuckC has quit IRC01:43
*** dboik has quit IRC01:46
*** banix has quit IRC01:53
*** etoews has joined #openstack-meeting-301:53
*** baoli has joined #openstack-meeting-301:54
*** etoews has quit IRC01:59
*** seizadi has quit IRC02:08
*** mrsmith has quit IRC02:10
*** alexsyip has quit IRC02:25
*** etoews has joined #openstack-meeting-302:26
*** etoews has quit IRC02:27
*** etoews has joined #openstack-meeting-302:28
*** Longgeek has joined #openstack-meeting-302:33
*** Longgeek has quit IRC02:38
*** ChuckC has joined #openstack-meeting-302:39
*** ycombinator_ has quit IRC02:42
*** vkmc has quit IRC02:54
*** s3wong has quit IRC02:55
*** rbertram has joined #openstack-meeting-303:00
*** banix has joined #openstack-meeting-303:00
*** rbertram has left #openstack-meeting-303:00
*** SridharRamaswamy has quit IRC03:04
*** bradjones has quit IRC03:10
*** bradjones has joined #openstack-meeting-303:12
*** bpokorny has joined #openstack-meeting-303:23
*** bpokorny has quit IRC03:24
*** bpokorny has joined #openstack-meeting-303:25
*** jrist has quit IRC03:28
*** Longgeek has joined #openstack-meeting-303:34
*** MarkAtwood has joined #openstack-meeting-303:36
*** jacalcat has joined #openstack-meeting-303:38
*** Longgeek has quit IRC03:38
*** dboik_ has quit IRC03:38
*** jacalcat has left #openstack-meeting-303:39
*** jrist has joined #openstack-meeting-303:40
*** etoews has quit IRC03:48
*** sigmavirus24 is now known as sigmavirus24_awa03:49
*** jacalcat has joined #openstack-meeting-303:49
*** bpokorny has quit IRC03:55
*** ycombinator_ has joined #openstack-meeting-304:04
*** jacalcat has left #openstack-meeting-304:10
*** carl_baldwin has joined #openstack-meeting-304:12
*** SumitNaiksatam has quit IRC04:17
*** SumitNaiksatam has joined #openstack-meeting-304:17
*** flwang has quit IRC04:21
*** banix has quit IRC04:21
*** jpomero has quit IRC04:21
*** otherwiseguy has joined #openstack-meeting-304:23
*** banix has joined #openstack-meeting-304:24
*** flwang has joined #openstack-meeting-304:24
*** MarkAtwood has quit IRC04:26
*** ycombinator_ has quit IRC04:28
*** MarkAtwood has joined #openstack-meeting-304:35
*** SumitNaiksatam has quit IRC04:37
*** SumitNaiksatam has joined #openstack-meeting-304:39
*** etoews has joined #openstack-meeting-304:40
*** banix has quit IRC04:41
*** ivar-laz_ has joined #openstack-meeting-304:42
*** etoews has quit IRC04:45
*** ivar-lazzaro has quit IRC04:45
*** ivar-laz_ has quit IRC04:46
*** pcarver has quit IRC04:53
*** ttrifonov is now known as zz_ttrifonov04:59
*** marun has joined #openstack-meeting-305:03
*** MarkAtwood has quit IRC05:05
*** SridharRamaswamy has joined #openstack-meeting-305:10
*** SridharRamaswamy has quit IRC05:15
*** marun has quit IRC05:32
*** zz_ttrifonov is now known as ttrifonov05:47
*** k4n0 has joined #openstack-meeting-305:52
*** seizadi has joined #openstack-meeting-305:54
*** amotoki_ has quit IRC05:57
*** david-ly_ has joined #openstack-meeting-306:11
*** seizadi has quit IRC06:11
*** david-lyle_afk has quit IRC06:12
*** carl_baldwin has quit IRC06:13
*** briancurtin has quit IRC06:19
*** Longgeek has joined #openstack-meeting-306:23
*** otherwiseguy has quit IRC06:26
*** Longgeek has quit IRC06:28
*** amotoki has joined #openstack-meeting-306:33
*** k4n0 has quit IRC06:39
*** mrunge has joined #openstack-meeting-306:50
*** Longgeek has joined #openstack-meeting-306:53
*** k4n0 has joined #openstack-meeting-306:54
*** Longgeek has quit IRC06:55
*** Longgeek has joined #openstack-meeting-306:56
*** pcarver has joined #openstack-meeting-307:03
*** beagles has quit IRC07:11
*** armax has quit IRC07:16
*** david-ly_ has quit IRC07:18
*** beagles has joined #openstack-meeting-307:20
*** beagles is now known as Guest721907:21
*** kevinbenton has quit IRC07:22
*** k4n0 has quit IRC07:31
*** k4n0 has joined #openstack-meeting-307:44
*** jtomasek has quit IRC07:58
*** ttrifonov is now known as zz_ttrifonov07:59
*** yamamoto_ has quit IRC08:02
*** freemabr_ has joined #openstack-meeting-308:08
*** freemabr has quit IRC08:09
*** evgenyf has joined #openstack-meeting-308:24
*** sergef has joined #openstack-meeting-308:29
*** zz_ttrifonov is now known as ttrifonov08:30
*** iovadia has joined #openstack-meeting-308:33
*** MaxV has joined #openstack-meeting-308:37
*** iovadia has quit IRC08:38
*** david-lyle_afk has joined #openstack-meeting-308:49
*** iovadia has joined #openstack-meeting-308:52
*** yamamoto_ has joined #openstack-meeting-308:53
*** safchain has joined #openstack-meeting-308:58
*** jcoufal has joined #openstack-meeting-308:58
*** jcoufal has quit IRC09:01
*** jcoufal has joined #openstack-meeting-309:01
*** jcoufal has quit IRC09:01
*** jcoufal has joined #openstack-meeting-309:02
*** SumitNaiksatam has quit IRC09:06
*** SumitNaiksatam has joined #openstack-meeting-309:06
*** evgenyf has quit IRC09:07
*** igordcard has joined #openstack-meeting-309:15
*** yamamoto_ has quit IRC09:18
*** Longgeek has quit IRC09:38
*** Longgeek has joined #openstack-meeting-309:49
*** igordcard has quit IRC09:59
*** enykeev has quit IRC10:08
*** enykeev has joined #openstack-meeting-310:11
*** yamamoto has joined #openstack-meeting-310:18
*** yamamoto has quit IRC10:23
*** jtomasek has joined #openstack-meeting-310:27
*** reed has joined #openstack-meeting-310:27
*** lhcheng has joined #openstack-meeting-310:33
*** flwang has quit IRC10:44
*** nfedotov has joined #openstack-meeting-310:47
*** lhcheng_ has joined #openstack-meeting-310:50
*** amotoki has quit IRC10:51
*** lhcheng has quit IRC10:53
*** freemabr_ has quit IRC11:16
*** vkmc has joined #openstack-meeting-311:28
*** etoews has joined #openstack-meeting-311:31
*** etoews has quit IRC11:36
*** igordcard has joined #openstack-meeting-311:37
*** alexpilotti has joined #openstack-meeting-311:44
*** ekarlso- has quit IRC11:44
*** ekarlso- has joined #openstack-meeting-311:50
*** Guest7219 is now known as b3nt_pin11:50
*** mwagner_lap has quit IRC12:08
*** etoews has joined #openstack-meeting-312:32
*** Longgeek has quit IRC12:36
*** Longgeek has joined #openstack-meeting-312:36
*** etoews has quit IRC12:37
*** ekarlso- has quit IRC12:50
*** ekarlso- has joined #openstack-meeting-312:50
*** yamamoto has joined #openstack-meeting-312:50
*** flwang has joined #openstack-meeting-312:52
*** yamamoto has quit IRC12:55
*** kashyap has quit IRC13:00
*** amotoki has joined #openstack-meeting-313:01
*** matrohon has joined #openstack-meeting-313:02
*** jacalcat has joined #openstack-meeting-313:18
*** Longgeek has quit IRC13:18
*** etoews has joined #openstack-meeting-313:21
*** xuhanp has joined #openstack-meeting-313:24
*** ycombinator_ has joined #openstack-meeting-313:24
*** markmcclain has joined #openstack-meeting-313:27
*** markmcclain has quit IRC13:27
*** markmcclain has joined #openstack-meeting-313:28
*** Longgeek has joined #openstack-meeting-313:50
*** yamahata has quit IRC13:57
*** yamahata has joined #openstack-meeting-313:57
*** shwetaap has joined #openstack-meeting-314:03
*** carl_baldwin has joined #openstack-meeting-314:05
*** hurgleburgler has joined #openstack-meeting-314:06
*** mwagner_lap has joined #openstack-meeting-314:11
*** carl_baldwin has quit IRC14:11
*** hurgleburgler1 has joined #openstack-meeting-314:13
*** hurgleburgler has quit IRC14:13
*** mestery has quit IRC14:14
*** hurgleburgler1 has quit IRC14:16
*** emagana has joined #openstack-meeting-314:17
*** hurgleburgler has joined #openstack-meeting-314:21
*** pballand has quit IRC14:22
*** mestery has joined #openstack-meeting-314:26
*** dboik has joined #openstack-meeting-314:27
*** Ark has joined #openstack-meeting-314:36
*** devvesa has joined #openstack-meeting-314:36
*** Ark is now known as Guest7200114:36
*** Guest72001 has quit IRC14:37
*** etoews has quit IRC14:38
*** gholler has joined #openstack-meeting-314:38
*** markmcclain has quit IRC14:38
*** peristeri has joined #openstack-meeting-314:38
*** pkoniszewski has joined #openstack-meeting-314:48
*** otherwiseguy has joined #openstack-meeting-314:49
*** amotoki has quit IRC14:50
*** armax has joined #openstack-meeting-314:51
*** jaypipes has joined #openstack-meeting-314:51
*** jpomero has joined #openstack-meeting-314:54
*** MaxV has quit IRC14:57
*** pawel-palucki has joined #openstack-meeting-314:57
*** etoews has joined #openstack-meeting-314:57
*** MaxV has joined #openstack-meeting-314:58
*** pc_m has joined #openstack-meeting-315:00
*** etoews has quit IRC15:02
*** dboik has quit IRC15:03
*** MaxV has quit IRC15:03
*** mrunge has quit IRC15:03
*** pc_m has left #openstack-meeting-315:04
*** nelsnelson has joined #openstack-meeting-315:07
*** otherwiseguy has quit IRC15:08
*** ycombinator_ has quit IRC15:09
*** hurgleburgler has quit IRC15:09
*** zz_jgrimm is now known as jgrimm15:14
*** etoews has joined #openstack-meeting-315:16
*** alaski has joined #openstack-meeting-315:18
*** xuhanp has quit IRC15:18
*** dboik has joined #openstack-meeting-315:22
*** sigmavirus24_awa is now known as sigmavirus2415:23
*** sergef has quit IRC15:23
*** sergef has joined #openstack-meeting-315:23
*** amotoki has joined #openstack-meeting-315:28
*** dboik_ has joined #openstack-meeting-315:28
*** cbouch has joined #openstack-meeting-315:28
*** MaxV has joined #openstack-meeting-315:29
*** markmcclain has joined #openstack-meeting-315:29
salv-orlandoaloha15:29
mesteryo/15:29
markmcclainhi15:29
amotokihi15:29
* markmcclain awaits his coffee15:29
mesteryarmax: ping15:29
armaxmestery: pong15:29
* mestery drinks his coffee15:29
mestery#startmeeting neutron_drivers15:30
openstackMeeting started Wed Nov 19 15:30:19 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.15:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:30
*** openstack changes topic to " (Meeting topic: neutron_drivers)"15:30
openstackThe meeting name has been set to 'neutron_drivers'15:30
*** pc_m has joined #openstack-meeting-315:30
mesteryWe have a light agenda today, and I'm going to try to wrap this up in 30 minutes or less. Wish me luck. :)15:30
mestery#link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers Agenda15:30
mestery#topic Discuss Vendor Split BP15:30
*** openstack changes topic to "Discuss Vendor Split BP (Meeting topic: neutron_drivers)"15:30
mestery#link https://review.openstack.org/#/c/134680/15:31
mesteryHopefully folks have had a chance to review this.15:31
mesteryI'd like to thank armax and marun (along with kevinbenton and dougwig) for their work on this one!15:31
*** shwetaap has quit IRC15:31
mesteryI think this captures the reasons for the split quite accurately.15:32
*** dboik has quit IRC15:32
armaxmestery: I am incorporating feedback as it comes…I need to look at yesterday’s feedback15:32
armaxso expect another patchset by the end of today15:32
mestery#info armax to land another version of the split spec by EOD15:33
mesteryThanks armax.15:33
*** Ark has joined #openstack-meeting-315:33
mesteryarmax: Any huge issues which people have brought up so far which seem insurmountable?15:33
*** Ark is now known as Guest4588815:33
salv-orlandoI find the proposal reasonable. We might need to educate contributors a bit when it comes to synchronizing data model changes and library changes, but that’s not going to be impossible.15:34
armaxnot that I could think of, to be honest15:34
salv-orlandoI think people have no idea where their library code should live15:34
armaxbut danger is always lurking behind the corner :)15:34
salv-orlandothat’s another thing that can be easily solved15:34
armaxsalv-orlando: that’s the beuty of the approach15:34
salv-orlandoI have two questions for us however15:34
armaxsalv-orlando: it does not matter15:34
mesteryI also think we'll need to work hard to evangelize this and make sure people know the deadlines, how to refactor their plugin/driver, etc.15:35
armaxsalv-orlando: it’s whatever you want it to lieve15:35
armax*live15:35
salv-orlandoarmax: “beauty” is probably a word I would not use in any context where you’re compromising15:35
*** shwetaap has joined #openstack-meeting-315:35
armaxsalv-orlando: would it make sense to post those questions on the spec? it’s easier to track15:35
armaxsalv-orlando: meh15:35
salv-orlandoI think someboduy did already15:35
salv-orlandoso the question for us are...15:35
salv-orlando1) when it comes to building rpms and debs, shall the plugin maintainers work with distros on their own?15:36
*** ajo has joined #openstack-meeting-315:36
markmcclainthat is going to be a big concern for some smaller vendors15:36
salv-orlandoI mean not for building the rpms, but for having them available in a repo15:36
markmcclainthey get visibility by being in the tree15:36
armaxsalv-orlando, markmcclain: so long that the source code is reachable15:37
armaxthe distro will have not difficulty of packaging the code15:37
mesteryarmax: ++15:37
markmcclainarmax: it is not that the distro will have challenges packaging15:37
*** dboik_ has quit IRC15:37
salv-orlandoyeah might be… there will be some hiccups and headaches at the beginning. I think it’s a process that will smooth out over time.15:37
markmcclainit is whether they'll do it in the first place15:38
armaxmarkmcclain, salv-orlando: I want to stress the fact that packaging is only the first step into getting your hands on any solutioin15:38
ajoif vendor (tagged) git's / release tarballs are available then it should be easy to package them15:38
ajo(hi ;D)15:38
armaxmarkmcclain, salv-orlando but there’s lot more15:38
amotokiagree. To allow distros to package plugins, we (vendors and neturon team) need to clarify version dependencies.15:38
armaxso frankly I am not too worried15:38
*** dboik has joined #openstack-meeting-315:38
amotokibut I think it is not a big problem and during clarifying the process it will be addressed.15:39
salv-orlandook if you have no reason to be worried I have no reason as well.15:39
mesterymarkmcclain: The visibility thing can be handled by us publicizing the places where the drivers go. That part is an education thing as much as a visibility thing. Maybe I'm simplifying it though. :)15:39
markmcclainyeah.. just want to make sure that is part of the solution15:39
armaxsalv-orlando: I am just saying that even if the source is packaged today, it does not mean it’s usable15:39
armaxtested or validated on any distro15:39
markmcclainalso notice that we don't require the drivers to be apache2 license compatible15:39
armaxdistros need a relationship with the vendor15:39
armaxto go beyond just packaging15:40
mesterymarkmcclain: Can we enforce that if htey are out of tree (licenses)? The parts which live in neutron need to be apache2 though.15:40
mesteryBut since the code is imported, do we need to enforce apache2?15:40
armaxmestery: I wouldn’t think so15:40
markmcclainline 255 would require it15:40
salv-orlandoI think plugin maintainers (they’re not only “vendors”) will need to learn how to manage the lifecycle of a package15:41
* mestery looks15:41
armaxfor the vendor library, I mean15:41
armaxthe vendor integration park, being in three is apache215:41
armax*part15:41
* salv-orlando will probably look for somebody to this do for me, as it’s not really one of things I want to learn15:41
mesterymarkmcclain: Yeah, so parts of it are apache2, we should add that in the spec.15:41
* armax thinks about greenery and the beauty of nature15:41
*** pkarikh has left #openstack-meeting-315:42
* mestery thinks about coffee15:42
markmcclainthe shim in the tree is obviously apache2, but any deps for the shim must be compatible since that is a dependency15:42
mesterymarkmcclain: Makes sense15:42
salv-orlandoarmax: greenery like you’re rolling some weed?15:42
markmcclainit's the battle we fight w/ global requirements15:42
mesterylol15:42
armaxmarkmcclain: same considerations apply to any library we use in openstack15:42
markmcclaincorrect, but we should restate is here15:42
armaxmarkmcclain: but I’ll make the point, it seemed obvious but being explicit does not hurt15:42
mesteryarmax: Agreed, but maybe we should call it out in this spec explicitly.15:42
armaxyeah15:43
armaxfair15:43
mesteryExcellent, agreement! :)15:43
* mestery thinks it's the greenery ;)15:43
anteayaexplict about licencing +115:43
markmcclainI do think that anyone that gets a shim must have the source posted somewhere open15:43
*** carl_baldwin has joined #openstack-meeting-315:43
ajo+115:43
mesterymarkmcclain: I'm somewhat split on that one, I can see arguments both ways, so I'm meh either way. :)15:44
armaxmarkmcclain: I see no reason why it shouldn't15:44
mesteryBut it should be documented (if it's not) on what we agree on.15:44
markmcclainwell we're still giving them a hook15:44
markmcclainthey have to trade something and having code locked in corporate repo is bad15:44
* mestery is good with requiring source15:44
armaxmarkmcclain: but ultimately it’s a choice we have no control of15:44
markmcclainwe do have control on the shim15:44
mesteryYes, we can control it by landing hteir shim15:44
mesteryor not landing it15:44
markmcclainright15:45
armaxmarkmcclain: I’ll be more explciit that accessibility to the source is an important criterion for assessing how friendly a vendor is15:45
markmcclainideally I'd like that code to exist in stackforge and follow our community model15:45
armaxfriendly for lack of better word15:45
armaxso don’t quote me on that15:45
armaxplease15:45
armax:)15:45
salv-orlandofolks, I think the idea of having  the shim in neutron and the plugin library private is just demoniac15:45
*** pballand has joined #openstack-meeting-315:45
salv-orlandodiabolic15:45
mesterystackforge is ideal, but if they have it on github, that is ok as well15:46
markmcclainsalv-orlando: someone will try it15:46
*** mrmartin has joined #openstack-meeting-315:46
salv-orlandomarkmcclain: and we’ll go medieval on them ;)15:46
anteayasomeone always tries something15:46
anteayasalv-orlando: that is tiring15:46
anteayabest to just say no when it happens15:46
armaxmarkmcclain, salv-orlando: I would cross that bridge when we get to it15:46
armaxhonestly15:46
mesteryI think explicitely putting it in the spec makes it clear, so lets just put it in there15:47
mesteryAnd face the pushback early rather than later15:47
armaxmestery: sure15:47
mesteryCool15:47
mesteryThanks armax15:47
amotokiIs a requirement for shim plugin  openness of their library ?15:47
amotoki or is it just a suggestion?15:47
mesteryamotoki: I think we're saying make it a requirement15:47
armaxI think it’s already expressed int he spec15:47
markmcclainI think requirement15:47
armaxbut I’ll build a stronger case for it15:47
mesteryarmax: Cool15:47
amotokimestery: agree15:47
salv-orlandoI think the requirement made here is that you don’t import a package which is not available in the open15:47
*** hemanthm has joined #openstack-meeting-315:47
armaxsalv-orlando: no15:48
salv-orlandoand frankly I think you need that for unit test don’t you?15:48
markmcclainsalv-orlando: +115:48
salv-orlandoarmax: you’re the voice of no...15:48
*** otherwiseguy has joined #openstack-meeting-315:48
salv-orlandowhat is the requirment then?15:48
armaxsorry I mean, the package must be accessible somewhere15:48
salv-orlandoanyway, this is only my first question… I also have a 2nd one ;)15:49
mesterylol15:49
armaxso, yes :)15:49
salv-orlandoaccessible like source code available in the open (where in the open == public)15:49
salv-orlandocan I go with the 2nd question?15:49
armaxyou guys are confusing me…right that’s what the spec states right now15:49
armaxsalv-orlando: but it does not make it a strong requirement for acceptance of the shim in the tree15:49
markmcclainarmax: I think the spec suggests but does not mandate15:49
armaxmarkmcclain: correct15:50
markmcclainI think a 'shall … ' is in order here15:50
*** dboik has quit IRC15:50
armaxso are we saying that the code must rather than shoud?15:50
mesteryWe're mandating I think, right?15:50
armaxshould?15:50
armaxmestery: ok15:50
anteayawill15:50
armaxlet’s go with that15:50
markmcclainmust/shall  rather may/should15:50
*** dboik has joined #openstack-meeting-315:50
mestery#info Update the spec to indicate any shim plugins/drivers in the tree require their out-of-tree code to be open source on something like stackforge or github15:51
salv-orlandois this sorted then?15:51
armaxmarkmcclain: ok15:51
armaxsalv-orlando: yes15:51
markmcclainwhat was Salv's question?15:51
salv-orlandothe second question is: how shimmy should the shim be?15:51
armaxsalv-orlando: thou shan't make the code private15:51
armaxsalv-orlando: does that work?15:52
armax:)15:52
mesteryarmax: lol15:52
salv-orlandoyou went from legalese to biblical15:52
markmcclainhaha15:52
armaxsalv-orlando: I know, right?15:52
armaxsalv-orlando: now you’re becoming even more pedantic than what you already are15:52
*** yamamoto has joined #openstack-meeting-315:52
armaxsalv-orlando: about the shimminess15:53
*** shwetaap has quit IRC15:53
* armax thinks it’s not even a word15:53
markmcclainI think the thinkess of the shim is dependent on the plugin refactor15:53
armaxsalv-orlando: I think that the shimmier it is the better15:53
markmcclainif we do our job right we should be able to make it really thin15:53
mesteryThe thinner the better IMHO15:53
armaxsalv-orlando: hopefully some initial effort will pave the way for ‘coding by example’15:53
mesterydougwig had an example of a LBaaS V2 driver which was super shimmy15:54
salv-orlandoshould we evaluate on a case by case basis? What if some plugin already in trunk offers a diet plan in say two or three phases?15:54
markmcclainin many ways the contrail plugin is closer to want we eventually want15:54
markmcclainsalv-orlando: I think a phased approach should be allowed15:54
mesteryThe spec makes it clear the diet has to happen during the kilo cycle.15:54
mesteryDo we want to change that?15:54
markmcclainwe do have to protect the operators15:54
mesteryIt needs an end date.15:54
mesteryOr else some will drag it out to the bitter end.15:54
salv-orlandook15:54
salv-orlandothe other point about the contrail plugin15:55
markmcclainit will always drag out to the bitter end :)15:55
salv-orlandothis means worst case one could do a proxy to a plugin living somewhere else?15:55
mesterylol15:55
armaxmarkmcclain: in the spec I set a date, which is suggested to be assessed at every mileston15:55
armaxe15:55
armaxto see whether we are on track with the plan15:55
armaxso there’s some wiggle room15:55
markmcclainsalv-orlando: yes.. a the shim could be proxy15:55
salv-orlandoI estimate 4 weeks full time for instance on NSX plugin15:55
salv-orlandowhich considering how much time I can spend on that means 4 months15:56
armaxbut we need to be clear that procrastination is not an option15:56
salv-orlandoand I think others will be in the same situation15:56
markmcclainthe thing to remember is I had a few folks say that 6mos was not enough time to enable IPv615:56
mesteryAnd so we double that for others, meaning 8 weeks for non salv-orlando maintainers ;)15:56
amotokisalv-orlando: Does 4 weeks include CI or other setups?15:56
salv-orlandofrankly in my case I’d rather accept deprecation that ask for an extension15:56
markmcclainand that spec has been around 20 yrs :p15:56
mesterymarkmcclain: Right, thus multi-cycle is needed15:56
armaxif no tangible progress is observed I think we should reserve the right to judge whether the deprecation appleis or not15:56
salv-orlando4 weeks code only15:56
mesteryarmax: ++15:56
*** shwetaap has joined #openstack-meeting-315:56
amotokisalv-orlando: I feel the similar too15:57
salv-orlandook so we will judge on a case by case basis15:57
armaxsalv-orlando: you’d do anything to save you from working15:57
armax:)15:57
mesteryWow, we made it through salv-orlando's questions in < 30 minutes! :)15:57
*** yamamoto has quit IRC15:57
armaxmestery: yay15:57
salv-orlandoit’s not a case if my job title is “distinguished procrastinator"15:57
armaxsalv-orlando: oh right, I forgot15:57
armaxsalv-orlando: I shan’t forget that, ever15:58
mesteryAnything else then?15:58
anteayaarmax: what is your benchmark for "tangilbe progress"?15:58
mesteryOtherwise, armax will update the spec15:58
mesteryAnd we'll review again.15:58
amotokii have two questions: destiny of linux bridge driver, and common driver code in ML2 stuff.15:58
salv-orlandoI think I will soon get the Homer Simpson fellowship15:58
armaxanteaya: some progress on the plan outlined on the work item section15:58
armaxamotoki: that was raised on the spec, and it’s been addressed15:58
amotokiarmax: will check15:59
anteayaokay, this will be challenging to assess, since your definition and someone else's will differ15:59
armaxamotoki: let me know if that answer your concerns15:59
salv-orlandoanteaya: it’s a situation where it’s really hard to define objective metrics inmho15:59
armaxotherwsie we’ll take it offline15:59
markmcclainarmax: I do think we need a work item for a realistic roadmap for vendors to follow15:59
armaxanteaya: no, if the plan is clear and well detailed15:59
armaximo15:59
anteayasalv-orlando: oh I agree, you can avoid the fight, you can just define the terms15:59
anteayacan't15:59
*** yamamoto has joined #openstack-meeting-315:59
markmcclainone of the current problems is that we don't provide a happy path for vendors15:59
markmcclainwhich leads to the poor impls15:59
mesterymarkmcclain: It needs to be laid out in detail for them to follow, agreed.16:00
armaxI mean, if no commits have been posted to refactor the code according the proposed structure16:00
anteayacommits, there is a metric16:00
anteayamerged commits?16:00
armaxit’s pretty obvious to me that no tangible procgress has been made16:00
armax:)16:00
mesteryWell, and if no one has reached out asking questions, etc.16:00
mesterythat's another sign16:00
anteayaquestions, another metric16:00
mesteryanteaya: Right.16:01
anteayagreat, two so far, thanks16:01
armaxok I’ll cover this area a bit more16:01
mesteryhonestly, these are metrics we should already have to some extent, we can collect from prior releases to get a feel for what to expect.16:01
mesterySpoiler: It won't be pretty in some cases.16:01
salv-orlandomarkmcclain: how can we sprinke happiness on vendors?16:01
anteayaha ha ha16:02
salv-orlandoI’m a rather grumpy one myself16:02
anteayaget them off windows16:02
mesterysalv-orlando: donuts16:02
markmcclainsalv-orlando: kittens and puppies16:02
*** Sukhdev has joined #openstack-meeting-316:02
*** Longgeek has quit IRC16:03
salv-orlandook, so for every plugin which is moved out into a library I’ll donate $100 to an animal shelter. does that work?16:03
anteayaha ha ha16:03
mesteryrofl16:03
markmcclainhaha16:03
salv-orlandoand mestery will send a box of 12 donuts - for each developer16:03
armaxsalv-orlando: okay let me set up a charity about this16:03
armaxsalv-orlando: I’ll send you the bank coordinates16:03
anteayaI can add a link to a linux distro download of choice16:03
mesteryWith sprinkles. Sprinkles make everything better.16:03
ajo:)16:04
salv-orlandoseriously. We probably want to have an “ideal story” - both for maintainters of plugin already in trunk and for maintainers of plugins not yet in trunk16:04
markmcclainright16:04
armaxideal being?16:04
markmcclainwe need a pioneer and extensively doc what we're doing16:04
armaxlike you want to write a novel or something?16:05
mesteryNot only that, but I think we need to make ourselves extra available to help people, on IRC, ML, meetings, etc.16:05
markmcclainarmax: more of a checklist that jr dev could follow of steps16:05
armaxmarkmcclain: oh right, it looks like kevinbenton should help us spearhead the effort16:05
mesteryIn other words, go out of our way to make this process smooth for people.16:05
anteayaI'm not sure how much more extra people have in them16:05
anteayaI know I'm all used up16:05
mesteryWe'll spread the extra around and see how much is left in our collective tanks16:06
armaxmarkmcclain: hopefully maintainers of vendor code are somewhat more than jr devs16:06
anteayagreat, I hope someone has some16:06
mesterySince we're moving people out of tree, we need to accomdate them during hte process16:06
salv-orlandoarmax: I might become a blogger! That would be the apotheosis of the procrastinator16:06
markmcclainarmax: experience says otherwise16:06
armaxotherwise we’d be in trouble with our without this proposal16:06
anteayaarmax: the ci operators aren't16:06
* mestery shudders at the ci operators16:06
mestery*though of the ci operators16:07
mestery*thought16:07
* mestery drinks more coffee16:07
anteayasorry about that16:07
armaxanteaya: operators should not be affected by this effort at all16:07
anteayadidn't meant to invoke that16:07
armaxif they did then we’d failed miserably16:07
anteayaarmax: shouldn't and are, yet to be seen16:07
salv-orlandoand honestly there are a lot of “junior” devs which are way better than me. So it’s a matter of how flexible and adaptable you are, not experience16:07
armaxanteaya: right, but we’re aware that disruption for operator is not an option16:07
anteayafor their ci operations?16:08
anteayathey will have to change their pointers for git clones at teh very least16:08
markmcclainif they have devstack support16:08
anteayasome having difficulty with that16:08
mesteryFolks, I think we're digressing a bit here.16:08
anteayabut don't mean to derail16:08
anteayasorry16:08
mesteryAnd we're 8 minutes over my ending time :)16:08
armaxanteaya: if it was just that I’d sign up for that16:08
mesteryOr proposed ending time :)16:08
mesteryAny other issues with the BP to bring up now?16:09
anteayaarmax: I'd welcome you16:09
mesteryOr should we let armax roll another version and then re-review that one?16:09
markmcclainI do have a questions on security handling, but I'll post those to the spec16:09
mesterymarkmcclain: Cool16:09
armaxmarkmcclain: we covered that part16:09
mesteryI want to think through stable updates, specifically Juno/Kilo backports, etc.16:09
armaxmarkmcclain: let us know if it’s too sparse for you16:09
salv-orlandosince it’s been a quiet meeting so far16:09
markmcclainright, but I have questions about what's covered16:09
salv-orlandolet me try and drop a bombshell16:09
* mestery gets his kevlar on16:10
salv-orlandoML216:10
mesteryBOOM!16:10
armaxsalv-orlando: drop away16:10
amotokidevstack integration is one of questions. in-tree devstack support is acceptable after splitting out? this is beyond the spec, but we need to clarify.16:10
armaxsalv-orlando: is there anything that wasn’t covered in the spec that deserve the bomb shelling?16:10
salv-orlandoI just did. What do we do with it? I think it’s unfair to give it special treatment and leave it in the tree16:10
markmcclainsalv-orlando: we need a gating reference implementation16:10
armaxsalv-orlando: that was documented16:11
armaxnot sure what else to add to that16:11
*** shwetaap has quit IRC16:11
salv-orlandoyou are speaking legales again.16:11
salv-orlandoI know it’s documented. I think it’s unfair.16:11
armaxamotoki: devstack integration has been documented16:11
armaxsalv-orlando: unfair on what grounds?16:11
mesteryI think the gating requirement is what's keeping it there16:11
salv-orlandoon the ground that we grant ML2 and all its drivers the right of staying in the tree16:11
salv-orlandoI am not bothered16:11
armaxsalv-orlando: you open source nsx and we’d be happy to switch16:11
mesteryWait, all the ML2 drivers are staying in tree?16:11
mesteryI missed that part16:12
mesteryI thought only the OVS one was staying in-tree (for now)?16:12
*** banix has joined #openstack-meeting-316:12
* mestery has to re-read that part16:12
amotokiarmax: the speci mentions just the existing devstack support. my point is future plan (new vendor support).16:12
salv-orlandoarmax: you just said somethign rather non intelligent16:12
salv-orlandoml2 has plenty of drivers for proprietary 3rd parties16:12
armaxsalv-orlando: sometimes I have brainfarts too16:12
armaxsalv-orlando: those will get slimmed down too16:12
armaxsalv-orlando: as we proposed16:13
salv-orlandowhat about the comment we received that you can’t split ml2 from its drivers because they work so nicely together?16:13
markmcclainok.. linuxbridge has to stay in w/OVS16:13
armaxmarkmcclain: then we should start gating on it16:13
markmcclainthere is a group of folks who don't want OVS16:13
markmcclainarmax: yes we should16:13
armaxok16:13
armaxmarkmcclain: until then we can’t worry bout LB, IMO16:14
armaxsalv-orlando: I don’t follow16:14
mestery#info To keep LB in-tree we need to start gating on it.16:14
markmcclainfolks deploy it into production16:14
*** shwetaap has joined #openstack-meeting-316:14
markmcclainso we should be gating on it16:14
salv-orlandoarmax: that was live at the summit - I think it was bob?16:14
armaxand perhaps we’d need to get LB to parity, like DVR perhaps?16:14
markmcclainarmax: ++16:15
armaxsalv-orlando: we’re not advocating to splitting drivers right now16:15
armaxwe’re advocating to slim vendor code down16:15
salv-orlandoI thought that meant removing drivers16:15
armaxsalv-orlando: we’d need to reassess what makes sense when some progress has been done16:15
armaxsalv-orlando: no it doesn’t16:15
salv-orlandoarmax: then until further notice ML2 is not affected by this blueprint at all.16:16
armaxthe same way we’re not proposing to remove vendor plugins16:16
mesteryThis is the first step in that direction, right armax?16:16
mesteryOR it coudl be I guess16:16
* markmcclain wonders if this will have unintended effect of vendors going ML2 to stay in tree16:16
mesteryYikes16:17
*** kashyap has joined #openstack-meeting-316:17
amotokitheoretically *new* ml2 drivers can be completely out of tree.16:17
armaxguys, no vendor gets out of the tree with this proposal16:17
armaxneither ml2 driversnor core plguins16:17
amotokibut some drivers already have db models in neutron tree :-(16:17
armaxI am amazed as you are still confused about this16:17
*** iovadia has quit IRC16:17
armaxwhere have we gone wrong?16:18
salv-orlandoI think armax’s point is that the plugins and the driver stays but they are going on a diet16:18
salv-orlandonow he’s defined a 1,200 kcal/day diet for plugins16:18
salv-orlandobut this diet does not apply to ML2, because it’s not a plugin like the others16:18
amotokiarmax: yes. even after the split, we still have thin drivers/plugin in the tree..16:18
salv-orlandolet’s not forget all the virtues of ML216:18
armaxsalv-orlando: it does apply across the boar16:19
armaxd16:19
salv-orlandobu armax will then define a plan also for putting ML2 drivers on a diet, right?16:19
mesteryThe spec references ML2 and monolithic plugins16:19
armaxbut if some ml2 drivers are already skinny, then there’s nothing that can be done16:19
armaxis there?16:19
salv-orlandook so ML2 will slim down too?16:19
markmcclainin theory ML2 drivers should be small :)16:19
armaxthat’s what the spec state16:19
mesterysalv-orlando: Yes, that was my reading of the spec16:19
salv-orlandoI thought it was excluded because of co-gating requiremtns?16:19
armaxsalv-orlando:  no16:20
salv-orlandoso the one who’s confused is me16:20
salv-orlandowho said co-gating and reference implementaiton?16:20
salv-orlandowas it markmcclain16:20
armaxright16:20
armaxand that’s true but one of the items of the spec is that even the reference implemetnation will go through the same refactoring exercise16:20
armaxeven though there’s no point of moving the code elsewhere, at least for the time being16:21
armaxthis is black and white on the spec16:21
mesteryFYI: 8 minutes left16:22
amotokias a conclusion, does the split out affect ml2 drivers?16:22
armaxI’ll revise the spec one more time to make sure there’s no room for confusion16:22
markmcclainamotoki: I think the we have to a clear plan for ml216:22
salv-orlandoI have a feeling the “shimming down” for ML2 will not be as obvious as the one for monolithic plugins16:23
salv-orlandobut this is just a feeling. You’ll buy me a beer in vancouver if it turns out I was right16:23
armaxthere’s a point about this on the spec I am trying to find the line no :)16:23
mesteryNote, the APIC ML2 driver went through a "thinning down" at the end of Juno already, that could be an example for folks.16:23
* mestery can't believe he just said use the APIC driver as an example for folks.16:23
markmcclainyeah that might be harder, but then again maybe designing better interface contracts would slim it down16:23
armaxbut anyhow I’ll clear this up, to make it salv-orlando proof16:23
mesteryAnyways, at this point, lets let armax spin a new version and continue comments there.16:24
mesteryAnd if there's nothing else right now, shall we close this jolly affair?16:24
mestery:)16:24
*** marun has joined #openstack-meeting-316:24
armaxline 124 btw16:25
*** etoews has quit IRC16:25
*** etoews has joined #openstack-meeting-316:25
armaxThe monolithic plugins and ML2 drivers become integration-only to code that lives outside the tree;16:25
armaxjust saying16:25
mesteryThanks armax, and thanks to everyone, I think this was a productive meeting (at least for me). ;)16:25
mesteryLooking forward to the new spec rev armax ;)16:26
mestery#endmeeting16:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:26
openstackMeeting ended Wed Nov 19 16:26:21 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-11-19-15.30.html16:26
salv-orlandocan vendor still run all their unit tests?16:26
salv-orlandonoooo16:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-11-19-15.30.txt16:26
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-11-19-15.30.log.html16:26
salv-orlandocome back16:26
mestery:(16:26
salv-orlandoI want to irritate armax further?16:26
salv-orlando!!!116:26
openstacksalv-orlando: Error: "!!1" is not a valid command.16:26
salv-orlandojk16:26
*** SridharRamaswamy has joined #openstack-meeting-316:26
yamamotoit seems like a bad idea to have this discussion simultaneously with ml2 subteam meeting16:26
armaxsalv-orlando: fire away?16:26
salv-orlandoopenstack go home you’re drunk16:26
ajo:D16:27
*** ttrifonov is now known as zz_ttrifonov16:27
mesterylol16:27
*** pc_m has left #openstack-meeting-316:27
armaxsalv-orlando: not sure I follow, but feel free to harass me privately :)16:27
salv-orlandoarmax I’ll bring the comment on the spec. But basically I want to know if all the unit tests we ran today for each vendor should still run in the main py-{26|27} jobs16:27
armaxno, they won’t16:28
ajosalv-orlando I undertood those wouldn't16:28
armaxit’s black and white on the spec16:28
armaxline 22016:28
ajoarmax, that was left to vendor CI, right?16:28
armaxyes…I gotta go now16:28
*** marun_ has joined #openstack-meeting-316:28
ajocu! ;)16:28
amotokiajo: or they can still use neutron core test framework for their own plugin/driver.16:29
armaxsalv-orlando: re-read the spec, because clearly you’ve forgotten it already16:29
ajoamotoki, of course16:29
ajothat was the idea, as far as I uderstood16:29
salv-orlandoarmax: come on you know I have not even read that16:29
ajolol :)16:29
armaxsalv-orlando: ah16:29
salv-orlandootherwise I would not be a distinguished procrastinator16:29
armaxsalv-orlando: I shan’t forget that salv-orlando is a professional procrastinator16:29
ajosalv-orlando: true16:29
salv-orlandodistinguished16:29
armaxsalv-orlando: I keep forgetting that16:29
armaxsalv-orlando: meh16:30
armaxreally gotta step away now16:30
*** zz_ttrifonov is now known as ttrifonov16:30
*** marun has quit IRC16:30
*** SridharRamaswamy has quit IRC16:31
amotokithnx all! moving to ml2 meeting...16:32
*** dboik has quit IRC16:33
*** david-lyle_afk is now known as david-lyle16:34
*** marun_ has quit IRC16:34
*** marun_ has joined #openstack-meeting-316:35
*** shwetaap1 has joined #openstack-meeting-316:35
*** shwetaap has quit IRC16:39
*** carl_baldwin has quit IRC16:43
*** jcoufal has quit IRC16:49
*** ttrifonov is now known as zz_ttrifonov16:49
*** marun has joined #openstack-meeting-316:52
*** dheeraj-gupta-4 has joined #openstack-meeting-316:53
*** marun__ has joined #openstack-meeting-316:53
*** marun_ has quit IRC16:55
*** dboik has joined #openstack-meeting-316:56
*** VineetMenon_ has joined #openstack-meeting-316:56
*** belmoreira has joined #openstack-meeting-316:56
*** pballand has quit IRC16:56
*** k4n0 has quit IRC16:56
*** bpokorny has joined #openstack-meeting-316:56
*** marun has quit IRC16:57
*** gilliard has joined #openstack-meeting-316:57
*** mriedem has joined #openstack-meeting-316:58
*** sarob has joined #openstack-meeting-316:58
*** pballand has joined #openstack-meeting-316:58
*** SridharRamaswamy has joined #openstack-meeting-316:59
*** jerdfelt has joined #openstack-meeting-316:59
alaski#startmeeting nova-cells17:00
openstackMeeting started Wed Nov 19 17:00:25 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
dansmitho/17:00
leifz:-)17:00
bauzas\o17:00
mriedemhi17:00
alaskiwoo17:00
*** jgallard has joined #openstack-meeting-317:00
alaskiwelcome everyone to the first meeting on this new effort17:01
edleafeo/17:01
*** SumitNaiksatam has quit IRC17:01
dheeraj-gupta-4hi17:01
alaskiI have a simple agenda setup at https://wiki.openstack.org/wiki/Meetings/NovaCellsv2#Agenda17:01
gilliard\o17:01
VineetMenon_\m/17:01
belmoreirahi17:01
alaskiand feel free to add to that for any particular week17:01
alaski#topic Cells manifesto17:02
*** openstack changes topic to "Cells manifesto (Meeting topic: nova-cells)"17:02
*** marun__ is now known as marun17:02
*** bobmel has joined #openstack-meeting-317:02
alaskiSo dansmith had the idea that some sort of manifesto would be useful17:02
bauzas+117:02
dansmithyeah, I was just thinking a summary of where we see this going17:02
dansmithan overview of the plan, what things will look like when it's "done" and maybe a few first steps17:03
*** markus_z has joined #openstack-meeting-317:03
bauzasI like the idea here https://review.openstack.org/#/c/133691/17:03
alaskiI think that's a very useful idea17:03
dansmithand of course, a little text relating this to current cells to make it clear that we're not really changing the high-level organization very much17:03
bauzasfor upgrades17:03
dansmithI'm happy to help with that, or start it, etc17:03
*** Longgeek has joined #openstack-meeting-317:03
leifzIt may be worth a paragraph on different issues we run into when add features that could affect cells?17:04
*** s3wong has joined #openstack-meeting-317:04
alaskidansmith: cool.  if you want to start it that would be great17:04
dansmithleifz: maybe, I think the alternate organization makes that much less of a problem17:04
VineetMenon_dansmith: functioanlly much will not change.. but implementation wise, lots gonna change, right17:04
alaskiI come from a place of familiarity with cells, so I may make a lot of assumptions as I go17:04
dansmithleifz: that's all in my mine of course, but..17:04
dansmithalaski: sure I can start it17:04
dansmithVineetMenon_: sure, a lot needs changing, but not as much as if we were doing something totally wildly different, I think17:05
alaskiwhere should this live?17:05
bauzasdansmith: what kind of deliverable do you plan ?17:05
VineetMenon_dansmith: and the DAG organization of cell won't be any more.. it will be a two level tree17:05
mriedemalaski: devref?17:05
alaskiwe could put it into a spec for review, but it's not really a spec in the traditional sense17:05
bauzasdansmith: I like the idea of a rst file17:06
dansmithalaski: I was thinking a blog post would be a good first thing17:06
bauzassee https://review.openstack.org/#/c/133691/17:06
dansmithVineetMenon_: yep17:06
alaskidansmith: would you want to put it out for feedback first?17:06
mriedemhttp://www.openstack.org/blog/ ?17:06
belmoreirai think is also important to take on board all the deployments that at the moment don't care about cells17:06
belmoreirabecause thay will be affected as well17:07
dansmithalaski: yeah, so maybe in a etherpad to start, then a post that can show up on the planet for wider audience17:07
*** jcook has joined #openstack-meeting-317:07
dansmithan rst in tree is good, but I think we might want to make some progress before we do that17:07
mriedem+117:07
bauzasack17:07
VineetMenon_alaski: then why not a typical BP?17:07
alaskidansmith: +117:07
mriedemthis isn't a bp17:07
dansmithbelmoreira: the goal here is that those deployments shouldn't really notice this change if they don't want to17:07
*** PaulMurray has joined #openstack-meeting-317:07
bauzasVineetMenon_: that's wider than just a specification17:07
alaskiVineetMenon_: this is more high level than a blueprint, as it's not describing specific work to be done17:08
*** stevelle has left #openstack-meeting-317:08
mriedemit's like an SLD right?17:08
dansmithright, which is why I called it a manifesto17:08
dansmithmriedem: don't bring your TLAs here17:08
dansmith:)17:08
VineetMenon_alaski: ack17:08
mriedemmuwahaha17:08
bauzasmriedem: I call PRD on my side :)17:08
*** Guest45888 has quit IRC17:08
*** pkoniszewski has quit IRC17:08
mriedemgonna be a fine line to not cram every little detail into this thing17:08
*** Longgeek has quit IRC17:08
dansmithright17:08
dansmithmanifestos are usually heavy on the goals, light on the actual details, right? :)17:09
mriedemlike deployment impacts, a history of cells and deep dive, etc17:09
*** nfedotov has quit IRC17:09
alaski#action dansmith to start an etherpad with a cellsv2 manifesto17:09
mriedemi guess17:09
mriedemwhen i think of manifesto i only think of hitler, is that wrong?17:09
bauzaswoah, first action17:09
*** Sukhdev has quit IRC17:09
leifzmanifesto == tell me why I should care...17:09
dansmithI think manifestos are usually "we want free icecream!" with no plan for how to pay for and deliver said icecream :)17:09
edleafemriedem: more like unabomber17:09
bauzasisn't what the scrum world would call an epic ? :)17:10
*** jacalcat has left #openstack-meeting-317:10
mriedemdansmith: so like a patent application :)17:10
VineetMenon_mriedem: huehue17:10
dansmithI'm suddenly uncomfortable with being tasked with the manifesto, and what that apparently connotes to people :)17:10
dansmithmriedem: heh17:10
leifzhttps://www.gnu.org/gnu/manifesto.html17:10
alaskileifz: nice save17:10
leifzit's old, but good.17:10
dansmithyeah, and similar to what I'm talking about17:11
dansmithlight on the details17:11
mriedemyeah, that's good17:11
alaskiright, details should go in specs17:11
mriedemyup17:11
alaskicool, moving on17:11
alaski#topic Checkpoints17:12
*** openstack changes topic to "Checkpoints (Meeting topic: nova-cells)"17:12
*** jtomasek has quit IRC17:12
alaskiI want to provide or get updates on various things we agreed to at the summit17:12
alaskiI now have two specs up for some initial cells work17:12
alaskihttps://review.openstack.org/135424 and https://review.openstack.org/13564417:13
*** mdbooth has joined #openstack-meeting-317:13
alaskithere will be more, but I could use as much feedback as possible17:13
dansmithjogo and I were going to try to do a first pass at table analysis..17:13
*** mdbooth has left #openstack-meeting-317:13
dansmithI don't think that needs to be a spec, right?17:13
alaskidansmith: yeah, I don't think so17:13
dansmithcool17:14
leifzdansmith: can you put it somewhere to view? just want to get my hands around this aspect if possible.17:14
alaskibut the results should live somewhere discoverable, perhaps in devref?17:14
dansmithleifz: totally17:14
mriedemdevref would be good, it's under utilized and probably pretty stale17:14
dansmithalaski: devref might be a good place eventually, so that it's easy to refer to17:14
mriedemlike does devref say anything about objects?17:14
bauzasmriedem: s/probably/obviously17:15
dansmithmy guess is that there will be a few that belong on one side or another, but need some work to make that true17:15
mriedemthe 2nd spec looks like a copy of the first when i reviewed the first yesterday17:15
dansmithso either devref will have to wait, or lie, or call those out17:15
dheeraj-gupta-4alaski: IIRC per the new specs each cell gets its own API and the cell table tells them how to contact each other?17:15
*** vishwanathj has joined #openstack-meeting-317:15
dheeraj-gupta-4alaski: for the first spec17:15
bauzasdansmith: can the analysis findings be provided in an etherpad ?17:15
alaskidansmith: I would expect it to call them out17:15
bauzasdansmith: so we can discuss on it17:16
alaskibut that is making me think an etherpad might be better for now17:16
dansmithbauzas: yeah, certainly we'll do the work in an etherpad, but if we want to argue, that's better suited for gerrit I think17:16
alaskidheeraj-gupta-4: each cell has it's own db, but there's one api17:16
alaskidheeraj-gupta-4: and the table tells the api how to contact each cell17:17
*** matrohon has quit IRC17:17
dheeraj-gupta-4alaski: Ahh OK17:17
bauzasdansmith: agreed17:17
bauzasdansmith: let's consider the etherpad as a first pass and then go to a devref file or whatever deliverable17:17
*** igordcard has quit IRC17:18
dansmithyeah, I think that's what I said :)17:18
*** belliott has joined #openstack-meeting-317:18
alaskianother action for dansmith!17:18
dansmithbah17:18
alaski#action dansmith to begin analysis of tables in an etherpad, to be moved to gerrit later17:18
alaski:)17:18
bauzasdansmith: I like paraphrasing :)17:19
dansmithjogo is suppsoed to help, so that's fine17:19
dansmithsupposed even17:19
alaskithere was quite a list of people to help on that one17:19
dansmithoh, okay cool17:19
alaski(Dan, Joe, Nikola, CERN, bauzas, NeCTAR)17:19
VineetMenon_alaski:... won't it be pertinent to discuss what all data need to reside where, at this point?17:19
dansmithall of cern is helping with that? awesome :)17:19
alaskidansmith: good luck with that17:19
dansmithVineetMenon_: that's what we're talking about17:20
belmoreirayes :)17:20
bauzasalaski: don't know who this bauzas is17:20
bauzas:)17:20
alaski:)17:20
leifzalaski: we should cross-check on our side as well.17:20
alaskiVineetMenon_: the etherpad will start that discussion.  it's a bit early to do it in a meeting17:20
VineetMenon_alaski: sure17:21
belmoreiraalaski: for the initial work what are the other specs that you are thinking ?17:21
alaskileifz: yeah, I didn't volunteer because I have a lot of other things I committed to, but Rackspace definitely has valuable input17:21
dansmithleifz: the assumption here is that existing cells people have to validate that this is reasonable17:22
alaskibelmoreira: the specs only go as far as creating new tables and the ability to use them.  We need something for a migration of data into those tables and to start using them17:22
leifzalaski: if you can't, we'll find someone to help.17:22
* leifz thinking I'm still volunteering alaski for now :-)17:22
alaskiI'll definitely be involved, just maybe more on verification than writing it17:22
mriedemthere would need to be some tool to read data from the old nova db and write into the new nova_api db right?17:23
dansmithI think that the manifesto will help us brainstorm what else we need to do along the way17:23
mriedemassuming that's a later spec17:23
alaskimriedem: right.  that's the next spec I'm looking to get together17:23
dansmithlike objects knowing whether they should talk to the api conductor or the local one, the eventlet python problem, etc17:23
belmoreiraalaski: the other thing that we discussed in the summit was testing17:24
alaskidansmith: agreed17:24
alaskibelmoreira: yep, thanks17:24
belmoreiraalaski: should that be a spec?17:24
alaskibelmoreira: I don't think so at this point17:24
mriedembelmoreira: i think it depends on changes needed to qa17:24
dansmithyeah17:24
alaskiI've been doing some work in infra for that17:24
dansmithanything we need to change in nova would be a bug17:24
mriedemif we need features in tempest, a small qa-spec is easy17:24
mriedemapparently i'm qa liasion so hopefully that goes both ways17:25
alaskiI did get a change in to exclude some tests from tempest on the experimental cells run17:25
mriedemalaski: cool, i'd like to see that change at some point later if you can dig it up17:25
*** dheeraj-gupta-4 has quit IRC17:25
*** dheeraj-gupta-4_ has joined #openstack-meeting-317:26
alaskithere's currently the issue that a flavor needs to exist in the cell db, which I'm hacking aroudn to get some data17:26
alaskiI would actually like to rely on dansmiths flavors in instance_extra patch series to ultimately resolve this though17:26
mriedemalaski: link to that for reviews?17:26
alaskibut in the meantime it might be worth considering alternatives17:26
dansmithhttps://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/flavor-from-sysmeta-to-blob,n,z17:26
mriedem#action review https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/flavor-from-sysmeta-to-blob,n,z17:27
dansmithmriedem: everything up to the last one with the WIP is good, I'm currently splitting the last one for sanity17:27
mriedemok, i'll try to focus on those17:27
alaskiI reviewed the early ones but haven't gotten through the end yet17:27
VineetMenon_alaski: what about this? https://review.openstack.org/#/c/108238/17:28
alaskiVineetMenon_: I didn't realize that had merged17:28
alaskithat may provide a short term workaround then17:28
alaski#action alaski to see if https://review.openstack.org/#/c/108238/ can be used to fix cells testing17:29
*** igordcard has joined #openstack-meeting-317:29
*** VineetMenon_ is now known as VineetMenon_Home17:29
alaskithere was also an item from the summit to get scheduling requirements from cells users17:30
bauzasagreed17:30
*** VineetMenon_Home is now known as vineet17:30
alaskijohnthetubaguy agreed to help on that, but isn't here atm... so I don't have an update there17:30
dansmithyeah, and I think he has a good handle on the issue17:30
dansmithso I think it'd be good to have him own that17:31
alaskiyeah17:31
alaskiI'll ping him specifically next time to get an update on that17:31
dansmithyeah, next meeting is late for him17:31
*** jogo has joined #openstack-meeting-317:32
alaskithat leads nicely into something I wanted to ask about17:32
alaski#topic open discussion17:32
*** openstack changes topic to "open discussion (Meeting topic: nova-cells)"17:32
*** devvesa has quit IRC17:32
alaskiI didn't get a lot of feedback on who might attend the 2200 meeting17:32
mriedemthat's 4pm for me i think so i should be able to attend17:33
belmoreirafor me ok17:33
bauzasI guess most of the EU people can't decently attend17:33
alaskiso what I'm curious about is if it actually helps anyone?17:33
bauzasoh, seems like CERN is now relocating to the US ? :)17:33
mriedemtz wise?17:33
vineetalaski: None from Asia, at least.17:33
alaskiI'm going to hold it for a bit to see who shows up, but if it's always the same group it may be easier to consolidate17:33
alaskimriedem: right17:34
mriedemsounds good17:34
dansmithI prefer consolidation of course, but yeah, not sure who else would show up in that slow17:34
dansmither, slot17:34
belmoreirabauzas: well is 2300 CET so is not to bad...17:34
dansmithmikal maybe, but I doubt he'd need to be here really17:34
bauzasbelmoreira: :)17:34
alaskidansmith: yeah, I think if we bring updates to the nova meeting he may be good17:34
dansmithyeah, so not sure who else the later meeting helps17:35
vineetwas that specifically for people in US?17:35
mriedemi think that was the plan at the summit17:35
alaskianyways, just wanted to bring it up and see if anyone here was helped by that timeslot17:35
*** dheeraj-gupta-4_ is now known as dheeraj-gupta-417:35
mriedemthe subgroups bring updates to the nova meeting, at least monthly or per milestone17:35
alaskivineet: the other slot was for asia/pacific region17:35
*** emagana has quit IRC17:35
vineetalaski: aah.17:36
*** emagana has joined #openstack-meeting-317:36
alaskiwell, we'll see how it goes17:36
alaskianyone have anything else to discuss?17:36
mriedemi guess my only open topic thing would be,17:36
mriedemwork items,17:36
mriedemlike if you think of things people can start working on now,17:37
vineetalaski: testing of present cell functionality?17:37
mriedemmake a list17:37
*** stevenld has quit IRC17:37
mriedemsince i don't know the existing cells design/code that well, if there are low hanging fruit things you want help with but don't have time, we should have a list for people to sign up,17:37
alaskimriedem: good point17:37
mriedeme.g. 'these unit tests suck, re-write them' or something, idk, like what jay did with the scheduling stuff17:37
mriedemconsider me an intern and code review monkey otherwise17:38
alaskiI'd like to get a list of what's left for testing, once I get more info about what happens when flavors is fixed17:38
alaskiand I will share that for everyone who wants to help17:38
dansmithmriedem: my guess is that you can help with the testing effort without needing to know much17:38
dansmithmriedem: I think plenty of those issues are just mechanical "didn't expect a ! in the instance name" thing or something17:38
mriedemsure17:38
mriedemif someone can just give me a task and say go, i can ask questions as needed17:39
vineetcan someone confirm this bug for me? https://bugs.launchpad.net/tempest/+bug/139422717:39
dansmithalaski: presumably you can cultivate such a list as you go along, right/17:39
leifzalaski: a good example is the GET calls may be easier to move over to the new functionality while other things are being addressed.17:39
alaskivineet: testing is mostly blocked by the flavors issue atm so that needs to be addressed first17:39
gilliardI'm in the same situation. Where would the list live?17:39
bauzasmriedem: it took some iterations to get the list we discussed at the summit for the scheduling stuff :)17:39
mriedemgilliard: thinking etherpad17:39
vineetalaski: okay.17:39
*** amotoki has quit IRC17:39
gilliardmakes sense17:39
bauzasmriedem: that's just coming from our past weekly discussions :)17:39
jogovineet: I was just looking at that bug,17:39
alaskidansmith: yes, I can keep a list going17:40
jogovineet alaski: my understanding is we aren't fixing existing cells issues17:40
vineetjogo: sure.. please let me know if you are able to reproduce it17:40
alaskiI'll get an etherpad going for that17:40
*** emagana has quit IRC17:40
mriedemvineet: check the experimental queue cells tempest job to see if that test fails there,17:40
jogojust making sure we don't code rot17:40
mriedemif the test is using security groups or something that's probably why it's failing17:40
dansmithyeah17:40
mriedemwhich i think it does, sets up a security group and then ssh's into the vm17:41
alaski#action alaski to cultivate a list of tempest tests that could use eyes or fixes17:41
mriedemi'll find a link to the cells tempest job on experimental so we can refer to that for what's failing today17:41
vineetmridem: okay.. I'll try that ASAP17:41
alaskijogo: it may be necessary to fix some issues, but mainly we're trying to adapt testing to test what currently works17:41
*** safchain has quit IRC17:42
jogoalaski: ahh17:42
mriedemyeah17:42
mriedembaseline17:42
mriedemso we don't regress cells v117:42
dansmithyeah, we probably just need to take each one17:42
alaskimriedem: https://review.openstack.org/#/c/135064/ btw17:42
mriedemalaski: thanks17:42
dansmith"is this worth fixing because it increases coverage"17:42
alaskiexactly17:43
leifzThere weren't many, but when I checked last there were a small set that dealt with the cellname mucking up our response (looked to be translation issue of some sort), but that's only a few tests.17:43
*** emagana has joined #openstack-meeting-317:44
alaskialso https://review.openstack.org/#/c/135621/ hacks around the flavors issue atm so results there are worth looking at17:44
mriedemleifz: we could disable ceilometer in the cells exp queue run if needed,17:44
mriedembut why would ceilometer muck up nova's responses?17:44
dansmithcellname17:44
*** armax has quit IRC17:44
leifzno these were http related (I don't remember the details) just went "hmmm... that's crazy we don't have the right code there".17:44
mriedemcolor me lost17:45
dansmithmriedem: he didn't say ceilometer17:45
mriedemah17:45
mriedemha17:45
leifzmriedem: CELLNAME not to be confused with a monitoring project17:45
mriedemi thought alaski was talking about that at the summit too, something about a hostname issue or something17:45
mriedemmaybe unrelated17:45
alaskimriedem: nope, same thing17:46
vineetmriedem: I'll post the nova log as well... tomorrow maybe17:46
alaskihostname is cellname!hostname in current cells17:46
mriedemi'd like to propose bubbles as the codename for the next openstack monitoring project, thanks17:46
*** Ark has joined #openstack-meeting-317:46
vineetmriedem: southpark?17:46
*** Ark is now known as Guest8216217:47
mriedemvineet: bubbles was the joke codename for cellsv217:47
mriedemor not joke, i couldn't tell17:47
dansmithI vote for Sparkly Twinkly Free Unicorn17:47
dansmithor STFU for short17:47
mriedemha17:47
vineet:D17:47
alaskion that note, anything else? :)17:47
dansmithplease no.17:47
mriedemnope17:48
alaskiexcellent17:48
alaski#endmeeting17:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:48
openstackMeeting ended Wed Nov 19 17:48:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2014/nova_cells.2014-11-19-17.00.html17:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2014/nova_cells.2014-11-19-17.00.txt17:48
alaskithanks everyone!17:48
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2014/nova_cells.2014-11-19-17.00.log.html17:48
*** dheeraj-gupta-4 has left #openstack-meeting-317:48
*** vineet has quit IRC17:48
gilliardthose links for minutes and log don't work - do I have to be more patient?17:49
*** alexsyip has joined #openstack-meeting-317:50
*** igordcard has quit IRC17:50
gilliard(there now)17:51
alaskicool.  I wasn't sure how it worked since this is my first meeting17:52
gilliardThanks. I'm UK based so won't be at the 2200 one.17:52
*** mriedem has left #openstack-meeting-317:55
*** johnbelamaric has joined #openstack-meeting-317:55
*** MaxV has quit IRC17:55
*** markmcclain has quit IRC17:55
*** markus_z has left #openstack-meeting-317:56
*** vishwanathj has quit IRC17:58
*** reed has quit IRC17:58
*** dboik_ has joined #openstack-meeting-317:58
*** dboik_ has quit IRC18:00
*** carl_baldwin has joined #openstack-meeting-318:00
*** dboik_ has joined #openstack-meeting-318:00
*** eghobo has joined #openstack-meeting-318:00
*** ajo has quit IRC18:00
*** jacalcat has joined #openstack-meeting-318:01
*** dboik has quit IRC18:02
*** armax has joined #openstack-meeting-318:03
*** dboik_ has quit IRC18:04
*** dboik has joined #openstack-meeting-318:04
*** jerdfelt has left #openstack-meeting-318:08
*** ivar-lazzaro has joined #openstack-meeting-318:08
*** eghobo has quit IRC18:09
*** PaulMurray has left #openstack-meeting-318:10
*** etoews has quit IRC18:10
*** yamamoto has quit IRC18:11
*** reed has joined #openstack-meeting-318:11
*** pballand has quit IRC18:12
*** etoews has joined #openstack-meeting-318:17
*** badveli has joined #openstack-meeting-318:17
*** armax has quit IRC18:18
*** armax has joined #openstack-meeting-318:19
*** yamahata has quit IRC18:23
*** johnbelamaric has quit IRC18:23
*** johnbelamaric has joined #openstack-meeting-318:23
*** pballand has joined #openstack-meeting-318:25
*** SridarK has joined #openstack-meeting-318:26
*** jacalcat has quit IRC18:26
*** jacalcat has joined #openstack-meeting-318:30
*** SumitNaiksatam has joined #openstack-meeting-318:31
SumitNaiksatamSridarK: badveli: hi18:32
SridarKSumitNaiksatam: hi18:32
badvelihello sumit18:32
SridarKbadveli: hi18:32
badvelihello sridar18:32
SumitNaiksatamapologies for the delay, lets get started18:32
SumitNaiksatam#startmeeting Networking FWaaS18:32
openstackMeeting started Wed Nov 19 18:32:51 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:32
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:32
openstackThe meeting name has been set to 'networking_fwaas'18:32
*** otherwiseguy has quit IRC18:33
*** pc_m has joined #openstack-meeting-318:33
*** sarob has quit IRC18:33
*** vishwanathj has joined #openstack-meeting-318:33
SumitNaiksatam#announce SPD: Monday 12-8-2014 SAD: Monday 12-15-201418:34
SumitNaiksatampc_m: vishwanathj: hi18:34
vishwanathjvi18:34
vishwanathjhi18:34
SumitNaiksatamhope the SPD and SAD dates are not too intimidating ;-)18:35
SridarKSumitNaiksatam: SPD, SAD are fast upon us18:35
SridarKdid not realize the timeline earlier either18:35
SumitNaiksatamyes, so lets focus on what we want to get in by that, we will pick that up in just a bit18:36
*** glebo has joined #openstack-meeting-318:36
SumitNaiksatam#topic Bugs18:36
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:36
badvelidecember 15th18:36
SumitNaiksatamglebo: hi18:36
SumitNaiksatam#undo18:36
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x1fe1950>18:36
SumitNaiksatamokay since we have some more critical mass here18:37
* glebo is here, but tied up on another call, so not really paying much attention. If needed, ping me unicast, and I'll pay attention to group18:37
badvelijust wanted to clarify if the spec approval is by december 15tt18:37
SumitNaiksatami wanted bring up the question that we had discussed in the adv services’ meeting as well yesterday18:37
*** arosen has left #openstack-meeting-318:38
SumitNaiksatamdo we need this sub-team and this meeting?18:38
*** LouisF has joined #openstack-meeting-318:38
SridarKbadveli: yes18:38
*** SridharRamaswamy has quit IRC18:38
badvelithanks sridar18:38
* pc_m hi. I'm multitasking meetings.18:38
SumitNaiksatambadveli: ?18:38
badvelisumit, i was confirming the spec approval date18:39
SridarKSumitNaiksatam: my vote is that it helps us discuss details as we get more into the specs and code especially18:39
*** jgallard has quit IRC18:39
SridarKSumitNaiksatam: i don't think we can discuss this in the neutron mtg18:39
SumitNaiksatamSridarK: okay, what do other folks present here think? glebo vishwanathj badveli pc_m?18:39
badvelipreviously when we wanted to discuss18:40
gleboi think we need this meeting because we are still really FAR behind the feature set required to be genuinely useful to operators, and once we get split done, we need to run like bats of out hell getting caught up, and the rest of the community doesn't need to be a part of that18:40
badveliin late juno cycle18:40
* glebo goes back to other mtg18:40
*** banix has quit IRC18:40
pc_mSumitNaiksatam: I'm just monitoring to keep a pulse on FWaaS (and make sure you're keeping things in line :)18:40
badveliwe used to join the meeting when we want18:40
SridarKglebo:  +118:40
SumitNaiksatampc_m: :-)18:40
pc_mSumitNaiksatam: Not sure if need this meeting or can include in Adv Svcs meeting as a topic.18:41
SridarKpc_m: with his baseball bat :-)18:41
badvelimy question is when we need info can we18:41
badvelijoin the meeting18:41
badveli?18:41
badvelii am fine wither way18:41
*** emagana has quit IRC18:41
badvelieither way18:41
SumitNaiksatampc_m: its proposed that this will be a standing item on the adv services meeting18:41
*** emagana has joined #openstack-meeting-318:42
SumitNaiksatampc_m: however our past experience is that we have used up the one hour of the FWaaS meetings prety regularly18:42
SumitNaiksatampc_m: and i am sure LBaaS tends to use theirs as well (in their meeting)18:42
SumitNaiksatampc_m: so i would tend to think that the adv services’ meeting would be more of an update from each of the services’ teams to the rest of the group18:43
pc_mSumitNaiksatam: That may make for the argument to keep it sep.18:43
SumitNaiksatampc_m: rather than deeper technical discussions (which we tend to have here)18:43
*** pawel-palucki has quit IRC18:43
SumitNaiksatampc_m: yeah18:43
*** marun has quit IRC18:43
pc_mSumitNaiksatam: makes sense18:43
SridarKSumitNaiksatam: i feel that this is a time that is blocked in our calendars  and an opportunity for a quick sync up to discuss issues on hand18:43
*** wuhg has quit IRC18:43
* pc_m putting bat back in drawer18:43
SumitNaiksatamSridarK: okay18:44
SridarKSumitNaiksatam: else we may land up doing this adhoc18:44
* pc_m :)18:44
vishwanathjSridarK +118:44
SridarKpc_m: Whew!  :-)18:44
SumitNaiksatamvishwanathj: okay18:44
SumitNaiksatampc_m: :-)18:44
SumitNaiksatamokay so it seems that this team wants to continue this collaboration as a sub-team, and continue the meetings as well18:44
badvelisumit, having the item in the adv service meeting will also give an opportuniy in asking qurestions which we are not sure18:44
SumitNaiksatambadveli: yes, i explained earlier what we will be doing in each of the meetings18:45
SumitNaiksatamok moving on18:45
SumitNaiksatam#topic Bugs18:45
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:45
SumitNaiksatamso we dont seem to have any new high priority bugs on reported18:46
SridarKSumitNaiksatam: yes nothing new18:46
*** emagana has quit IRC18:46
SumitNaiksatamthe highest priority one is this on the client side:18:46
SumitNaiksatam#link https://bugs.launchpad.net/python-neutronclient/+bug/131861718:47
SumitNaiksatamthe priority for this was bumped up, not sure why18:47
SumitNaiksatamlets review the patch: #link https://review.openstack.org/#/c/104132/18:48
*** marun has joined #openstack-meeting-318:48
SumitNaiksatambadveli: anything else on your bug triaging radar?18:48
badveli nothing much i am checking the other one18:49
SumitNaiksatambadveli: which other one?18:49
badvelitear down existing session18:49
badveliwhen there is an update18:49
SumitNaiksatambadveli: ah okay18:49
SridarKbadveli: the iptables issue ?18:49
badveliyes18:49
SumitNaiksatamyeah we discussed last week18:50
SumitNaiksatambadveli: can you post the link?18:50
*** hinnant_ has joined #openstack-meeting-318:51
badvelihttps://bugs.launchpad.net/neutron/+bug/138654318:51
SridarKmay be not much may need to be done on this18:51
badveliyes18:52
SridarKfrom the fw side18:52
*** bradjones has quit IRC18:52
*** emagana has joined #openstack-meeting-318:52
SumitNaiksatamok good18:52
SumitNaiksatambadveli: please keep tracking since its assigned to you18:52
SumitNaiksatam#topic Docs18:52
*** openstack changes topic to "Docs (Meeting topic: Networking FWaaS)"18:53
SumitNaiksatamSridarK: and I had an AI last week to follow up on the FWaaS/DVR documentation18:53
SridarKSumitNaiksatam: yes18:53
SumitNaiksatamjust heard back from swami18:53
SridarKyes we looks like it is WIP18:53
SumitNaiksatamSridarK: from what i understood, he will be making the doc changes?18:53
SridarKI will be in sync with Swami18:54
SridarKI could provide a description of the fw side of the world18:54
SumitNaiksatamSridarK: ok cool, perhaps we can pass the link to the rest of the team as well (should help to get more eyes on the review)18:54
SridarKanyways will sync with Swami18:54
*** armax has quit IRC18:54
SridarKok will do when i get it18:55
SumitNaiksatamSridarK: thanks18:55
*** armax has joined #openstack-meeting-318:55
SumitNaiksatamSridarK: any other docs activity showing up your radar?18:55
SridarKthe other is one is:18:55
SridarK#link https://bugs.launchpad.net/openstack-manuals/+bug/134698618:55
SridarKthis seems to be an update on a section for the Security Guide18:56
SridarKand it is quite dated - so am confused by what is actually reqd18:56
SridarKas the general docs cover FWaaS18:56
SridarKI should reach out to the submitter for some clarification - should have done that earlier - apologies18:57
SumitNaiksatamyeah this is the one which rudrajit was assigned to18:57
SridarKwill take care of this18:57
SumitNaiksatamseems to be sitting there for a long time18:57
SridarKif it is not relevant we can close it18:57
SumitNaiksatamnot sure if its even relevant any more18:57
SumitNaiksatamyeah exactly18:57
SridarKyes and it involves a lot of other things not just fwaas18:57
SumitNaiksatamthere are a bunch of doc bugs mentioned in the neutron meeting:18:57
SumitNaiksatam#link https://wiki.openstack.org/wiki/Network/Meetings18:57
SumitNaiksatamwe need to scrub this list to see if there is anything that we need to contribute to18:58
SumitNaiksatam#link https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=neutron18:59
SridarKSumitNaiksatam: i will do this and reach out to Edgar if more clarification is needed18:59
SumitNaiksatamSridarK: great, thanks@18:59
*** sarob has joined #openstack-meeting-318:59
SumitNaiksatamits interesting there are references to quantum in that list ;-)18:59
SridarK:-)18:59
SridarKi would like to see positron or quark or whatever in the next cycle :-)19:00
SumitNaiksatami think we need to pay attention to this: #lik https://bugs.launchpad.net/openstack-manuals/+bug/137367419:00
SumitNaiksatam#link https://bugs.launchpad.net/openstack-manuals/+bug/137367419:00
*** otherwiseguy has joined #openstack-meeting-319:00
SumitNaiksatamperhaps follow up with anne gentle on this19:01
SumitNaiksatamSridarK: you want to take that AI?19:01
SridarKSumitNaiksatam: yes pls19:01
SumitNaiksatam#action SridarK to follow up with ann gentle on #link https://bugs.launchpad.net/openstack-manuals/+bug/137367419:02
SumitNaiksatamSridarK: please cc me (and anyone else interested) as well, so that we can jump in if required19:02
SridarKSumitNaiksatam: will do19:02
SumitNaiksatamSridarK: thanks19:03
SumitNaiksatammoving on19:03
badveli yes19:03
SumitNaiksatam#topic Kilo Blueprints19:03
*** openstack changes topic to "Kilo Blueprints (Meeting topic: Networking FWaaS)"19:03
*** marun has quit IRC19:03
*** marun_ has joined #openstack-meeting-319:03
SumitNaiksatambadveli’s security objects and groups:19:03
badveli   yes sumit19:03
*** shwetaap1 has quit IRC19:04
SridarKbadveli: thanks for addressing my review comments19:04
SumitNaiksatam#link https://review.openstack.org/#/c/131596/19:04
badvelithanks sridar, for review19:04
badveli i think sumit wants to rephrase some of them19:04
SridarKbadveli: i think once u have addressed the latest round from SumitNaiksatam - i think i am good19:05
SumitNaiksatami added some review comments19:05
SumitNaiksatambadveli: thanks19:05
badveli yes i am in the process, but one thing in the work items19:05
*** shwetaap has joined #openstack-meeting-319:05
badveli how can we explain more19:05
SumitNaiksatami had mentioned this process, we need to tighten up the content otherwise it creates unnecessary misunderstanding19:06
badveli my problem is if i do not put them after *19:06
SumitNaiksatamand we should not have to waste cycles on grammar and typos19:06
*** MaxV has joined #openstack-meeting-319:06
*** jcook has left #openstack-meeting-319:06
SumitNaiksatamthis should be run through spell checkers upfront19:06
SumitNaiksatamhaving reviewers tell you to correct grammar, and then having to spend the back and forth cycles on doing it, is just a big waste of time19:07
badveli do we have some kind of tool19:07
SumitNaiksatambadveli: be creative :-)19:07
badveli i am just editing in the vi,19:07
SumitNaiksatameasy to copy paste in a word-like editor :-)19:07
SumitNaiksatamokay, any other objections or blockers on the techincal front with respect to this blueprint?19:08
SumitNaiksatamor any suggestions for badveli?19:08
SridarKSumitNaiksatam: none from me - i think the model resembles Sec Grps19:08
SumitNaiksatamSridarK: okay19:09
SridarKSumitNaiksatam: badveli confirmed this in terms of object to group association19:09
badveli thanks sridar19:09
SumitNaiksatamSridarK: that we cannot resuse objects across groups?19:09
SridarKSumitNaiksatam: yes19:09
SumitNaiksatamokay19:09
SridarKSumitNaiksatam: we can take a call on the approach19:10
SumitNaiksatamthe reuse is at the group level19:10
SridarKSumitNaiksatam: yes19:10
*** emagana has quit IRC19:10
badveliyes19:10
*** MaxV has quit IRC19:10
*** emagana has joined #openstack-meeting-319:11
SumitNaiksatamso this is consistent with the FWaaS rule and policy association as well, right?19:11
*** marun_ has quit IRC19:11
SridarKSumitNaiksatam: i think this is fine but this should not become a roadblock on Dec 14 - i think this kind of adopts the Sec grp way of doing things19:11
*** yamamoto has joined #openstack-meeting-319:11
badveli yes this is similar to sec grp way19:11
SumitNaiksatamwe cant reuse rules across firewall policies19:11
*** marun_ has joined #openstack-meeting-319:11
SumitNaiksatam*firewall rules19:12
SridarKSumitNaiksatam: yes so this is consistent19:12
badveli yes19:12
*** emagana_ has joined #openstack-meeting-319:13
*** emagana has quit IRC19:13
SridarKas long as we are clear there is no issue here19:13
SumitNaiksatamso once badveli puts out the new rev, lets try to push forward19:14
SumitNaiksatamglebo: did you get a response to the email you had sent regarding the service groups blueprint?19:14
SridarKbadveli: after ur next rev - i will go thru one other scan and i can +119:14
gleboSumitNaiksatam: I don't think so19:15
* glebo double checking now19:15
badveli  thanks sridar, sumit19:15
SumitNaiksatamglebo: okay, yeah just checking, since i did not see anything19:15
*** dboik has quit IRC19:15
*** yamamoto has quit IRC19:16
*** marun has joined #openstack-meeting-319:16
SumitNaiksatamthe next one we are tracking is the router-specific firewall insertion19:18
SumitNaiksatamSridarK: any progress?19:18
SridarKSumitNaiksatam: few options19:18
SridarKOption 1: Revive Service Insertion - i am not sure about how this will fly.19:18
SridarKOption 2: Insert FW on a specific Router. (what Mark wanted)19:18
SridarKOption 3: Insert FW on neutron port(s) (we can validate to ensure that if it is a list they are all associated with a single router)19:18
SridarKMy personal opinion is that if we are not doing Option 1, Option 3 is reasonable - it can achieve the requirement from Mark and yet is more flexible.19:19
*** marun_ has quit IRC19:19
SridarKthe Spec deadlines got me boltibg19:19
SridarK*bolting19:19
bobmelI agree, why essentially waste effort on a something halfbacked as option 219:19
SumitNaiksatamSridarK: yeah i dont think we are doing option 119:19
SridarKi have started putting things down for a spec19:19
SumitNaiksatambobmel: i agree, though that comes with the risk of a -219:20
SridarKwill get a first cut out by end of week19:20
SumitNaiksatamand i am willing to vote in favor of that option if everyone in the team here feels likewise19:20
SridarKbobmel: yes19:20
SumitNaiksatambobmel: btw, welcome to the fwaas meeting ;-)19:20
bobmelSumitNaiksatam: Yes but it is a bit insane to -2 something that is more useful in practice19:21
SumitNaiksatambobmel: i will let history speak for itself! ;-)19:21
bobmelSumitNaiksatam: Like pc_m I monitor every step... :-) Hope I can actively contribute going forward though.19:21
s3wongSridarK: option 1 is already rejected by markmcclain --- during Friday's meeting in Paris, markmcclain talked about FW able to run on selected routers without a new service insertion framework19:21
SridarKbobmel: yes agree i think we can find a reasonable ground19:21
*** marun has quit IRC19:22
SumitNaiksatamah s3wong, we have lots of people watching over our shoulders today! :-)19:22
SridarKs3wong: yes i think we can work with option 3 that will satisfy the requirement19:22
SumitNaiksatamand i thought we were lacking critical mass19:22
SridarKhopefully no one came with weapons19:23
SridarK:-)19:23
SumitNaiksatamSridarK: lol19:23
SumitNaiksatamSridarK: sorry to push, any ETA on posting the spec?19:23
SridarKSumitNaiksatam: ok i will put things down in a spec19:23
s3wongSridarK: keep in mind that markmcclain wants to have the ability to backport to stable branches, so a new framework would be out of question, too much to port19:23
SridarKwill try for end of week19:23
SridarKs3wong: hmm we will need to add an extension19:24
s3wongSumitNaiksatam: just got out of my day job meeting -- and was attracted by the term "service insertion" :-)19:24
SridarKs3wong: u are a riot (meant as a compliment) :-)19:25
SumitNaiksatamSridarK: not sure why an extension is required19:25
SumitNaiksatamSridarK: but lets take it offline19:25
SridarKSumitNaiksatam: u are saying add it as an attribute to the resource19:25
SridarKSumitNaiksatam: yes we can discuss more19:25
SumitNaiksatamSridarK: i am also curious as to what the default would be with ports19:25
*** armax has quit IRC19:26
SumitNaiksatamSridarK: i am sure you have given this thought, so lets see it in the spec19:26
*** belmoreira has quit IRC19:26
SumitNaiksatamSridarK: as far as the spec is concerned, you can keep it simple and cut to the chase19:26
SumitNaiksatamSridarK: easier to read that way :-)19:26
SridarKSumitNaiksatam: more thought is needed here - will ping u offline19:26
badveli  please let me know also when you are discussing this19:26
SridarKSumitNaiksatam: yes will do19:26
SumitNaiksatamSridarK: extra details can be added per request19:26
* glebo just resent that email to mestery & markmcclain trying to nail down required reviewers for Service Object & Groups spec19:27
SridarKbadveli: sure19:27
SridarKSumitNaiksatam: ok sounds good19:27
SumitNaiksatamanything else to discuss on this topic?19:27
SridarKSumitNaiksatam: nothing from me19:27
SumitNaiksatam#topic Open Discussion19:27
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:27
*** dboik has joined #openstack-meeting-319:27
SumitNaiksatamanything more to cover for today?19:27
SridarKSumitNaiksatam: we wil also be pushing a vendor bp19:27
SumitNaiksatamSridarK: sure19:28
*** dboik has quit IRC19:28
SridarKit is out already ( i have resubmitted from Juno)19:28
SumitNaiksatamanyone else planning to push a vendor bp, so that we can track it?19:28
SumitNaiksatamfwass-related that is19:28
SridarKvishwanathj: ?19:28
vishwanathjBrocade will soon19:28
*** dboik has joined #openstack-meeting-319:28
SridarKvishwanathj: if u have intent for Kilo u should do that soon19:28
vishwanathjSridarK, understood19:29
*** armax has joined #openstack-meeting-319:29
pc_mFYI: I'm starting on some L3 agent refactoring. Starting with extracting out device driver logic. Please look at https://review.openstack.org/#/c/135392/ if you get a chance.19:29
SridarKvishwanathj: karhik will need to get his router stuff out too19:29
SumitNaiksatamvishwanathj: yeah, you might have missed earlier, SPD: Monday 12-8-2014 SAD: Monday 12-15-201419:29
pc_mTeasing out FW, VPN, LB device driver loading.19:29
SridarK*karthik19:29
vishwanathjSridarK, I think Karthik already did that for the router last week19:29
*** dt_os has joined #openstack-meeting-319:29
SridarKok19:30
SumitNaiksatampc_m: sweet, great that you could get started on this19:30
pc_mwould love and FW centric feedback on what's happening there.19:30
SumitNaiksatampc_m: is such situations it will help proactively add us reviewers so that it readily shows up on our radars19:30
*** armax has quit IRC19:30
vishwanathjSumitNaiksatam: What is SPD and what is SAD19:30
pc_m(and LB too)19:30
*** markmcclain has joined #openstack-meeting-319:30
SumitNaiksatamvishwanathj: spec proposal deadline, spec approval deadline19:31
*** markmcclain has quit IRC19:31
SridarKpc_m: u have my feedback19:31
vishwanathjThanks19:31
pc_mSridarK: Thanks!19:31
SumitNaiksatamvishwanathj: propose the spec latest by the first deadline and get it approved by the second19:31
SumitNaiksatamok thanks all19:31
SumitNaiksatamwe are minute over19:31
SridarKbye19:31
SumitNaiksatamthanks for joining19:31
vishwanathjOk19:31
SumitNaiksatambye!19:31
vishwanathjbye19:31
SridarKvishwanathj: ping me offline19:31
SumitNaiksatam#endmeeting19:31
badveli  bye19:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:31
openstackMeeting ended Wed Nov 19 19:31:44 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-11-19-18.32.html19:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-11-19-18.32.txt19:31
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-11-19-18.32.log.html19:31
SridarKvishwanathj: i can clarify some things around spec19:32
*** pc_m has left #openstack-meeting-319:32
vishwanathjSridarK thanks19:32
SridarKnp19:32
*** julim has quit IRC19:33
*** ivar-laz_ has joined #openstack-meeting-319:34
*** ivar-laz_ has quit IRC19:34
*** baoli has quit IRC19:34
*** ivar-laz_ has joined #openstack-meeting-319:35
*** Sukhdev has joined #openstack-meeting-319:35
*** dboik has quit IRC19:35
*** armax has joined #openstack-meeting-319:35
*** SridarK has quit IRC19:36
*** LouisF has quit IRC19:36
*** marun has joined #openstack-meeting-319:37
*** ivar-lazzaro has quit IRC19:37
*** dt_os has quit IRC19:38
*** ivar-laz_ has quit IRC19:38
*** ivar-lazzaro has joined #openstack-meeting-319:39
*** carl_baldwin has quit IRC19:39
*** SridharRamaswamy has joined #openstack-meeting-319:39
*** marun_ has joined #openstack-meeting-319:42
*** dboik has joined #openstack-meeting-319:44
*** marun has quit IRC19:44
*** sarob has quit IRC19:45
*** carl_baldwin has joined #openstack-meeting-319:45
*** jtomasek has joined #openstack-meeting-319:47
*** mwang2 has joined #openstack-meeting-319:49
*** dboik has quit IRC19:50
*** otherwiseguy has quit IRC19:50
*** ivar-laz_ has joined #openstack-meeting-319:51
*** marun_ has quit IRC19:51
*** otherwiseguy has joined #openstack-meeting-319:52
*** marun_ has joined #openstack-meeting-319:53
*** ivar-lazzaro has quit IRC19:54
*** MaxV has joined #openstack-meeting-319:55
*** matrohon has joined #openstack-meeting-319:57
*** ivar-laz_ has quit IRC20:01
*** emagana_ has quit IRC20:01
*** emagana has joined #openstack-meeting-320:02
*** dboik has joined #openstack-meeting-320:02
*** dboik has quit IRC20:03
*** gholler has quit IRC20:03
*** etoews_ has joined #openstack-meeting-320:03
*** dboik has joined #openstack-meeting-320:03
*** emagana_ has joined #openstack-meeting-320:05
*** otherwiseguy has quit IRC20:05
*** emagana has quit IRC20:06
*** etoews has quit IRC20:07
*** matrohon is now known as matrohon_20:09
*** ivar-lazzaro has joined #openstack-meeting-320:09
*** marun_ has quit IRC20:09
*** matrohon_ is now known as matrohon20:09
*** banix has joined #openstack-meeting-320:09
*** david-lyle is now known as david-lyle_afk20:10
*** markmcclain has joined #openstack-meeting-320:11
*** cbouch has quit IRC20:12
*** MaxV has quit IRC20:16
*** MaxV has joined #openstack-meeting-320:16
*** otherwiseguy has joined #openstack-meeting-320:17
*** marun has joined #openstack-meeting-320:20
*** edhall_ has left #openstack-meeting-320:24
*** ivar-lazzaro has quit IRC20:26
*** sarob has joined #openstack-meeting-320:31
*** julim has joined #openstack-meeting-320:38
*** ajo has joined #openstack-meeting-320:39
*** julim has quit IRC20:39
*** julim has joined #openstack-meeting-320:41
*** jtomasek has quit IRC20:46
*** emagana_ has quit IRC20:55
*** ajo has quit IRC20:57
*** ivar-lazzaro has joined #openstack-meeting-320:57
*** ajo has joined #openstack-meeting-320:58
*** emagana_ has joined #openstack-meeting-320:59
*** SridharRamaswamy has quit IRC21:00
*** emagana_ has quit IRC21:01
*** emagana has joined #openstack-meeting-321:02
*** johnbelamaric_ has joined #openstack-meeting-321:04
*** johnbelamaric has quit IRC21:04
*** julim has quit IRC21:04
*** lhcheng_ has left #openstack-meeting-321:06
*** julim has joined #openstack-meeting-321:07
*** otherwiseguy has quit IRC21:09
*** ivar-lazzaro has quit IRC21:10
*** ivar-lazzaro has joined #openstack-meeting-321:10
*** otherwiseguy has joined #openstack-meeting-321:10
*** shakamunyi_ has joined #openstack-meeting-321:12
*** yamamoto has joined #openstack-meeting-321:14
*** johnbelamaric_ has quit IRC21:15
*** ivar-lazzaro has quit IRC21:15
*** johnbelamaric_ has joined #openstack-meeting-321:15
*** yamamoto has quit IRC21:18
*** armax has quit IRC21:25
*** sigmavirus24 is now known as sigmavirus24_awa21:26
*** emagana has quit IRC21:27
*** emagana has joined #openstack-meeting-321:28
*** armax has joined #openstack-meeting-321:31
*** emagana has quit IRC21:33
*** baoli has joined #openstack-meeting-321:33
*** sarob has quit IRC21:34
*** Sukhdev has quit IRC21:34
*** bpokorny has quit IRC21:37
*** jacalcat has quit IRC21:40
*** Guest82162 has quit IRC21:42
*** peristeri has quit IRC21:43
*** salv-orlando_ has joined #openstack-meeting-321:44
*** salv-orlando has quit IRC21:44
*** salv-orlando_ is now known as salv-orlando21:44
*** emagana has joined #openstack-meeting-321:46
*** vishwanathj has quit IRC21:48
*** carl_baldwin has quit IRC21:51
*** jimhoagland has joined #openstack-meeting-321:53
*** carl_baldwin has joined #openstack-meeting-321:54
*** emagana has quit IRC21:56
*** mrmartin has quit IRC21:56
*** emagana has joined #openstack-meeting-321:56
*** shakamunyi_ has quit IRC21:59
*** SridharRamaswamy has joined #openstack-meeting-322:01
*** emagana has quit IRC22:02
*** emagana has joined #openstack-meeting-322:03
*** bpokorny has joined #openstack-meeting-322:06
*** emagana has quit IRC22:07
*** ivar-lazzaro has joined #openstack-meeting-322:08
*** Sukhdev has joined #openstack-meeting-322:08
*** sergef has quit IRC22:09
*** banix has quit IRC22:09
*** jacalcat has joined #openstack-meeting-322:10
*** shwetaap has quit IRC22:10
*** mwagner_lap has quit IRC22:10
*** ajo has quit IRC22:12
*** johnbelamaric_ has quit IRC22:13
*** bpokorny_ has joined #openstack-meeting-322:13
*** bpokorny has quit IRC22:16
*** emagana has joined #openstack-meeting-322:16
*** jimhoagland has quit IRC22:16
*** johnbelamaric_ has joined #openstack-meeting-322:18
*** matrohon has quit IRC22:18
*** johnbelamaric_ has quit IRC22:18
*** sigmavirus24_awa is now known as sigmavirus2422:18
*** kevinbenton has joined #openstack-meeting-322:27
*** baoli_ has joined #openstack-meeting-322:28
*** baoli has quit IRC22:29
*** marun has quit IRC22:29
*** emagana has quit IRC22:34
*** emagana has joined #openstack-meeting-322:35
*** baoli_ has quit IRC22:39
*** baoli has joined #openstack-meeting-322:39
*** emagana has quit IRC22:39
*** bpokorny_ has quit IRC22:39
*** jimhoagland has joined #openstack-meeting-322:39
*** marun has joined #openstack-meeting-322:42
*** bpokorny has joined #openstack-meeting-322:42
*** marun_ has joined #openstack-meeting-322:49
*** dboik has quit IRC22:49
*** david-lyle_afk is now known as david-lyle22:50
*** glebo has quit IRC22:50
*** marun has quit IRC22:50
*** emagana has joined #openstack-meeting-322:55
*** MaxV has quit IRC22:56
*** mwagner_lap has joined #openstack-meeting-323:02
*** bpokorny_ has joined #openstack-meeting-323:02
*** otherwiseguy has quit IRC23:04
*** bpokorny has quit IRC23:05
*** ivar-laz_ has joined #openstack-meeting-323:05
*** ivar-laz_ has quit IRC23:06
*** armax has quit IRC23:06
*** ivar-laz_ has joined #openstack-meeting-323:07
*** ivar-lazzaro has quit IRC23:08
*** markmcclain has quit IRC23:11
*** gaitan_ has quit IRC23:18
*** gaitan has joined #openstack-meeting-323:19
*** carl_baldwin has quit IRC23:19
*** ivar-laz_ has quit IRC23:30
*** etoews has joined #openstack-meeting-323:32
*** marun_ has quit IRC23:34
*** etoews_ has quit IRC23:35
*** jacalcat has left #openstack-meeting-323:35
*** sigmavirus24 is now known as sigmavirus24_awa23:37
*** julim has quit IRC23:39
*** Adri2000 has quit IRC23:42
*** ycombinator_ has joined #openstack-meeting-323:43
*** sarob has joined #openstack-meeting-323:46
*** Adri2000 has joined #openstack-meeting-323:49
*** Adri2000 has quit IRC23:49
*** Adri2000 has joined #openstack-meeting-323:49
*** etoews has quit IRC23:51
*** s3wong has quit IRC23:55
*** pballand has quit IRC23:57
*** ycombinator_ has quit IRC23:58

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