Wednesday, 2014-11-26

*** banix has quit IRC00:00
*** thinrichs has joined #openstack-meeting-300:00
*** Guest8043 has quit IRC00:02
*** carl_baldwin has quit IRC00:04
*** dboik_ has quit IRC00:04
*** emagana has joined #openstack-meeting-300:16
*** ChuckC_ has quit IRC00:18
*** SridharRamaswamy has quit IRC00:19
*** Sukhdev has joined #openstack-meeting-300:20
*** ycombina_ has joined #openstack-meeting-300:22
*** emagana has quit IRC00:23
*** emagana has joined #openstack-meeting-300:23
*** ycombinator_ has quit IRC00:23
*** ycombinator_ has joined #openstack-meeting-300:24
*** ChuckC_ has joined #openstack-meeting-300:25
*** alexsyip has quit IRC00:26
*** ycombina_ has quit IRC00:27
*** emagana has quit IRC00:28
*** hurgleburgler has quit IRC00:34
*** emagana has joined #openstack-meeting-300:35
*** emagana has quit IRC00:35
*** emagana has joined #openstack-meeting-300:35
*** julim has joined #openstack-meeting-300:40
*** SridharRamaswamy has joined #openstack-meeting-300:40
*** clu_ has quit IRC00:41
*** yamamoto has joined #openstack-meeting-300:44
*** ongk has joined #openstack-meeting-300:47
*** alexpilotti has quit IRC00:51
*** david-lyle is now known as david-lyle_afk00:51
*** thinrichs has quit IRC00:51
*** baoli has joined #openstack-meeting-300:56
*** emagana has quit IRC00:57
*** emagana has joined #openstack-meeting-300:58
*** yamahata has joined #openstack-meeting-301:01
*** emagana has quit IRC01:02
*** eliqiao has joined #openstack-meeting-301:03
*** eliqiao has quit IRC01:04
*** salv-orlando has quit IRC01:07
*** yamamoto has quit IRC01:08
*** stanzgy has joined #openstack-meeting-301:09
*** amotoki has joined #openstack-meeting-301:10
*** eliqiao has joined #openstack-meeting-301:12
*** baoli has quit IRC01:19
*** baoli has joined #openstack-meeting-301:30
*** MaxV_ has quit IRC01:31
*** bpokorny has quit IRC01:45
*** ycombinator_ has quit IRC01:52
*** wuhg has joined #openstack-meeting-301:52
*** ongk has quit IRC01:54
*** marun has quit IRC01:55
*** devlaps has quit IRC02:04
*** lhcheng has quit IRC02:04
*** ongk has joined #openstack-meeting-302:05
*** emagana has joined #openstack-meeting-302:06
*** emagana_ has joined #openstack-meeting-302:07
*** emagana has quit IRC02:10
*** Ark has joined #openstack-meeting-302:11
*** Ark is now known as Guest3413802:12
*** etoews has joined #openstack-meeting-302:12
*** etoews has quit IRC02:17
*** banix has joined #openstack-meeting-302:18
*** Sukhdev has quit IRC02:20
*** Sukhdev has joined #openstack-meeting-302:21
*** yamamoto has joined #openstack-meeting-302:22
*** MarkAtwood has quit IRC02:28
*** etoews has joined #openstack-meeting-302:30
*** MaxV has joined #openstack-meeting-302:32
*** etoews has quit IRC02:36
*** MaxV has quit IRC02:37
*** MarkAtwood has joined #openstack-meeting-302:38
*** SridharRamaswamy has quit IRC02:39
*** aleksandr_null has quit IRC02:52
*** banix has quit IRC02:54
*** MarkAtwood has quit IRC02:59
*** Sukhdev has quit IRC03:01
*** etoews has joined #openstack-meeting-303:02
*** banix has joined #openstack-meeting-303:06
*** etoews has quit IRC03:06
*** aleksandr_null has joined #openstack-meeting-303:08
*** vkmc has quit IRC03:12
*** shwetaap has joined #openstack-meeting-303:21
*** etoews has joined #openstack-meeting-303:44
*** sarob has joined #openstack-meeting-303:45
*** emagana_ has quit IRC03:48
*** emagana has joined #openstack-meeting-303:48
*** emagana has quit IRC03:49
*** sarob has quit IRC03:49
*** emagana has joined #openstack-meeting-303:50
*** thinrichs has joined #openstack-meeting-303:50
*** thinrichs has quit IRC03:52
*** ivar-lazzaro has quit IRC03:53
*** thinrichs has joined #openstack-meeting-304:21
*** MaxV has joined #openstack-meeting-304:22
*** etoews has quit IRC04:22
*** MaxV has quit IRC04:25
*** Sukhdev has joined #openstack-meeting-304:26
*** flwang1 has quit IRC04:27
*** emagana has quit IRC04:28
*** banix has quit IRC04:34
*** seizadi has joined #openstack-meeting-305:04
*** thinrichs has quit IRC05:15
*** emagana has joined #openstack-meeting-305:29
*** Longgeek has joined #openstack-meeting-305:38
*** Longgeek has quit IRC05:44
*** Guest34138 has quit IRC05:47
*** simon-AS559 has joined #openstack-meeting-305:48
*** simon-AS5591 has joined #openstack-meeting-305:50
*** simon-AS559 has quit IRC05:53
*** simon-AS5591 has quit IRC05:59
*** k4n0 has joined #openstack-meeting-306:03
*** Ark has joined #openstack-meeting-306:17
*** Ark is now known as Guest541606:18
*** Sukhdev has quit IRC06:22
*** Longgeek has joined #openstack-meeting-306:22
*** mrmartin has joined #openstack-meeting-306:23
*** ycombinator_ has joined #openstack-meeting-306:25
*** Guest5416 has quit IRC06:26
*** etoews has joined #openstack-meeting-306:26
*** etoews has quit IRC06:30
*** SumitNaiksatam has quit IRC06:38
*** SumitNaiksatam has joined #openstack-meeting-306:39
*** emagana has quit IRC06:43
*** emagana has joined #openstack-meeting-306:43
*** etoews has joined #openstack-meeting-306:45
*** belmoreira has joined #openstack-meeting-306:46
*** emagana has quit IRC06:48
*** etoews has quit IRC06:49
*** ycombinator_ has quit IRC06:55
*** jtomasek has joined #openstack-meeting-306:55
*** jtomasek has quit IRC07:00
*** mrunge has joined #openstack-meeting-307:04
*** etoews has joined #openstack-meeting-307:17
*** etoews has quit IRC07:22
*** simon-AS559 has joined #openstack-meeting-307:28
*** jtomasek has joined #openstack-meeting-307:36
*** evgenyf has joined #openstack-meeting-307:43
*** SumitNaiksatam has quit IRC07:46
*** jtomasek has quit IRC07:47
*** SumitNaiksatam has joined #openstack-meeting-307:49
*** jaypipes has quit IRC07:50
*** armax has quit IRC07:55
*** salv-orlando has joined #openstack-meeting-308:02
*** jtomasek has joined #openstack-meeting-308:04
*** sergef has joined #openstack-meeting-308:06
*** sergef_ has joined #openstack-meeting-308:09
*** sergef has quit IRC08:11
*** sergef_ is now known as sergef08:11
*** seizadi has quit IRC08:16
*** matrohon has joined #openstack-meeting-308:17
*** zz_ttrifonov is now known as ttrifonov08:17
*** yamahata has quit IRC08:18
*** ttrifonov is now known as zz_ttrifonov08:19
*** zz_ttrifonov is now known as ttrifonov08:20
*** jcoufal has joined #openstack-meeting-308:29
*** matrohon has quit IRC08:33
*** MaxV has joined #openstack-meeting-308:40
*** SumitNaiksatam has quit IRC08:51
*** SumitNaiksatam has joined #openstack-meeting-308:52
*** matrohon has joined #openstack-meeting-308:53
*** safchain has joined #openstack-meeting-308:54
*** SumitNaiksatam has quit IRC08:56
*** mvineet has joined #openstack-meeting-308:57
*** mvineet is now known as vineetmenon08:57
*** SumitNaiksatam has joined #openstack-meeting-309:00
vineetmenonalaski: Do we have meeting today nova-cell-v2? if yes at what time? 1700 UTC or 2200 UTC?09:01
*** amotoki has quit IRC09:11
*** flwang1 has joined #openstack-meeting-309:28
*** yamamoto has quit IRC09:32
*** Longgeek_ has joined #openstack-meeting-309:38
*** Longgeek has quit IRC09:39
*** yamahata has joined #openstack-meeting-309:45
*** Ark has joined #openstack-meeting-309:47
*** Ark is now known as Guest5539509:48
*** Guest55395 has quit IRC09:53
*** iovadia has joined #openstack-meeting-309:56
*** jcoufal_ has joined #openstack-meeting-309:57
*** iovadia1 has joined #openstack-meeting-309:57
*** pkoniszewski has joined #openstack-meeting-309:59
*** jcoufal has quit IRC10:00
*** iovadia has quit IRC10:00
*** evgenyf has quit IRC10:28
*** scheuran has joined #openstack-meeting-310:31
*** yamahata has quit IRC10:43
*** yamahata has joined #openstack-meeting-310:45
*** stanzgy has quit IRC10:50
*** shwetaap has quit IRC11:05
*** evgenyf has joined #openstack-meeting-311:06
*** shwetaap has joined #openstack-meeting-311:09
*** shwetaap has quit IRC11:11
*** simon-AS5591 has joined #openstack-meeting-311:13
*** simon-AS559 has quit IRC11:16
*** salv-orlando has quit IRC11:29
*** pkarikh has quit IRC11:34
*** vkmc has joined #openstack-meeting-311:34
*** gholler has joined #openstack-meeting-311:37
*** iovadia1 has quit IRC11:45
*** flwang1 has quit IRC11:56
*** iovadia has joined #openstack-meeting-311:57
*** baoli has quit IRC12:10
*** salv-orlando has joined #openstack-meeting-312:20
*** pkarikh has joined #openstack-meeting-312:46
*** jcoufal_ has quit IRC12:47
*** jcoufal has joined #openstack-meeting-312:48
*** eliqiao has quit IRC12:49
*** baoli has joined #openstack-meeting-312:54
*** xuhanp has joined #openstack-meeting-312:57
*** banix has joined #openstack-meeting-313:01
*** banix has quit IRC13:04
*** Longgeek_ has quit IRC13:11
*** ycombinator_ has joined #openstack-meeting-313:12
*** julim has quit IRC13:19
*** alexpilotti has joined #openstack-meeting-313:21
*** alexpilotti has quit IRC13:32
*** safchain has quit IRC13:33
*** safchain has joined #openstack-meeting-313:33
*** jaypipes has joined #openstack-meeting-313:36
*** mestery has quit IRC13:36
*** Longgeek has joined #openstack-meeting-313:37
*** baoli has quit IRC13:37
*** baoli has joined #openstack-meeting-313:44
*** julim has joined #openstack-meeting-313:49
*** shwetaap has joined #openstack-meeting-313:50
*** shwetaap has quit IRC13:50
*** shwetaap has joined #openstack-meeting-313:50
*** zhipeng has joined #openstack-meeting-313:50
*** yamahata has quit IRC13:50
*** erw has quit IRC13:51
*** yamahata has joined #openstack-meeting-313:51
*** beagles has quit IRC13:52
*** erw has joined #openstack-meeting-313:53
*** xuhanp has quit IRC14:01
*** jacalcat has joined #openstack-meeting-314:04
*** jacalcat has left #openstack-meeting-314:04
*** mestery has joined #openstack-meeting-314:05
*** pkoniszewski has quit IRC14:08
*** sigmavirus24_awa is now known as sigmavirus2414:08
*** beagles has joined #openstack-meeting-314:09
*** beagles is now known as Guest589914:09
*** gholler_ has joined #openstack-meeting-314:09
*** shwetaap1 has joined #openstack-meeting-314:09
*** Guest5899 is now known as b3nt_pin14:12
*** b3nt_pin is now known as Guest4786014:12
*** gholler has quit IRC14:13
*** shwetaap has quit IRC14:13
*** gholler_ has quit IRC14:13
*** peristeri has joined #openstack-meeting-314:17
*** ameade_ has quit IRC14:18
*** johnbelamaric has joined #openstack-meeting-314:19
*** ameade_ has joined #openstack-meeting-314:20
*** johnbelamaric has left #openstack-meeting-314:21
*** peristeri has quit IRC14:28
*** Ark has joined #openstack-meeting-314:30
*** Ark is now known as Guest6203614:30
*** jgrimm is now known as zz_jgrimm14:32
*** Longgeek has quit IRC14:34
*** Guest62036 has quit IRC14:34
*** peristeri has joined #openstack-meeting-314:34
*** armax has joined #openstack-meeting-314:36
*** Longgeek has joined #openstack-meeting-314:40
*** Guest47860 has quit IRC14:41
alaskivineetmenon: it's at 2200 today.  I am going to show up for it but I'm guessing it will be really light and fast today14:42
*** mestery has quit IRC14:48
*** xuhanp has joined #openstack-meeting-314:49
*** dboik has joined #openstack-meeting-314:52
*** amuller has joined #openstack-meeting-314:56
*** markmcclain has joined #openstack-meeting-314:58
*** seizadi has joined #openstack-meeting-314:59
*** etoews has joined #openstack-meeting-315:01
*** mattfarina has joined #openstack-meeting-315:02
amullerarmax: drivers meeting is supposed to be now right?15:03
armaxamuller: I am actually confused, but I think it might start in 30 mins15:03
armaxmestery is offline so I suspect that’s the case15:04
armaxhang on, just a tad longer ;)15:04
*** wuhg has quit IRC15:05
*** wuhg has joined #openstack-meeting-315:05
salv-orlandoaloha fellow drivers.15:05
salv-orlandoarmax I now recalled that it’s actually in 24 minutes15:06
vineetmenonalaski: yeah.. it will be fast today.. Only 'Pacificers' and some owls from Europe, IMO. :)15:06
salv-orlandomestery move it but we never updated our calendars I think15:06
armaxthe meeting page says the meeting starts on the half of the hour15:07
armaxso I am going to flood myself with a pint of coffee15:07
amullerTonight: Tragedy in California; Man literally drowns himself in coffee15:08
*** beagles has joined #openstack-meeting-315:10
*** jcoufal has quit IRC15:10
*** beagles is now known as Guest7475215:10
*** ycombinator_ has quit IRC15:11
*** Guest74752 has quit IRC15:12
*** iovadia has quit IRC15:12
*** beagles_ has joined #openstack-meeting-315:12
*** Youcef has quit IRC15:12
*** beagles_ is now known as b3nt_pin_nickles15:12
armaxamuller: ah…I survived!15:14
*** etoews has quit IRC15:14
amullerGood news!15:14
*** seizadi has quit IRC15:15
*** mestery has joined #openstack-meeting-315:16
*** seizadi has joined #openstack-meeting-315:18
*** etoews has joined #openstack-meeting-315:19
*** seizadi has quit IRC15:20
*** Ark has joined #openstack-meeting-315:21
*** Ark is now known as Guest1052915:22
*** hurgleburgler has joined #openstack-meeting-315:27
*** david-lyle_afk is now known as david-lyle15:28
mesteryaloha neutron drivers!15:29
* mestery steals salv-orlando's trademark entrance music15:29
armaxyello15:30
salv-orlandoALOHA15:30
mesterylol15:30
mesterymarkmcclain: Yo!15:30
mestery#startmeeting neutron-drivers15:30
markmcclainhi15:30
openstackMeeting started Wed Nov 26 15:30:43 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
mesterynice timing markmcclain ;)15:30
mestery#link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers Agenda15:30
mesteryWe have a short agenda15:30
*** Sukhdev has joined #openstack-meeting-315:31
mesteryAnd amotoki cannot make it today.15:31
mestery#topic Sub-Team Charter Review15:31
*** openstack changes topic to "Sub-Team Charter Review (Meeting topic: neutron-drivers)"15:31
mestery#link https://wiki.openstack.org/wiki/NeutronSubteamCharters15:31
mesteryHas anyone looked at these yet?15:31
*** marun has joined #openstack-meeting-315:31
armaxI did, sir15:31
mesteryAny early thoughts armax?15:31
markmcclainI was waiting on the sub-team for sub-teams to organize15:31
mesteryrofl15:32
dougwiglol15:32
armax:)15:32
mesteryI like what carl_baldwin has done for L3 there.15:32
mesteryHe has specific BPs/specs he's tracking for Kilo15:32
mesterydougwig, you also have a clear charter for LBaaS15:32
mesteryAlthough no unicorns dougwig :(15:33
mesteryOnly rainbows15:33
dougwigha15:33
armaxwe’d need to monitor how this page evolves, as it looks the list is potentially not complete yet15:33
mesteryarmax: Yes, agreed.15:33
mesteryMostly just wanted an early look today, and to make sure drivers were looking at it :)15:33
armaxbut I think it makes sense to be explicit upfront about the fact that subteams are not lifelong teams15:33
mestery++15:33
*** xuhanp has quit IRC15:33
mestery#info Continue tracking Sub-Team Charter page for another week15:34
markmcclainI am concerned about adv svcs.. not sure what they're actually setting out to accomplish15:34
mestery#info Ensure people are aware sub-teams are not lifelong teams15:34
armaxone thing that’s not clear15:35
mesteryThat one stood out for me too markmcclain15:35
markmcclainalso the edge vpn… should that be something that starts out in stackforge?15:35
armaxis what we do if as a drivers team does not feel a subteam should exist15:35
mesteryWell, either stackforge or in the new vpnaas repo15:35
armaxor cannot be supported effort-wise by the core team15:35
mesteryarmax: Move it to stackforge?15:36
salv-orlandomarkmcclain: my guess it that the adv svcs charter is a stub at the moment15:36
markmcclainyeah… I still think we need to better scope the barbican interaction since it seems necesarry15:36
armaxright, but that might still need help by the core15:36
*** natarajk has joined #openstack-meeting-315:36
markmcclainsalv-orlando: ok if it is a stub then we should prob ask for clarity15:36
mesteryarmax: Agreed, but maybe we encourage iteration in stackforge while the cores have no time?15:36
armaxwhat if for instance15:36
armaxI want to come up with my own subgroup15:36
armaxbut drivers team feels there’s no scope for it in Kilo at all15:37
salv-orlandomarkmcclain: I don’t know if they want to commit to that… it’s so vague that makes me wonder what the team is there for15:37
armaxthe charter is per-cycle after all15:37
armaxthe subteam can still work indepently and locally15:37
markmcclainright folks can still self organize15:37
mesteryRight, we're not preventing that15:37
armaxbut at one point there would be an interaction point with the core15:37
*** xuhanp has joined #openstack-meeting-315:37
markmcclainbut this is really to say these teams are doing tracked work for Kilo15:38
mestery++15:38
armaxwhat if the core can’t commit to it by Kilo. Do we even have to worry about it?15:38
mesteryThat's the real gist there15:38
mesteryThese teams should be tracking actionable work for Kilo15:38
mesteryOR whatever release we're currently on15:38
salv-orlandoyeah that’s pretty much it for me. I think we aim at tracking sub-teams that do stuff which has to be part of the deliverable of this release cycles15:38
salv-orlandoif other groups of people do stuff more or less related to neutron in stackforge, we don’t have a need to keep track of them.15:38
armaxok, but if the team produces deliverables in stackforge15:39
armaxwhy would we even track it here?15:39
salv-orlandoeven though obviously they can “interact” with neutron core15:39
mesteryRight15:39
mesteryWe're not saying we'll ignore them15:39
mesteryJust that if they are doing work for Kilo we can track it in a sub-team15:39
salv-orlandoit’s not like we tell them “sorry, you’re stackforge I won’t talk to you. Go away!"15:39
*** alexpilotti has joined #openstack-meeting-315:39
mesteryarmax: Makes sense?15:39
salv-orlandomestery: yes, that’s pretty much it in my opinion15:39
armaxok15:39
armaxnot sure what’s the value in that, but ok15:40
armaxfor instance the edge vpn team15:40
salv-orlandoit’s funny no subteam stated an endgoal15:40
salv-orlandojusrt lbaas has “exit criteria"15:41
armaxtheir charter is pretty clear15:41
kevinbentonWhat is the drivers team endgoal?15:41
marunlol15:41
armaxis the core gonna do any anthing about it this cycle?15:41
salv-orlandokill the other teams15:41
mesteryrofl15:41
markmcclainhaha15:41
mesteryThe drivers team can go away when people stop proposing specs for neutron kevinbenton.15:42
mesterySince our goal is to approve specs :)15:42
marunnot really15:43
amullerSo lbaas subteam is done when there's no more bugs and RFEs?15:43
dougwigif we need to be a sub team after v2, i'll ask for another charter.15:43
kevinbentonmestery: so wouldn't the L3 team exist for an also undefined amount of time?15:43
salv-orlandomaybe the rest of the teams can indict the drivers team and ask for its suppression :)15:43
*** xuhanp has quit IRC15:43
markmcclaindougwig: right that's the correct way to do it15:43
mesterysalv-orlando: I'd prefer a revolt personally, there's more bloodshed that way15:43
markmcclainI also think a valid charter is to be dedicated to the ongoing stable maintenance of a feature15:43
mesterykevinbenton: If the L3 team has things to accomplish in "L", then it can re-charter15:44
dougwigotherwise, bugs get folded into whichever team is involved (neutron), and we're not going anywhere.15:44
markmcclainespecially if that sub area requires SME15:44
*** yamamoto has joined #openstack-meeting-315:44
salv-orlandoI think at some point we can consider the L3 team complete… once DVR-related items are complete, BGP is introduced, and it scales to a point that it won’t be a concern in large deployments15:44
kevinbentonmestery: ok15:44
salv-orlandofrankly I expect the L3 team to be done either for Kilo or L15:44
*** thinrichs has joined #openstack-meeting-315:44
mesteryMy guess would be L, not sure BGP lands in Kilo at this point, but maybe15:44
kevinbentonsalv-orlando: l3 is not done until I see ISIS support15:45
markmcclainsalv-orlando: agreed.. I was guessing M15:45
salv-orlandokevinbenton: that is an acronym you can’t use anymore on IRC unfortunately. It’s been hijacked.15:45
salv-orlandoand now you’ve got CIA and NSA on your back15:45
kevinbentonsalv-orlando: that just occurred to me :)15:45
* mestery thinks we're all being watched anyways15:46
kevinbentonIS-IS15:46
dougwigsalv-orlando: it's not like kevinbenton is going to bomb an airport and kill the president.15:46
armaxkevinbenton: try IS-IS15:46
*** jcoufal has joined #openstack-meeting-315:46
mesterydougwig: Now we're in trouble15:46
armaxoh my15:46
dougwigcome on wiretaps.15:46
dougwig:)15:46
* markmcclain awaits knock on his door from three letter agents15:46
armaxI am gonna leave this room15:46
kevinbentonWhat's a letter agent?15:46
salv-orlandomarkmcclain knows that even mentioning agencies puts them on your back ;)15:47
mesteryOK, lets focus again.15:47
mesterySub-Teams: We'll keep waiting for more people to add charters and re-review next week. Sound good?15:47
salv-orlandosounds good to me.15:47
markmcclainmestery: I'm intrigued about Kevin's holiday plans with a now frozen bank account :p15:47
mesterylol15:48
mesteryAs if on queue ...15:48
kevinbentonSo IIUC each sub team justifies its existence at the start of each cycle15:48
salv-orlandomarkmcclain: I think he’s going to cuba.. the easternmost tip15:48
mestery#topic Service Split BP15:48
*** openstack changes topic to "Service Split BP (Meeting topic: neutron-drivers)"15:48
mestery#link https://review.openstack.org/#/c/136835/15:48
mesteryWanted to make sure the drivers are getting in on the fun with this one.15:48
mesteryWe almost had 80 comments for revision one15:48
dougwig84, i thought15:48
mesteryRight dougwig, we did cross 80, apologies :)15:48
dougwigsorry, 8215:48
mesteryI think dougwig has done a good job with most of the technical details here15:49
mesteryBut I wanted to highlight we're now proposing per-service repositories15:49
dougwigthe three biggest hot areas are: governance (which isn't even covered by the spec), whether extensions move before they're refactored, and the notion of making the services auto-install somehow with neutron in the kilo cycle.15:50
mesteryThis will let each services team iterate at their own pace15:50
mesteryThoughts?15:50
salv-orlandomestery: that maes more sense.15:50
marunauto-install?15:50
markmcclainmestery: +115:50
mestery#info For the services split, we will have a per-service git repository, letting teams iterate at their own pace.15:50
dougwigmarun: you install neutron, you get lbaas v1, fwaas, vpnaas automatically, so your upgrade doesn't break any existing deployments.  in mark's email to the TC, it was stated as neutron having a dependency on the services project.15:51
marunIsn't that up to the distros/packagers?15:51
markmcclainbackwards compatibility makes it a bit messy15:51
markmcclainmarun: the master much follow deprecation cycles15:52
markmcclains/much/must/15:52
marunI'm saying it doesn't necessarily matter for distros/packagers.15:52
marunWe don't have the same backwards compatibility requirements as upstream.15:52
markmcclaincorrect the distros can work with their customers to meet their needs15:52
dougwigso can we strike that as a technical issue and just work with the distros on packaging?15:53
marunmaybe not15:53
salv-orlandodougwig: so are the services splitting or cloning? And in the latter case, the “original” ones in neutron will go in the deprecation path?15:53
dougwigsplitting. the goal is to get some code out of neutron.15:54
marunis the idea that neutron would reference the new distributions of the services as explicit dependencies?15:54
mesteryFor LBaaS, the new neutron-lbaas project will also take lbaasv1 with it15:54
mesteryright dougwig ?15:54
dougwigmestery: right15:54
salv-orlandomestery: so when you talk about backward compability we’re talking about it from a deployer perspective, not consumer, is that right?15:54
dougwigmarun: if necessary, yes.  something that makes packaging implicit to the outside world, though i don't like the circular requirements.txt dependency15:55
marundougwig: yeah, that would be messy15:55
mesterysalv-orlando: Yes15:55
marundougwig: at least in the case of the vendor decomposition there's only one explicit dependency15:55
*** ongk has joined #openstack-meeting-315:55
salv-orlandocool thanks. It seems to me we’re having a discussion we should have in gerrit.15:56
markmcclaindougwig: yeah working through how we can make the deps unidirectional15:56
marunsalv-orlando: because chatting via comments is so much better than irc?15:56
mesterysalv-orlando: ++15:56
salv-orlandomarun: it’s just that I think the meeting is over soon :)15:57
salv-orlandodougwig: have you tried to play a bit with the code to see how the spin off for lbaas for instance would work?15:58
dougwigmarkmcclain: right now i've got it specified as a circular dependency with a hacking check in neutron to prevent it being used circularly.  which is barely palatable because i know the circle gets broken in a cycle or two.  but i'd love to hear a better way.15:58
mesteryI am good with a 30 minute meeting today :)15:58
markmcclaindougwig: yeah… I keep thinking if there is a way have a weak dep15:58
markmcclainmestery: ++ to short meeting15:59
dougwigsalv-orlando: i have played with the also git script and experimented with two repos.15:59
dougwigoslo15:59
*** sarob has joined #openstack-meeting-316:00
armaxperhaps we need a third repo16:00
armaxto break the circular deps?16:00
marunoy16:01
marunmake neutron depend on the repos, because it has to16:01
dougwiglike a networking umbrella repo?  i had thought of that, but it won't solve the "pip install -U neutron" case, so to speak.16:01
marunmake the services not depend on neutron and require an explicit install16:01
markmcclainmarun: eventually yes, but we'll have to tackle to short term operator impact16:01
*** thinrichs has quit IRC16:02
marunmarkmcclain: which operator is not going to install neutron?16:02
marunit's only the folks that want to try to install services without neutron that have to do an extra step16:02
maruni.e. not people with an existing install16:02
dougwigthe services repos are spec'ed to include neutron as a library dependency in kilo, so separate service installs aren't in the cards right now.16:03
mesteryYes, for Kilo, lets keep it that way dougwig.16:03
*** mrunge has quit IRC16:04
marundougwig: but doesn't that imply that the services have an explicit dependency on Neutron?16:04
marundougwig: Given the compat requirements the explicit dep would seem more necessary for Neutron, and unless I"m missing something there can only be one.16:04
kevinbentonSo we have a circular dependency issue if we want neutron to auto install services16:04
dougwigthey do right now, since they have to import neutron to reach under the covers.16:04
marundougwig: They can import Neutron without having the explicit dep16:05
dougwigkevinbenton: hence the messiness.  :)16:05
marundougwig: It just requires an explicit install step.16:05
maruni.e. pip install neutron-lbaas neutron16:05
kevinbentonmarun: that's just a temporary hack, right?16:05
kevinbentonBecause that's exactly the opposite of the real dependency16:05
dougwigjust import and pray in kilo?   hmm, that's a possibiility16:06
marunkevinbenton: Sure, for however long we need backwards compat16:06
salv-orlandoI believe that what marun is suggesting is acceptable, but I’m no operator16:06
marunsalv-orlando: I would hope documenting this requirement would be sufficient for any given operator.16:06
mesteryAlso +1 to marun's idea, seems like it would work16:06
dougwigthe only place it really bites you is if you install a service in a way that would process requirements.txt, and have an older neutron, and then you'll import weirdness.  but i don't think that's a real scenario.16:06
marunI like to think they have brains16:06
mesterylol16:06
marundougwig: It will probably happen, but again, docs :)16:07
salv-orlandoI also understand markmcclain’s point. But if I had to choose between a circular dependency and requiring operators to do an additional manual step after pkg upgrade, I’d vote for the manual step16:07
salv-orlandostill, if you have a 3rd option which will give us the best of both worlds, the we’ll go for that16:08
marun(pony!)16:08
kevinbentonNobody reads docs16:08
dougwigi'll go with marun's idea unless someone pulls some magic out of a hat.16:08
marunkevinbenton: true.  it's more a 'get out of jail free' card16:08
marunkevinbenton: 'something went wrong?  did you read the docs?'16:09
kevinbentonYeah16:09
armaxwhat about hte usual RTFM16:09
armax?16:09
maruntrying to avoid channeling linus16:09
kevinbentonThat's what people say when they have bad UX :)16:09
marunbut that would work too16:09
armax:)16:09
dougwiglinus strikes me as more of a PEBKAC kind of guy.16:10
salv-orlandooh you don’t say RTFM in openstack. We simulate respect for others16:10
marunhah16:10
kevinbentonDougwig made a good point though. This will just be a weird corner case16:10
mesterylol16:11
* mestery thinks we've ratholed deep enough16:11
salv-orlandook… can you guys remind me why are we worrying about that if it’s a weird corner cases that can be easily documented and distros don’t really care about it?16:11
mesterysalv-orlando: See rathole comment above16:11
mestery;)16:11
dougwigwe're not, we're just dribbling into IRC.16:12
salv-orlandoindee16:12
armaxeither way we go, people need to be aware that something in Kilo changed16:12
dougwigcontinue rathole in gerrit.  i want to break 100 comments on this rev.16:12
armaxso they need to document themselves of the potential pitfalls16:12
mesteryI think it's safe to assume people can read, now whether they do that is harder to predict16:12
armaxright16:12
mestery"Hey, new shiny thing!" <Throws manual away and starts playhing>16:12
armaxour job should stop at ‘documenting'16:12
salv-orlandodougwig: it’s like you win a teddy bear if you reach 100 comments on a single patchset… you win that if you reach 100 patchsets!16:12
*** Ark has joined #openstack-meeting-316:12
* dougwig writes down his new goal.16:13
*** Ark is now known as Guest863816:13
dougwigi'll just submit PS1 as ruby, and let people review it as python.16:13
* mestery pulls us back out of the hole16:13
*** Guest10529 has quit IRC16:13
mesteryOK, make sure to review dougwig's spec if you haven't.16:13
mesteryGood stuff in there.16:13
mesteryAnd it's important, we need to be moving forward on this next week if we want to make progress before the holidays16:13
*** MarkAtwood has joined #openstack-meeting-316:13
salv-orlandomestery: I think they’ll go back to the manual immediately after upgrade once their neutron server won’t start because it does not find the lb service plugin16:14
mestery#topic Open Discussion16:14
*** openstack changes topic to "Open Discussion (Meeting topic: neutron-drivers)"16:14
mesteryAnything else?16:14
mesterysalv-orlando: If they can find the manual ;)16:14
kevinbentonIhar has made a point on the vendor pl16:14
kevinbentonVendor split*16:14
armaxkevinbenton: I am actually pushing another revision shortly16:14
kevinbentonThat Red Hat will likely not create packages for the vendors16:14
kevinbentonUnless they are partners16:15
armaxihar’s point is well taken, but I think that makes quite a bit of sense16:15
marunUnless a vendor has zero extra dependencies, I'm not sure that's really a problem.16:15
mesteryI'll I'm going to say here is that the only way to make that possible (packages by distros) is if we have a single, shared repo for all the plugins and drivers, not in neutron itself.16:15
dougwigso?  where the packages stop, pypi takes over.16:15
mesteryAnd that presents a whole host of other issues16:15
kevinbentonIt's a problem for our code16:15
marunmestery: The problem of having extra non-Neutron deps is common to pretty much any solution.16:16
kevinbentonBecause we have no other deps16:16
mesterymarun: Ack16:16
armaxwe can always figure out ways to make everyone happy, but all things considered, potential lack of packaging is not the real stopper to adoption of a specific vendor solution IMO16:16
marunmestery: So if we solve some of it, they still have work to do.16:16
maruni.e. install contrail is not our job.16:16
mesterymarun: Exactly16:16
mesteryI agree marun16:16
mesteryFrankly, the plugin/driver is the easy part16:16
marunSo pretty much any vendor has to be able to package and distribute extra deps.16:16
mesteryThe controllers are likely way harder to install16:16
*** zigo has quit IRC16:16
marunEither with a distro's help or otherwise.16:17
kevinbentonMarun we don't now16:17
salv-orlandoI think we already had this discussion about packaging and we reached a consensus that it was the plugin maintainer interest to ensure it was packaged properly?16:17
marunkevinbenton: You don't have software to install?16:17
kevinbentonNo16:17
marunkevinbenton: just hardware?16:17
salv-orlandoI am sure I bored you for about 20 minutes last week with this packaging story16:17
kevinbentonYes16:17
kevinbentonPerhaps we are a corner case16:17
kevinbentonBut there are no extra python libs for big switch16:18
marunkevinbenton: Hmmm... I'm not sure why I assumed bigswitch was primarily a software solution, my bad.16:18
kevinbentonOr code on the openstack nodes16:18
salv-orlandomarun: you’re so 2012!16:18
kevinbentonMarun: we have an optional vswitch16:18
kevinbentonBut it is optional precisely because we had some pushback from installing extra stuff16:19
salv-orlandoanyway, let’s leave the controllers aside, and focus on another comment from the hyper-v team that they’re concerned of being neglected because their plugin has a smaller user base.16:20
*** amuller has quit IRC16:20
kevinbentonOh well, I don't think I need to waste more of this meetings time16:20
salv-orlandowhat should we answer them to reassure they won’t end up being forgotten?16:20
marunI guess offline discussion is suggested then.16:20
kevinbentonSalv-orlando by who?16:20
dougwigwe have ten minutes, unless there's another topic...16:20
marunThat we want to focus our efforts on benefiting as large a part of the community as possible?16:20
natarajkDoes the vendor code decomposition scope include vendor L3 service plugins also ?16:21
mesterydougwig: Now you've jinxed us :(16:21
alexpilottisalv-orlando: it’s not because of the user base size16:21
salv-orlandoah see hear it from alexpilotti. I did not want to offend you saying you’ve got a small user base ;)16:21
mesterynatarajk: Not for stage one, but I defer to armax. Those will be spun into the respective service repositories.16:21
armaxnatarajk: I would think so16:21
alexpilottisalv-orlando: np, and thanks for raising this up :-)16:22
kevinbentonarmax +116:22
natarajkarmax: Thanks. I didn't see any mention of vendor of L3 service plugins in the spec. That's why the question16:22
armaxI am sure there was, I’ll make the extra effort to emphasize16:22
alexpilottisalv-orlando: we definitely agree on getting the drivers out of Neutron16:22
alexpilottiour main concern is that if the drivers will land out of core (e.g. devstack), there will be different perceptions16:23
mesterySo, for devstack, have folks seen this?16:23
mesteryhttps://review.openstack.org/#/c/137054/216:23
kevinbentonalexpilotti: that's why all are being separated16:23
mesteryThat spec proposes pluggable devstack16:23
salv-orlandoalexpilotti: did you mean devstack or stackforge?16:23
mesteryAnd I think devstack will push to get rid of a lot of things upstream with regards to drivers :)16:24
mesteryalexpilotti: Your conversation made me think of that16:24
alexpilottisalv-orlando: stackforge, horrible lapsus, sorry :-)16:24
alexpilottithe docs team already agreed in documenting only fully end to end open source stacks16:24
dougwigalexpilotti: well, they will have different perceptions because there are different realities.  you're trading in-tree code for a healthier core project and more flexibility with your own code.  that's the crux of agreeing to the split.16:24
alexpilottidougwig: the way you put it, it sounds like you guys are kicking us out for Neutron’s benefit16:25
salv-orlandoI think the “stackforge is a terrible place to be” discussion has come often. My answer in short is that it’s as good as any other place to keep your code public, but work is needed at the community level to communicate that if you go to stackforge is not because you’ve been booted out16:25
alexpilottinot caring about what actually happens with the plugins as it’s not your responsability anymore :-)16:25
alexpilottimy question is: since the plugin today is core code, why can’t we still be core?16:26
alexpilottiI mean, teh people writing and maintaining that code are the same16:26
alexpilottiso I don’t get why we should go back to the starting port (aka StackForge purgatory)16:27
kevinbentonalexpilotti: it's consuming community resources16:27
dougwigif we're cold-blooded, that is one of the net advantages.  but i don't think the intent is to "kick out" or to lose the community aspect; merely to change the interface by which that happens.  that's far from not caring.  (i'm not a core, and i am a vendor, btw, so this is just my opinion.)16:27
*** zigo has joined #openstack-meeting-316:27
armaxalexpilotti: core of what?16:27
armaxstackforge is no purgatory16:27
alexpilottiteh plugins are a community asset, of course they consume community resources!16:27
armaxI think people should refrain from making such statements16:28
marunalexpilotti: 'community asset'?16:28
alexpilottiarmax: of cours it is: you have to wait to cycles before asking to be admitted in core “heaven”16:28
mesterycommunit assett?16:28
mesteryWe can't even test most of htem because they require proprietary controllers or HW16:28
mesteryHow are they community assetts?16:28
*** sarob has quit IRC16:28
alexpilottithe plugins are16:28
marunalexpilotti: core heaven is a process-heavy development environment that I wouldn't wish on anyone that didn't absolutely require it16:28
armaxalexpilotti: there will no longer be a core heaven, and let me tell you, today the core is far from being heaven, perhaps hell if you ask me16:28
mesteryarmax: ++16:28
alexpilottithe  underlying technology not16:28
mesterymarun: ++16:28
mesteryAll the effort we've done to try to get people to test their code, run CI systems, all of that takes cycles from cores and other people upstream16:29
mesteryIt's a huge effort16:29
kevinbentonI think an analogy would be the way Linux drivers are a community asset16:29
alexpilottiarmax: sure, nova for example for us is the closest thing to hell we’ve been in16:29
marunalexpilotti: neutron in it's current state is worse than nova16:29
alexpilottimestery: we run our own CI16:29
mesteryalexpilotti: You guys do a good job with that, but others ...16:30
marunalexpilotti: are you saying you find that productive?16:30
alexpilottimarun: trust me: you guys are angels in comparison ;-)16:30
*** k4n0 has quit IRC16:30
marunalexpilotti: I guess our standards differ.16:30
alexpilottimestery: yeah, but why do we have to pay the price for others?16:30
salv-orlandoalexpilotti: but still, we won’t be able to list any driver-specific item in kilo priorities, just like nova16:30
mesteryOK we're at time16:30
mesteryThanks for a productive discussion folks.16:30
mestery#endmeeting16:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:30
openstackMeeting ended Wed Nov 26 16:30:48 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-11-26-15.30.html16:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-11-26-15.30.txt16:30
salv-orlandoadieuuuuu16:30
marunalexpilotti: everyone pays.16:30
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2014/neutron_drivers.2014-11-26-15.30.log.html16:30
alexpilottiall we want is to be independent (so outside of neutron, nova, etc)16:30
dougwigbye16:31
armaxalexpilotti: right16:31
armaxand this effort enables to do that16:31
alexpilottiwhile still publishing our code on a place which can be considered THE openstack code16:31
armaxthis won’t change16:31
*** natarajk has left #openstack-meeting-316:31
alexpilottiit will16:31
kevinbentonalexpilotti: no, there will still be a hyper v folder16:32
alexpilottias stackforge is not THE opensatck code repository16:32
armaxare you saying that it will change?16:32
armaxalexpilotti: that does not matter16:32
armaxif you think it does, then there’s nothing we can say to change your mind, really16:32
alexpilottiin url terms, all I’d like to have is: https://github.com/openstack/hyper-v-drivers16:32
alexpilotti(or whatever the name will be)16:32
kevinbentonalexpilotti: it will just be a much smaller integration layer16:32
marunalexpilotti: Why should neutron have to carry of vendor-specific code that we don't understand and can't maintain?16:32
marunalexpilotti: Makes zero sense.16:32
marunalexpilotti: The proposed separation of concerns is for everyone's benefit.16:33
armaxalexpilotti: that url you’re so fond of16:33
alexpilottimarun: to be clear, I don’t want this code to remain in Neutron16:33
kevinbentonalexpilotti: you can't have something in the OpenStack name space16:33
*** jcoufal has quit IRC16:33
*** ongk has left #openstack-meeting-316:33
armaxhas greater implications16:33
armaxand you’ll have even more oversight than the one you already have16:33
alexpilottikevinbenton: well, now I have it (as part of Neutron)16:33
kevinbentonalexpilotti: there are a bunch of infra rules governing how those are created16:33
marunalexpilotti: I don't understand why you expect OpenStack to continue blessing code we don't understand and can't maintain.16:34
kevinbentonalexpilotti: you will still have a folder in the neutron code16:34
marunalexpilotti: Providing this separation makes the responsibilities clear to both maintainers and end users.16:34
armaxwith the decomposition there will be a part of the hyper-v code that will still be part of neutron16:34
alexpilottimarun: because we (the driver mainteners) are part of the OpenStack community as much as you guys are16:34
armaxthe part that neutron does not need to worry about can be anywhere16:34
armaxeven in https://github.com/alexpillotti/hyper-v-drivers16:35
armaxno-one should care16:35
armaxbut you16:35
alexpilottithere should be a new project for a driver with a new set of cores16:35
armaxor anyone who works with you16:35
marunalexpilotti: You are free to do that.16:35
armaxand you can do whatever you want with this repo16:35
armaxpush with or without control16:35
marunalexpilotti: Why you would want the openstack process to slow you down is beyond me.16:35
alexpilottiarmax: you don’t really get it16:35
kevinbentonalexpilotti: hyper v specific code is not relevant to the community16:35
marunalexpilotti: Do you really not like getting things done?16:35
armaxalexpilotti: I don’t?16:35
armaxok16:35
armaxso I am outta here16:35
*** sarob has joined #openstack-meeting-316:35
alexpilottiuser xyz will never trust code on https://github.com/hohndoe/hyper-v-drivers16:36
marunalexpilotti: They do already16:36
alexpilottinot really16:36
kevinbentonalexpilotti: they won't know where it comes from16:36
marunalexpilotti: there are tons of dependencies that are not openstack-namespaced.16:36
marunalexpilotti: So, what makes your code special that they won't trust it?16:36
alexpilottiwell, those dependies become “trusted” in the moment in which the requirements.txt lists them16:36
alexpilottieven if it’s obviously outside of the project’s scope16:37
marunalexpilotti: like talking to a wall16:37
marunalexpilotti: Sorry, but I think you're confusing upstream distribution with how end-users actually consume the code.16:37
alexpilottiI’ll take it like this: you kick the drivers pout from the “core” space :-)16:37
marunMostly it's through distros like redhat16:37
marun(who I happen to work for)16:38
armaxthat’s not what we’re aiming for16:38
alexpilottithose “distros” use our code16:38
armaxwe’re taking out what makes no sense to be in the core16:38
alexpilottithey’re legal teams have huge issues in accepting anything ouside of core, for example16:38
armaxthat’s nonsense16:38
marunalexpilotti: you want to prove that point?16:38
alexpilottiwell speak w them16:38
kevinbentonalexpilotti: neutron depends on tons of packages not in the core16:39
armaxthere’s exactly no difference from a legal standpoint16:39
alexpilottimarun: I can ask some of them to come out with their opinion16:39
armaxso long as the licensing terms are kept equal16:39
alexpilottiI can’t make names now of course16:39
marunalexpilotti: we can make _zero_ guarantees of the quality of code that happens to be in tree16:39
marunalexpilotti: that's why it doesn't belong16:39
alexpilottimarun: that’s why it has to go in another project, where OTHER people guarantee on the quality16:39
alexpilottithose people being the driver mainteners16:40
alexpilottide facto you trusted us until now16:40
kevinbentonalexpilotti: it will, but that doesn't need to be in openstack16:40
alexpilottikevinbenton: that’s where we disagree16:40
alexpilottikevinbenton: we’ve been part of openstack until now16:40
alexpilottiyou trusted our code16:40
armaxalexpilotti: and you’re continue to be16:40
salv-orlandoalexpilotti: by that analogy these “distros” will not install any software that does not come in the OS DVD? Sounds a bit extreme, but I’m sure there a lot of strange realities out there16:41
alexpilottiarmax: no16:41
armaxnow, we clearly failed to convince you16:41
alexpilottiarmax: as we won’t be “core”16:41
armaxso I see no point to continue this conversation in this venue16:41
alexpilottiI guess we are in a loop :-)16:41
kevinbentonalexpilotti: there will still be a hyper v integration point in neutron!16:41
marunalexpilotti: we've ignored the fact that we have no basis for trusting your code16:41
kevinbentonalexpilotti: to indicate that there is a level of testing16:41
marunalexpilotti: that's not the same as 'trusted'16:41
salv-orlandoalexpilotti: since nobody will be “core” these distros of yours will just have to stop using neutron then ;)16:42
marunalexpilotti: but if you want to presume, that's you right16:42
dougwigalexpilotti: marketing of core code aside, realistically speaking, we have a constrained problem that is failing.  and it's been ongoing.  neutron has insufficient resources to maintain all this vendor code.  you can't increase neutron resources quickly.  how would you suggest breaking the constaints and solving the problem?  and "just let me stay in core"16:42
dougwigisn't breaking any constraint at all; it's the status quo that isn't working.16:42
alexpilottidougwig: nobody is disagreeing with the solution to the Neutron problem: aka the fact that drivers need to go out16:42
alexpilottiif you look at the ML, I’m fighting with Nova since 2 years to have the same result there16:43
*** scheuran has quit IRC16:43
dougwigso what are you asking for?16:43
alexpilottigeez16:43
* mestery is really confused16:43
alexpilotti1) get the drivers out 2) keep the drivers in core16:43
armaxalexpilotti: there’s no need to use inflamatory language here by the way16:43
armaxalexpilotti: calm down16:43
armaxplease16:43
dougwigalexpilotti: i read that as contradictory.  can you explain?16:43
kevinbentonalexpilotti: so maybe for comparison, how do you guys vet the netaddr library16:44
alexpilottidougwig: let me rewind. Please let me know if you want to move thsi to another channel16:44
armaxI might be tempted to say, take it to review16:44
armaxbut I really don’t see why it would be any different16:44
marunkevinbenton: if I read him right, the fact that openstack explicity depends on it is what qualifies it16:44
marunkevinbenton: the fact that we gate on it16:44
alexpilottidriver sub-teams are de-facto are maintaining their own code16:45
armaxit seems like fundamentally we have been unable to express exactly what the intentions are16:45
kevinbentonmarun: ack16:45
alexpilottiuntil now neutron/nova/etc cores blindly trusted the code16:45
alexpilottiwe provide16:45
marunkevinbenton: the fact that we don't gate or otherwise test any part of the 'trusted' vendor stuff ourselves - we have to trust 3rd party ci - doesn't appear to be figuring into his thinking16:45
alexpilottiexcept for the usual “add a unit test here and there“16:45
alexpilottiwe have a CI, which is defending our drivers against regressions in neutron/nova/etc16:46
alexpilottiand at the same time making sure that new code does not break anything16:46
alexpilottibut the first part is the mnost important one16:47
alexpilotti(for driver devs)16:47
alexpilottithe day in which we’ll be out, without being in a TRUSTED localtion16:47
alexpilottiwe’ll lose the ability to gate Neutron/nova/etc agains regressions16:47
marunno, you won't16:47
dougwigand your stub in the neutron core isn't trusted?16:47
marunso long as your driver stub is in the tree, 3rd party ci will remain in force16:48
alexpilottidougwig: stub?16:48
marunthat's the precondition for its inclusion16:48
kevinbentonalexpilotti: you will still have CI16:48
dougwigevery plugin/driver will have a stub in neutron core that calls out to the real code.16:48
dougwigthat's the in-tree hook and review point.16:48
alexpilottikevinbenton: a driver CI in Neutron?16:48
kevinbentonalexpilotti: the integration point I mentioned earlier16:48
kevinbentonalexpilotti: yes, anyone with an integration point will need to tesy16:49
kevinbentonTest* and report results16:49
kevinbentonJust like now16:49
marunalexpilotti: The only thing that's changing is where the code lives that currently implements a given plugin/driver16:49
marunalexpilotti: some remains in tree, some goes out.  same 3rd party ci requirements.  run tempest against configured integration point, including configured backend, and return a result16:50
alexpilottikevinbenton: so if Neutron will contain a requirement, configuration or whatvere saying that the “official” place where driver xyz lives is https://… I’m good16:50
marunalexpilotti: it will16:50
dougwigit will16:50
marunalexpilotti: that's in the spec16:50
armaxalexpilotti: dude, read the spec :)16:51
kevinbentonalexpilotti: yes, the requirements.txt in the spec16:51
alexpilottimarun armax: I must have missed it, I read (and reviewed) the specs :-)16:51
kevinbentonalexpilotti: each plugin folder will have one16:51
armaxalexpilotti: apparently not thoroughly enough16:51
marunalexpilotti: Each plugin/driver will have a requirements.txt that points to the external dependency.16:51
*** emagana has joined #openstack-meeting-316:51
kevinbentonalexpilotti: specifies the python library required to operate16:51
dougwighe said he's good, let's all go sing around the campfire now.16:52
marunalexpilotti: It won't allow automatic installation, but it will allow for discovery via other tools and for packaging.16:52
alexpilottiarmax: sorry for missing this. This improves the scenario16:52
*** belmoreira has quit IRC16:52
kevinbentondougwig: smoke inhalation leads to increased risk of lung cancer16:52
marunkumbaya!16:52
dougwiggotta die sometime.16:52
dougwigok, we only a few minutes before this becomes someone else's meeting channel.16:53
kevinbentonOk16:53
dougwiggood discussion, thanks alexpilotti16:53
alexpilottiit’s still a very faint ombelical cord between core and the orphaned drivers16:53
kevinbentonBye bye folks16:53
alexpilottibut better than nothing :-)16:53
alexpilottithanks folks!16:53
*** eghobo has joined #openstack-meeting-316:54
salv-orlandoI have to admin that I’m struggling to follow this discussion, but I think that 1) being neutron core means nothing. in or out of tree all the plugin will be treated in the same way; 2) the assumption that to be core you’ve got to be in the same repo is nonsense, and I hope we all understand that, and finally 3) packaging wise nothing should change. Plugins will be installed in the same way, with16:54
salv-orlandothe difference that they will pull some extra dependencies, which will be packaged and distributed by repos in the same way.16:54
dougwigsalv-orlando: it was resolved.  :)16:55
salv-orlandoIt seems to me that the argument if that the code doesn’t come from git.openstack.org/openstack then it’s not trusted16:55
salv-orlandodougwig: good to know16:55
salv-orlandoI type slowly today16:55
marunFunny to think that whole thing was about needing an authoritative link to the external dependency to be in the neutron tree.16:56
marunwhich we had already decided was necessary16:57
*** s3wong has joined #openstack-meeting-316:57
alexpilottisalv-orlando: yes, that was the main point16:57
alexpilottisalv-orlando: but if we have code in  git.openstack.org/openstack (your new stubs) pointing to the external code16:58
alexpilottisalv-orlando: this gives a kind of indirect official recognition16:59
alexpilottiwe still have to solve the legal issues for the distros, but that’s a separate issue16:59
dougwigthis is someone else's channel now...17:00
*** pballand has joined #openstack-meeting-317:00
alexpilottidougwig: sorry about that, I didn’t see any start meeting message yet17:01
*** vishwana_ has joined #openstack-meeting-317:01
dougwigit's almost turkey day, so it might be canceled.  but our slot is well over.  :)17:01
dougwigi knew it was open until 1017:01
marunalexpilotti: What legal issues would the distros have to worry about?17:01
*** SridharRamaswamy has joined #openstack-meeting-317:01
*** vishwana_ is now known as vishwanathj_17:01
*** vishwanathj_ has quit IRC17:02
*** vishwana_ has joined #openstack-meeting-317:02
alexpilottimarun dougwig: shouldn’t we move the converstaion to #openstack-neutron ?17:02
marunsure17:02
*** vishwana_ is now known as vishwanathj_17:02
*** hareeshp has joined #openstack-meeting-317:03
*** eghobo has quit IRC17:04
*** evgenyf has quit IRC17:05
*** ChuckC_ has quit IRC17:05
*** ChuckC has joined #openstack-meeting-317:06
*** MaxV has quit IRC17:07
*** eghobo has joined #openstack-meeting-317:08
*** baoli has quit IRC17:08
*** eghobo has quit IRC17:09
*** thinrichs has joined #openstack-meeting-317:10
*** yamamoto has quit IRC17:13
*** b3nt_pin_nickles is now known as b3nt_pin17:14
*** Swami has joined #openstack-meeting-317:18
*** dconde has joined #openstack-meeting-317:18
*** Longgeek has quit IRC17:24
*** ttrifonov is now known as zz_ttrifonov17:26
*** Sukhdev has quit IRC17:34
*** matrohon has quit IRC17:35
*** thinrichs has left #openstack-meeting-317:37
*** seizadi has joined #openstack-meeting-317:39
*** baoli has joined #openstack-meeting-317:40
*** vishwanathj_ has quit IRC17:45
*** asahlin is now known as asahlin_afk17:50
*** pballand has quit IRC18:00
*** pballand has joined #openstack-meeting-318:02
*** peristeri has quit IRC18:04
*** safchain has quit IRC18:04
*** simon-AS5591 has quit IRC18:05
*** peristeri has joined #openstack-meeting-318:08
*** igordcard has joined #openstack-meeting-318:11
*** igordcard has quit IRC18:12
*** clu_ has joined #openstack-meeting-318:12
*** igordcard has joined #openstack-meeting-318:12
*** baoli has quit IRC18:15
*** peristeri has quit IRC18:21
*** badveli has joined #openstack-meeting-318:22
*** emagana has quit IRC18:23
*** emagana has joined #openstack-meeting-318:23
*** peristeri has joined #openstack-meeting-318:24
*** etoews has quit IRC18:26
*** emagana has quit IRC18:28
*** SridharRamaswamy has quit IRC18:29
*** SridarK_ has joined #openstack-meeting-318:29
*** etoews has joined #openstack-meeting-318:31
SridarK_Hi18:32
*** bobmel has joined #openstack-meeting-318:32
SumitNaiksatamSridarK_: hi18:32
SridarK_SumitNaiksatam: hi18:32
SumitNaiksatambadveli: bobmel: hi18:32
bobmelHi, lurking in...18:32
badveliyes, sumit hello18:32
badvelihello sridark18:33
SridarK_badveli: hi18:33
SumitNaiksatambobmel: doing lurking duties for pcm :-P18:33
*** vishwana_ has joined #openstack-meeting-318:33
SumitNaiksatamvishwana_: hi18:33
SumitNaiksatamlets get started18:33
vishwana_hi Sumit18:33
SumitNaiksatam#startmeeting Networking FWaaS18:33
vishwana_hi all18:33
openstackMeeting started Wed Nov 26 18:33:46 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:33
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:33
bobmelSumitNaiksatam: :-)18:33
openstackThe meeting name has been set to 'networking_fwaas'18:33
*** wuhg has quit IRC18:33
SridarK_vishwana_: hi18:33
vishwana_SridarK_: Hi18:34
SumitNaiksatam#announce SPD: Monday 12-8-2014 SAD: Monday 12-15-201418:34
SumitNaiksatamjust retierating18:34
SumitNaiksatam*reiterating18:34
*** emagana has joined #openstack-meeting-318:34
SridarK_SumitNaiksatam: yes the pressure :-(18:35
SumitNaiksatamany other announcements anyone wants to share?18:35
SumitNaiksatamok moving on18:36
SumitNaiksatam#topic Bugs18:36
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:36
Swamihi18:36
SridarK_Swami: hi18:36
badvelihello swami18:36
SridarK_#link https://bugs.launchpad.net/openstack-manuals/+bug/134698618:36
SumitNaiksatamthankfully seems like nothing critical/high has showed up18:36
*** etoews has quit IRC18:36
SridarK_oops sorry18:36
SumitNaiksatamSwami: hi, thanks for joining18:37
SridarK_SumitNaiksatam: yes nothing new18:37
SumitNaiksatamSwami: we will get to your email on E-W in just a bit18:37
SumitNaiksatamSridarK_: ok cool18:37
SumitNaiksatamwe are still delinquent on: https://review.openstack.org/#/c/104132/18:37
SumitNaiksatamlets review this at the earliest18:37
SwamiSumitNaiksatam: no worries18:38
SridarK_SumitNaiksatam: yes the client one will do that18:38
SumitNaiksatamSridarK_: thanks18:38
SumitNaiksatambadveli: anything else on your radar on the bugs front?18:39
badveliNothing as i could see18:39
*** dconde has quit IRC18:39
SumitNaiksatambadveli: okay, and you are still tracking the discussion around: https://bugs.launchpad.net/neutron/+bug/1386543 and https://bugs.launchpad.net/neutron/+bug/1335375, right?18:40
badveliyes18:40
SumitNaiksatambadveli: okay18:40
SumitNaiksatam#topic Docs18:40
*** openstack changes topic to "Docs (Meeting topic: Networking FWaaS)"18:40
SumitNaiksatamSridarK_: go ahead18:40
SridarK_#link https://bugs.launchpad.net/openstack-manuals/+bug/134698618:41
SumitNaiksatami noticed your post, thanks!18:41
*** LouisF has joined #openstack-meeting-318:41
SumitNaiksatamjust in the nick of time ;-P18:41
SridarK_i think there is one section there - can one post a review for just our section ?18:41
SridarK_SumitNaiksatam: :-) life seems to be "nick of time" all the time :-)18:42
SumitNaiksatamSridarK_: :-)18:42
SumitNaiksatamSridarK_: i think that should be good, perhaps we can send an email to ann gentle to check with her as to what is the process?18:42
SridarK_SumitNaiksatam: ok will do18:42
SumitNaiksatamSridarK_: great, thanks18:42
SridarK_the other one:18:43
SridarK_#link https://bugs.launchpad.net/openstack-manuals/+bug/137367418:43
SridarK_is fixed but someone already18:43
SumitNaiksatamsweet!18:43
*** ivar-lazzaro has joined #openstack-meeting-318:43
SumitNaiksatamdocumentation seems to be okay on that18:44
SumitNaiksatamit would be good for us to be in the loop on these things18:44
SridarK_SumitNaiksatam: yes it was a quick clarification18:44
SridarK_SumitNaiksatam: yes - it seems the only way is to poll for these18:44
SumitNaiksatamSridarK_: yeah :-(18:45
SumitNaiksatamSwami: so on the DVR related documentation, your suggestion is that we wait and watch?18:45
Swamihi18:46
SwamiYes, we will wait till they have the networking guide and we can provide the feedback there to add the services that are supported and how it is supported.18:46
SumitNaiksatamSwami: ok cool18:46
SwamiI am working with Edgar, Matt Kassawara and Elke Vorghies18:47
SumitNaiksatamSwami: is there any meeting that we should be attending?18:47
SumitNaiksatamSwami: i recall references during the last neutron meeting18:47
SwamiThere is a meeting on Friday's from 9.00a.m to 10.a.m.18:47
SwamiAt this time, I will take care, and if needed I will let you know.18:47
SumitNaiksatamSwami: woudl appreciate if you get SridarK_ and me plugged into that meeting18:47
SwamiOk, it is a google hangout meeting18:48
SumitNaiksatamSwami: okay thanks18:48
SwamiI will send you the link.18:48
SridarK_Swami: thanks18:48
SumitNaiksatamSwami: great! but hangout is wierd for this kind of a thing!18:48
SumitNaiksatamSwami: thanks Swami for that input18:48
SumitNaiksatamanything else on docs?18:49
Swamithat's what they do right now18:49
SumitNaiksatamSwami: okay18:49
SumitNaiksatammoving on18:49
SumitNaiksatam#topic FWaaS team mission and charter18:50
*** openstack changes topic to "FWaaS team mission and charter (Meeting topic: Networking FWaaS)"18:50
SumitNaiksatamhttps://wiki.openstack.org/wiki/NeutronSubteamCharters#FWaaS_Team18:51
SumitNaiksatamwe discussed this over emails18:51
SumitNaiksatambringing it up here in case anyone missed it18:51
SumitNaiksatamcurrently this does not mention the DVR E-W18:51
SwamiI have mentioned in the DVR charter.18:52
SumitNaiksatamwe also need to append to the specs list once we post those18:52
SumitNaiksatamSwami: great, nice to have cross team reinforcement18:52
SumitNaiksatamanything more to discuss here?18:53
SumitNaiksatamwe will touch on the topic of services’ split in a bit18:53
SumitNaiksatamok next topic18:53
SumitNaiksatam#topic Kilo blueprints18:53
*** openstack changes topic to "Kilo blueprints (Meeting topic: Networking FWaaS)"18:53
SumitNaiksatamrelated to our charter18:54
SumitNaiksatamService groups and objects: #link https://review.openstack.org/#/c/13159618:54
SumitNaiksatambadveli: thanks for the updates18:54
badveli     thanks sumit18:54
SumitNaiksatambadveli: sorry i havent had a chance to get back to it18:54
SumitNaiksatamis glebo here?18:54
badvelino problem, thanks18:54
badvelilooks like not here18:55
badvelithanks giving18:55
badveliweek18:55
SumitNaiksatambadveli: i understand, i did expect a light attendance today18:55
*** SridharRamaswamy has joined #openstack-meeting-318:56
SumitNaiksatami wanted to check if he got any response to the emails he had sent to mestery or markmcclain regarding the service groups18:56
badvelido we need any inputs from him?18:56
SridarK_badveli: i will go thru once more and put a +118:56
SumitNaiksatami did not see a response, but just checking18:56
badvelithanks sridark, on that front, did not receive anything18:56
SumitNaiksatamSridarK_: thanks, i need to read through again as well18:56
*** peristeri has quit IRC18:56
SumitNaiksatamSridarK_: any update on the router/port based insertion?18:57
*** pballand has quit IRC18:57
SridarK_SumitNaiksatam: will put this together real soon18:57
SumitNaiksatamSridarK_: okay thanks18:58
SridarK_on router_id - we keep this optional18:58
SumitNaiksatamSridarK_: did we get any response from arvind, brian or glebo on the use cases?18:58
SridarK_SumitNaiksatam: no18:58
SridarK_SumitNaiksatam: let me send a reminder18:59
*** yamahata has quit IRC18:59
*** pballand has joined #openstack-meeting-318:59
SumitNaiksatamSridarK_: okay18:59
SridarK_SumitNaiksatam: based on what we have in our various discussions - i think ports seems more palatable18:59
SumitNaiksatamSridarK_: okay, what does the rest of the team think about this?19:00
SridarK_SumitNaiksatam: the other thing is that this will probab need to go as an attribute of the firewall extension19:00
SumitNaiksatamSridarK_: okay19:00
badvelisridark, does it seem odd to ask the user to give the port19:00
SridarK_SumitNaiksatam: given that extensions are being clamped down19:00
badveli may be we are asking more from user19:00
SridarK_badveli: the thought was that the port is a representation of the subnet "behind" it19:01
SridarK_badveli: and we are add a fw for that subnet19:01
SridarK_badveli: did u have something else in mind ?19:01
*** reed has quit IRC19:02
badveli currently i do not have much, i need to think more19:02
*** etoews has joined #openstack-meeting-319:02
SridarK_badveli: ok - do send an email19:03
badveli i am not sure if the customers really would like anything like this19:03
SridarK_badveli: we need to go away from the all routers all ports model19:03
badveli  thanks sridark, will let you know19:03
badveli yes that would be ideal19:04
SridarK_badveli: based on the feedback from the summit19:04
badveli  sridark, my only thaught was when this happens would be a undo the one that we had done19:04
*** pballand has quit IRC19:04
SridarK_badveli: if we want to fw a particular subnet for ex engineering19:04
badveli  from the configuration19:05
SridarK_badveli: router port provides a good abstraction19:05
badveli19:05
SridarK_badveli: sorry don't understand19:06
*** pballand has joined #openstack-meeting-319:06
SumitNaiksatamSridarK_: we had discussed one option of having router_id and router_ports, both as optional attributes19:06
badveli sridark ideally we do not want to tie up to ports / routers19:06
*** pballand has quit IRC19:07
badveli sumit, so this will be optional parameters19:07
SridarK_SumitNaiksatam: yes by specifying the router-id and the ports associated19:07
SridarK_SumitNaiksatam: perhaps a subset or all19:07
SumitNaiksatambadveli: its an option to have these as optional parameters :-)19:08
SumitNaiksatamSridarK_: okay19:08
SumitNaiksatamokay so lets wait for SridarK_’s spec19:08
*** pballand has joined #openstack-meeting-319:08
SridarK_SumitNaiksatam: :-) yes all are optional19:08
*** pballand has quit IRC19:08
badveligood one19:08
SridarK_SumitNaiksatam: but what is ur thought on attribute to firewall extension19:09
SridarK_SumitNaiksatam: i guess that would be okay ?19:09
SumitNaiksatamSridarK_: you mean an extension to the firewall resource, or add an attribute to the current firewall resource?19:10
SridarK_SumitNaiksatam: attribute to the firewall resource19:10
*** pballand has joined #openstack-meeting-319:10
SumitNaiksatamSridarK_: perhaps that might be the more palatable option19:10
SridarK_SumitNaiksatam: the extension to firewall resource may have some acceptance issues19:10
*** pballand has quit IRC19:11
SumitNaiksatamSridarK_: the attribute extension mechanism is more flexible in that it does not pollute the base model, but it has its downside19:11
SumitNaiksatamSridarK_: yeah19:11
SridarK_SumitNaiksatam: perhaps we can put that as an Alternative19:11
*** briancurtin has joined #openstack-meeting-319:11
*** etoews has quit IRC19:11
SumitNaiksatamSridarK_: perfect19:11
SumitNaiksatami would also like to hear the opinion of the rest of the team on this19:12
SridarK_SumitNaiksatam: ok thx19:12
SumitNaiksatamso i think looking at the spec people can provide an informed opinion19:12
SumitNaiksatamok moving on19:12
*** pballand has joined #openstack-meeting-319:12
SumitNaiksatamwe should also be discussing pcm’s patch of the L3 agent refactor19:12
*** etoews has joined #openstack-meeting-319:13
SumitNaiksatam#link https://review.openstack.org/#/c/135392/19:13
*** pballand has quit IRC19:13
SumitNaiksatami believe pcm is on vacation, we can probably have this discussion in this meeting if he is around in the next week19:13
SridarK_SumitNaiksatam: yes pcm is out19:14
SumitNaiksatamSridarK_: ok thanks19:14
SumitNaiksatam#topic FWaaS for E-W traffic scenario with DVR19:14
*** openstack changes topic to "FWaaS for E-W traffic scenario with DVR (Meeting topic: Networking FWaaS)"19:14
*** pballand has joined #openstack-meeting-319:15
SumitNaiksatamSwami just sent some detailed ideas, which i have shared with the rest of the team19:15
Swami#link https://docs.google.com/document/d/11Gp62Yfyi1WH6yM6E_308OB4CC9A6xhxKZJ8B5jOwLc/edit19:15
SumitNaiksatamperhaps we can take a quick min to peruse the diagrams19:15
SumitNaiksatamSwami: thanks!19:15
*** pballand has quit IRC19:16
SwamiJust to give a brief summary of the two options that we discussed in Paris.19:16
*** banix has joined #openstack-meeting-319:16
badveli thanks swami, will take a look19:16
SwamiOption 1: is to have a bump in the wire scenario. To add a bridge in between the br-int and br-tun and track all the traffic incoming and outgoing. Apply the rules there.19:16
SwamiOption 2: Instead of applying firewall rules in multiple places for East-West and north south, let us apply it in the "qr" namespace.19:17
*** pballand has joined #openstack-meeting-319:17
SwamiBut when the return traffic hits the br-int, if possible we can force the traffic to get into the router, like a loopback interface and apply the rules there. I am not sure if it is viable and has any issues. But it has to be investigated from the flow rules and from the routers perspective.19:18
*** pballand has quit IRC19:18
SumitNaiksatamSwami: does applying in the “qr” namespace introduce a single choke point?19:18
*** briancurtin has left #openstack-meeting-319:19
SumitNaiksatamSwami: btw, thanks for the summary (was about to ask)!19:19
SwamiIt will not be a single choke point, because you are also applying all the compute nodes. But it will be single choke point for that particular host.19:19
*** pballand has joined #openstack-meeting-319:20
*** SridharRamaswamy has quit IRC19:20
*** pballand has quit IRC19:20
SumitNaiksatamSwami: So the point is that the “qr” namespace itself is distributed since it manifests on all the hosts?19:20
SwamiYes.19:20
badveli  swami: adding a bridge19:21
Swamibadveli: yes19:21
badveli add forcing the traffic towards it19:21
SridarK_Swami: we will do the "return traffic thru qr" if we have fw configured ?19:21
badveli how do we do that?19:22
badveli19:22
Swamiadding a bridge will be similar to the security groups where you apply all the rules in a bridge and then attach it with the veth pairs.19:22
*** pballand has joined #openstack-meeting-319:22
SumitNaiksatamSwami: in that case, i believe the advantage with the second method is that from a fwaas perspective we only have to deal with the “qr” namespace, always (regardless of E-W or N-S traffic)?19:22
badveli thanks swami19:22
SwamiSridarK_: Yes, if firewall is configured for the tenant we force the traffic to send it back to the "qr" and so all your rules will be applied in a single place.19:22
*** pballand has quit IRC19:23
*** reed has joined #openstack-meeting-319:23
SumitNaiksatamSwami: okay i think you answered my question as well with that response19:23
SridarK_Swami: ok that way we will take  a sub-optimal path only then19:23
SridarK_Swami: defn looks like a viable option but need to think some more19:24
SumitNaiksatamgood discussion19:24
SwamiYes we don't need to decide today. But give it a thought.19:24
*** pballand has joined #openstack-meeting-319:24
SumitNaiksatamSwami: thanks for the timely interjection with this proposal :-)19:24
SwamiI have also asked "Vivek" to check on the flow rules and any impact for option 2.19:24
SwamiWhichever option is viable and riskless we can go on that direction.19:25
SumitNaiksatamlets circle back on the email thread, and have a more definitive discussion in the next meeting19:25
SumitNaiksatamSwami: thanks19:25
SumitNaiksatam5 mins left19:25
SwamiSorry I was supposed to send you out this picture after the paris trip, but I was on Jet lag for a week.19:25
badveliyes, thanks sumit19:25
SumitNaiksatamSwami: np19:25
SridarK_Swami: thanks19:25
SumitNaiksatam#topic Vendor drivers19:25
*** openstack changes topic to "Vendor drivers (Meeting topic: Networking FWaaS)"19:25
*** dboik has quit IRC19:25
SumitNaiksatamvishwana_: you posted your spec, right?19:25
SumitNaiksatamlink?19:26
*** MaxV has joined #openstack-meeting-319:26
vishwana_yes, I did, thanks to you and SridarK for initial review and comments19:26
SumitNaiksatamvishwana_: np, just procedural nits19:26
vishwana_https://review.openstack.org/#/c/136953/19:27
vishwana_I am yet to address your review comments19:27
SumitNaiksatamvishwana_: thanks for the link19:27
*** seizadi has quit IRC19:27
vishwana_What is the Ipv6 impact requirement?19:27
SumitNaiksatamany other vendor related bps posted or in the pipeline?19:27
SridarK_SumitNaiksatam: #link https://review.openstack.org/#/c/129836/19:27
SumitNaiksatamvishwana_: i am not completely sure on this19:27
SumitNaiksatamvishwana_: however there was a thread in the -dev ML on this19:28
SumitNaiksatamvishwana_: perhaps you can post your question there19:28
vishwana_Any guidance on how to approach that would be valuable19:28
vishwana_SumitNaiksatam: Thanks19:28
SumitNaiksatamvishwana_: i believe in your case there should not be any IPv6 impact since this is vendor specific19:28
*** banix has quit IRC19:28
vishwana_I see19:28
SumitNaiksatamSridarK_: thanks, did not notice that one19:28
SumitNaiksatamvishwana_: again, my comment was more procedural ;-)19:29
SridarK_SumitNaiksatam: no worries - it has extension written all over it :-)19:29
SumitNaiksatamSridarK_: :-)19:29
SumitNaiksatam#topic Open Discussion19:29
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:29
vishwana_SumitNaiksatam :understaood19:29
SumitNaiksatamwe have one minute19:29
SumitNaiksatamone quick one - #link https://review.openstack.org/#/c/136835/19:29
SumitNaiksatamservices’ split ^^^19:29
SumitNaiksatamthis is shaping up in a different way from what we discussed in the paris summit19:30
SridarK_SumitNaiksatam: +1 :-(19:30
SumitNaiksatamat any rate i have volunteered to help out on the fwaas side of things19:30
SridarK_SumitNaiksatam: i can also help19:30
SumitNaiksatamothers should read this spec carefully and express their opinion as well19:30
SumitNaiksatamSridarK_: great19:30
SumitNaiksatamok, lets call it a wrap19:30
SumitNaiksatamhappy thanksgiving to all!19:30
SridarK_Ok bye all19:30
Swamiwill take a look at it.19:31
SumitNaiksatambye19:31
vishwana_bye19:31
badveli  bye all19:31
SridarK_Happy Thanks giving19:31
Swamibye, happy thanksgiving19:31
SumitNaiksatam#endmeeting19:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:31
openstackMeeting ended Wed Nov 26 19:31:17 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-26-18.33.html19:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-11-26-18.33.txt19:31
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-11-26-18.33.log.html19:31
*** Swami has quit IRC19:31
*** emagana has quit IRC19:31
*** vishwana_ has quit IRC19:32
*** emagana has joined #openstack-meeting-319:32
*** peristeri has joined #openstack-meeting-319:32
*** LouisF has quit IRC19:36
*** emagana has quit IRC19:36
*** banix has joined #openstack-meeting-319:36
*** dboik has joined #openstack-meeting-319:40
*** emagana has joined #openstack-meeting-319:42
*** shwetaap1 has quit IRC19:43
*** SridarK_ has quit IRC19:43
*** simon-AS559 has joined #openstack-meeting-319:44
*** Sukhdev has joined #openstack-meeting-319:46
*** peristeri has quit IRC19:46
*** simon-AS5591 has joined #openstack-meeting-319:46
*** peristeri has joined #openstack-meeting-319:47
*** simon-AS559 has quit IRC19:48
*** emagana has quit IRC19:59
*** emagana has joined #openstack-meeting-319:59
*** emagana has quit IRC20:03
*** SridharRamaswamy has joined #openstack-meeting-320:04
*** b3nt_pin has quit IRC20:05
*** beagles has joined #openstack-meeting-320:15
*** mvineet has joined #openstack-meeting-320:16
*** mvineet is now known as vineet20:16
*** vineet is now known as vineetmenon_20:17
*** pballand has quit IRC20:26
*** sarob has quit IRC20:28
*** obondarev has quit IRC20:28
*** matrohon has joined #openstack-meeting-320:29
*** sarob has joined #openstack-meeting-320:29
*** obondarev has joined #openstack-meeting-320:29
*** sarob has quit IRC20:34
*** flwang1 has joined #openstack-meeting-320:34
*** baoli has joined #openstack-meeting-320:35
*** belmoreira has joined #openstack-meeting-320:42
*** pballand has joined #openstack-meeting-320:49
*** baoli has quit IRC21:01
*** SridharRamaswamy has quit IRC21:01
*** SridharRamaswamy has joined #openstack-meeting-321:02
*** baoli has joined #openstack-meeting-321:02
*** emagana has joined #openstack-meeting-321:06
*** Sukhdev has quit IRC21:10
*** matrohon has quit IRC21:17
*** Sukhdev has joined #openstack-meeting-321:17
*** peristeri has quit IRC21:20
*** jpomero has quit IRC21:21
*** baoli has quit IRC21:24
*** emagana has quit IRC21:24
*** baoli has joined #openstack-meeting-321:24
*** emagana has joined #openstack-meeting-321:24
*** emagana_ has joined #openstack-meeting-321:27
*** emagana has quit IRC21:27
*** amitpp has joined #openstack-meeting-321:30
*** emagana has joined #openstack-meeting-321:31
*** emagana_ has quit IRC21:31
*** peristeri has joined #openstack-meeting-321:37
*** Guest8638 has quit IRC21:46
*** tonyb has joined #openstack-meeting-321:47
*** banix has quit IRC21:49
*** hareeshp has quit IRC21:50
*** mattfarina has quit IRC21:50
*** MaxV has quit IRC21:51
*** amitpp has quit IRC21:58
*** SridharRamaswam1 has joined #openstack-meeting-322:00
alaskiAnyone around for the cells meeting?22:00
tonybalaski: yup22:00
belmoreirayes22:00
vineetmenon_alaski: yeah22:00
leifzalaski: I'm around... but more lurking than anything else22:00
dansmithI am, but only barely22:01
*** SridharRamaswamy has quit IRC22:01
alaskidansmith: same here :)22:01
*** lhcheng has joined #openstack-meeting-322:01
alaski#startmeeting nova_cells22:01
openstackMeeting started Wed Nov 26 22:01:24 2014 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: nova_cells)"22:01
openstackThe meeting name has been set to 'nova_cells'22:01
alaskihttps://wiki.openstack.org/wiki/Meetings/NovaCellsv2#Next_Meeting22:01
leifz:-)22:01
*** melwitt has joined #openstack-meeting-322:01
alaskiI've carried over the agenda from last week, but we can just touch on everything quickly22:01
alaski#topic manifesto22:02
vineetmenon_#help22:02
*** openstack changes topic to "manifesto (Meeting topic: nova_cells)"22:02
alaskiI know dansmith has been working on the manifesto, but it isn't up for general feedback yet22:02
dansmithI'm cool with dropping it here if you are22:02
*** lhcheng_ has joined #openstack-meeting-322:03
alaskidansmith: sure22:03
dansmithhttps://etherpad.openstack.org/p/kilo-nova-cells-manifesto22:03
dansmithif people have general feedback, please add it to a section at the bottom or something22:03
alaskiI know leifz is also interested in this and has sent some ideas to me which might be worth incorporating22:03
dansmithcool22:04
alaski#link https://etherpad.openstack.org/p/kilo-nova-cells-manifesto22:04
bauzas\o22:04
leifzdansmith: I can share directly, I just wanted to sanity check before... it's more big picture stuff.. I'll find a spot to add probably Friday.22:04
*** simon-AS5591 has quit IRC22:04
dansmithcool22:05
*** lhcheng has quit IRC22:05
leifzgood stuff by the way dansmith :-)22:05
dansmithI will say, for those that are looking at it,22:05
*** lhcheng_ has left #openstack-meeting-322:05
dansmithwe specifically didn't put in the solutions to all the problems we have, or even document all the problems22:05
dansmithwe know there are lots of challenges to solve, but this was supposed to just be documentation of the idea/goal22:06
alaskiright, I actually pushed back against that a little22:06
dansmithwe can create another page for grievances or something and for solution brainstorming22:06
leifzIt's less solutions and why people should care IMHO22:06
alaskiI didn't want this to need editing after we had implemented a couple of specs22:06
bauzasdansmith: which kind of deliverable do you expect ?22:06
vineetmenon_dansmith: but should be sort out almost all technical queries before going ahead?22:06
alaskivineetmenon_: those should be sorted out in specs I think22:06
dansmithyar22:07
dansmithbauzas: not sure what you mean22:07
vineetmenon_alaski: fair enough22:07
melwittagree that specs are for problem/solution details22:07
bauzasdansmith: I mean, how long can I review this manifesto ?22:07
dansmithbauzas: as long as you want? :)22:08
dansmithbauzas: as soon as alaski stops this meeting, I'm going away for four days, so .. :)22:08
bauzasdansmith: ok, so how the other people will know about the manifesto ? :)22:08
alaskidansmith: so I can keep you from that indefinitely? :)22:08
alaskibauzas: it will eventually get proposed to devref in Nova22:08
bauzasalaski: ack22:09
belmoreiradansmith: I'm reading it... very good stuff22:09
dansmithanyway,22:09
dansmithlet's not read it together live,22:09
dansmithwe can chat again next week22:09
bauzasagreed22:09
dansmithalaski: no, that's lower bound :)22:09
alaski:)22:09
alaskiwe'll come back to this next week22:09
vineetmenon_#agreed22:09
belmoreiraoperators should be actively informed as well22:09
alaski#action anyone interested please read and comment on the manifesto22:10
*** banix has joined #openstack-meeting-322:10
alaskibelmoreira: good point.  We can circulate this on the operators list for feedback as well22:10
*** obondarev has quit IRC22:10
alaskibut I'd like for that to happen once we've done a first pass on it22:11
dansmithyeah22:11
vineetmenon_alaski: circulate it next week, then in the mailing list22:11
*** obondarev has joined #openstack-meeting-322:11
bauzaseh, EU people don't have Thanksgiving, so you can go on vacation while we review the manifesto ;)22:12
belmoreirabauzas: :)22:12
*** banix has quit IRC22:12
dansmithyeah, you poor folks :(22:12
dansmithalthough a whole holiday dedicated to eating is very american :)22:13
alaskivineetmenon_: let's see how it looks when we check back next week22:13
bauzas:)22:13
alaski#topic specs22:13
*** openstack changes topic to "specs (Meeting topic: nova_cells)"22:13
alaskiunfortunately there's not a great link to provide here, though I can link them all separately22:14
bauzas+122:14
alaskibut there are 3 specs now I think22:14
bauzasis there a Gerrit topic ?22:14
alaskihttps://review.openstack.org/135424 https://review.openstack.org/135644 https://review.openstack.org/13649022:14
alaskibauzas: there isn't since they're associated with different bps22:14
vineetmenon_alaski: yeah.. 1 about migration, 2 about cells. All of then from you22:15
bauzasalaski: oh right22:15
vineetmenon_%s/then/them22:15
*** alexpilotti has quit IRC22:15
alaskithe topic of handling deleted rows has come up and started a ML discussion22:15
bauzasat least all of them are having dependencies, so that's easy provided you have the new Gerrit UI22:15
alaskibauzas: yeah, that's helpful22:16
bauzasalaski: sounds like you have consensus on the soft delete ?22:16
alaskibauzas: I think there's consensus on not doing soft delete like we currently do it22:16
bauzasalaski: well, not exactly consensus, but strong majority22:16
alaskibut no clear plan forward22:16
vineetmenon_alaski: and it has gather quite a bit of momentum, the email discussion22:16
alaskiI don't want to block on that so I may try to defer that to a later spec22:17
bauzasalaski: +122:17
belmoreiraalaski: +122:18
alaskibut please review the specs, and if you see gaps please bring it up in a meeting or propose something to cover it22:18
bauzasalaski: I left a comment btw. on the URIs22:18
alaskiI think there's at least one more spec needed for populating data in the cells mapping22:19
bauzasalaski: maybe this meeting is not the good time for discussing it22:19
alaskibauzas: well, you're keeping dan from vacation... :)22:19
bauzasalaski: agreed, and I'm keeping myself away from bed22:19
belmoreiraalaski: we still don't have a clear picture how top and child dbs will look like22:20
vineetmenon_"populating data in the cells mapping" specs requires new schema, right22:20
belmoreiraalaski: having that will be important for the "delete" discussion as well22:20
dansmithbelmoreira: why?22:20
alaskivineetmenon_: there's a schema proposed, but nothing proposed on how to get data into it22:21
belmoreiradansmith: I'm interested to know where instance information should live. top or child?22:21
dansmithbelmoreira: definitely in the children, that's the whole point22:21
bauzas+122:21
dansmithsee line 14  of the manifesto :)22:21
vineetmenon_dansmith: does that mean top level will not have anything except the instance information as detailed in the spec?22:22
belmoreiradansmith: But if delete goes to top, how you remove old data from child?22:22
alaskibelmoreira: I responded to your email on that.  I think we want to make sure that deleting at the api level doesn't mean the same as deleting in the cell22:22
dansmithvineetmenon_: no, the top level will have the mapping, and also things like flavors, keypairs, and other bits of information that are common to the whole deployment22:22
bauzasbelmoreira: I think deletes are different if you consider a cell or an instance22:22
*** banix has joined #openstack-meeting-322:22
alaskibelmoreira: a delete would delete in the child, and doesn't need to touch the mapping.  that can be deleted independently22:22
dansmithbelmoreira: I dunno what you mean about "old data", but any change (delete, update) that goes to the top will modify the thing in the child database, because that's the only place it lives22:23
dansmithunlike current cells, we don't need to delete it in both places and/or sync that it has been deleted22:23
belmoreiradansmith: maybe is that what I'm missing... understand how to delete in map table and child DB without sync22:24
alaskithere's a big change here, which is that the mapping is almost wholly independent of the instance22:24
alaskiso they don't need to be synced22:24
leifzWe do talk about cache'ing the information at global level, but that is standard cleaning for a cache'ing implementation.22:24
belmoreiraalaski: ok22:25
bauzasbelmoreira: persistence is local to the object22:25
leifzchild cell dbs are the authority for instance information.22:25
*** banix has quit IRC22:25
alaskileifz: right22:26
vineetmenon_..and the command to alter the database is direct not via message queue22:26
tonybSo a query for a dleted instance would match in the top DB, lookup the mapping a query the child woudl say "doesnt exist" right?22:26
alaskibelmoreira: does that make sense about deletes?22:26
vineetmenon_i mean n-api to child db22:26
belmoreiraalaski: yes, thanks22:26
tonybwould the top table do anything other than pass that back to the caller?22:26
dansmithvineetmenon: correct22:26
dansmithtonyb: the top table is just a mapping of what is where, you still have to talk to the database that has the thing you're looking for, once you determine where it is22:27
tonybdansmith: right.  I get that part.22:27
tonyboh wait the top DB tells the client "it's over there"22:27
dansmithno22:28
tonyband the client talks the the child DB?22:28
dansmithbi22:28
vineetmenon_alaski: all other service will use the usual message queue, except n-api-cell, which will directly get hold of DB... is this right22:28
dansmithno, it tells the api where to find it, on behalf of the client22:28
*** sergef has quit IRC22:28
dansmithtonyb: right now, it's implied that the instance is in "the" database, because there is only one (as far as the api is concerned)22:28
tonybdansmith: okay that's wahtr I thought at first.22:28
tonybdansmith: okay.  that's also as I thought.22:28
alaskivineetmenon_: anything that uses a queue now will continue to use a queue22:28
dansmiththis would add a switch in front of that to not just imply the database location22:29
*** mrmartin has quit IRC22:29
bauzasI think we all need to read the manifesto carefully :)22:29
dansmithyes :)22:29
tonybI guess I'll read the specs and if they'er not at all clear poke at that level22:29
tonybrather than keep eveyone here22:29
vineetmenon_bauzas: haha.. yes22:29
alaskiI think a diagram might help too22:29
dansmithalaski: yeah, good point, I suck at drawing, so I volunteer you :)22:29
alaskidansmith: heh.  I'm fine with that22:30
alaski#action alaski to diagram cellsv2 flow and approximate table split22:30
alaskiwhich leads to...22:30
alaski#topic analysis of tables22:30
*** openstack changes topic to "analysis of tables (Meeting topic: nova_cells)"22:30
alaskiI don't believe there's anything to report here22:30
dansmithno, because I suck22:31
dansmithand because flavors have been kicking my ass all week22:31
alaskiwell, because flavors suck22:31
bauzass/flavors/data migration, eh ?22:31
vineetmenon_alaski: on that note, i have generated an ER diagram for nova db.. I can share it on ML if anyone needs...22:31
dansmithbauzas: no, just flavors22:32
melwittflavors...22:32
dansmithbauzas: the migration is easy22:32
bauzasdansmith: speak for you :)22:32
dansmithflavors, I want to set on fire22:32
alaskiI think getting this sorted out will help a lot with understanding of where this is headed22:32
alaskiat least getting some things sorted out22:32
bauzasagreed22:32
alaskiso maybe we just start with some easy ones and get something in place22:32
vineetmenon_alaski: the patches by gary are all merged... shouldn't that solve flavor?22:32
bauzasYAE ? yet another etherpad ?22:32
belmoreiraflavors is not the worst in my opinion...22:33
alaskivineetmenon_: yeah, share that on the ML22:33
belmoreirahow about aggregates?22:33
alaskivineetmenon_: it solves some of it, although there are two more by him that need merging22:33
alaskibauzas: yeah, probably another etherpad22:33
bauzasbelmoreira: I don't think that aggregates are considered as an easy one :)22:33
bauzasbelmoreira: I'm personnally convinced that aggregates are local to cells22:34
alaskiI'm going to take an action to get something together with just easy ones.  like mapping tables in the api and flavors, and instances in the cells22:34
bauzasbelmoreira: but some other people can argue on this22:34
alaski#action alaski start an etherpad on easy table splits22:35
bauzasbelmoreira: cells are a certain level of segregation, aggregates are another level of segregation IMHO22:35
alaskithat will pair nicely with the diagram I need to do22:35
belmoreirabauzas: I think we will need a meeting only for that. But I agree with you22:35
*** lhcheng has joined #openstack-meeting-322:35
vineetmenon_bauzas, alaski, belmoeira: let's start with easy ones.. and subsequently resolve others...22:35
bauzasbelmoreira: well, the problem is that contextual information (aka. metadata) is attached to a placement thing, and here comes our problems...22:35
alaskiyeah, we can devote a much larger meeting time to that discussion22:36
bauzasvineetmenon_: ack, I was diverting22:36
alaskiafter we get some easier ones nailed down22:36
alaski#topic testing22:37
*** openstack changes topic to "testing (Meeting topic: nova_cells)"22:37
alaskiThere's this now https://etherpad.openstack.org/p/nova-cells-testing22:37
alaskiwhich needs some real work from me22:37
alaskihttps://review.openstack.org/#/c/135285/ gets cells failures down from ~150 to ~9522:37
alaskiwhich is a possible short term solution which can be superceded by dansmiths flavor work22:38
alaskiI have a tempest fix up for some service test failures22:38
alaskiand I've determined that fixed-ip tests should be excluded22:38
alaskiI've been looking at floating-ip tests to see what's up there but havne't made much progress yet22:39
bauzasouch, are you planning to fix functional test coverage for Cells V1 ?22:39
bauzasI missed the rationale of that work :)22:39
alaskihttp://logs.openstack.org/85/135285/5/experimental/check-tempest-dsvm-cells/8b23f8d shows some other tests that need work though22:39
vineetmenon_bauzas: to check what all things work under current inplementation22:40
alaskibauzas: fix, or exclude tests that we don't expect to work22:40
dansmithright, we need to make sure cellsv1 doesn't rot22:40
bauzasalaski: oh, for regression checking ?22:40
alaskiexactly22:40
bauzasalaski: got it22:40
alaskithere's been some progress, but there are still some test classes I'm not sure of yet22:41
alaskiI'd like to get that laid out on the etherpad so others can help look if they're inclined22:42
vineetmenon_alaski: I can do my bit, if guided...22:42
*** banix has joined #openstack-meeting-322:42
alaski#action alaski record in progress test work, and remaining failing tests in etherpad22:42
alaskivineetmenon_: awesome.  I'll ping you once I get the etherpad in better shape22:43
vineetmenon_I'm a newbie, so...22:43
* tonyb is also very happy to help with whatever can be delegated22:43
vineetmenon_alaski: sure22:43
alaskitonyb: noted, thanks22:43
dansmithooh, nice22:43
dansmithtonyb: be careful what you volunteer for :)22:43
leifzI'd offer, but alaski already delegates enough to me :-)22:44
* bauzas should do call for volunteers in other meetings...22:44
tonybdansmith: I'm green but feel free to pass work my way22:44
tonybdansmith: Gotta learn somehow22:44
dansmithessellent22:44
vineetmenon_dansmith: lisp22:44
tonybdansmith: after your long weekend ;P22:44
alaskileifz: :)22:44
melwittI want to help too, but new to cells. this is my first cells meeting22:45
alaskiI had another topic on the agenda about cells scheduling requirements but there hasn't been any progress there yet22:45
tonybmelwitt: well it's inly the 2nd cellsv2 meeting ;P22:45
*** alexpilotti has joined #openstack-meeting-322:45
alaskimelwitt: cool22:45
alaskiwell have everyone as a cells expert in no time22:45
dansmithI think there was a plan to come up with some low-hanging fruit on the cellsv1 test effort22:46
alaskiwe'll22:46
tonyb(and the first at a "reasonable" time)22:46
melwitt:)22:46
alaskidansmith: yes.  I haven't quite gotten there yet, but I'm going to get it into that etherpad22:46
alaskihttps://etherpad.openstack.org/p/nova-cells-testing22:46
vineetmenon_tonyb: Americans can say that. :)22:46
tonybvineetmenon_: Meh I'm in Australia22:47
leifzalaski: put an action for me to help find the categories... since i already did this run through once I should help.22:47
alaski#action leifz help categorize test failures22:48
leifzall in the U.S. have a good holiday..  all everywhere else have a good rest of the week, I'm out.22:48
alaskialso, tonyb answered my question from last week about this later meeting time22:48
alaskileifz: ok.  happy holiday22:48
alaski#topic open discussion22:48
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"22:48
*** banix has quit IRC22:49
*** SridharRamaswamy has joined #openstack-meeting-322:49
alaskithis meeting time has drawn a few different folks than last week, so it may be worth having22:49
*** SridharRamaswam1 has quit IRC22:49
tonybalaski: please keep it if you can.22:50
*** zhipeng has quit IRC22:50
tonybalaski: I'm keen to help and wont be at the alternate time22:50
bauzasI don't know if belmoreira can regularly attend this meeting, I took this one opportunisticly22:50
alaskitonyb: okay.  good to know.  I will keep running it if it's useful22:51
belmoreirabauzas: I will try22:51
*** etoews has quit IRC22:51
alaskianything else people would like to discuss here?22:52
tonybalaski: you could move it an hour or two earlier if that helps (but only during the US winter)22:52
alaskitonyb: It might help the US east coast, but I don't think that helps Europe that much22:52
bauzasalaski: not really :)22:53
bauzasI mean, there was no good TV shows tonight... :)22:53
alaskiheh22:53
belmoreirabauzas: :)22:53
bauzasthen, I assume we're done ? :)22:54
alaskiseems like it22:54
alaski#endmeeting22:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:54
openstackMeeting ended Wed Nov 26 22:54:22 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2014/nova_cells.2014-11-26-22.01.html22:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2014/nova_cells.2014-11-26-22.01.txt22:54
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2014/nova_cells.2014-11-26-22.01.log.html22:54
bauzasthanks all22:54
alaskidansmith: get out of here :)22:54
bauzasbye22:54
alaskithanks22:54
tonybThanks all22:54
dansmithwiit!22:54
bauzasenjoy Black Friday22:54
dansmither, woot even!22:54
vineetmenon_all: bye22:54
tonybenjoy thanksgiving those that have it22:54
belmoreirathanks all22:54
melwittthanks :)22:55
*** belmoreira has quit IRC22:55
*** vineetmenon_ has quit IRC22:55
*** hareeshp has joined #openstack-meeting-322:56
*** Ark has joined #openstack-meeting-322:56
*** Ark is now known as Guest5107522:57
*** melwitt has left #openstack-meeting-322:57
*** etoews has joined #openstack-meeting-322:57
*** banix has joined #openstack-meeting-322:58
*** elmiko has joined #openstack-meeting-322:59
*** hareeshp has quit IRC23:01
*** Guest51075 has quit IRC23:01
*** igordcard has quit IRC23:04
*** MarkAtwood has quit IRC23:08
*** SumitNaiksatam has quit IRC23:10
*** SumitNaiksatam has joined #openstack-meeting-323:10
*** peristeri has quit IRC23:13
*** SridharRamaswamy has quit IRC23:14
*** Sukhdev has quit IRC23:17
*** dboik has quit IRC23:24
*** SridharRamaswamy has joined #openstack-meeting-323:29
*** pballand has quit IRC23:35
*** banix has quit IRC23:42
*** SumitNaiksatam has quit IRC23:42
*** banix has joined #openstack-meeting-323:42
*** baoli has quit IRC23:44
*** baoli has joined #openstack-meeting-323:45
*** etoews has quit IRC23:47
*** SumitNaiksatam has joined #openstack-meeting-323:49
*** sigmavirus24 is now known as sigmavirus24_awa23:53
*** banix has quit IRC23:56
*** etoews has joined #openstack-meeting-323:57
*** marun has quit IRC23:57
etoewsapi wg meeting to start in a minute23:59
cyeohetoews: hi!23:59
etoewscyeoh: hello!23:59

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