16:04:47 <rkukura> #startmeeting networking_ml2
16:04:48 <openstack> Meeting started Wed Oct  1 16:04:47 2014 UTC and is due to finish in 60 minutes.  The chair is rkukura. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:04:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:04:52 <openstack> The meeting name has been set to 'networking_ml2'
16:05:23 <rkukura> #link agenda: https://wiki.openstack.org/wiki/Meetings/ML2#Agenda
16:05:36 <rkukura> #topic Announcements
16:05:58 <rkukura> Kilo is now open for new specs
16:06:27 <rkukura> There is a new template as well, so some updates will be needed moving Juno specs to Kilo
16:06:41 <Sukhdev> Spec template has changed a bit -
16:07:01 <rkukura> Sukhdev: anything significant?
16:07:18 <Sukhdev> rkukura: not really
16:07:59 <rkukura> Kilo Summit topics for Neutron: https://etherpad.openstack.org/p/kilo-neutron-summit-topics
16:08:02 <romilg> One question, I would like to propose a new CLI in python neutron-client , do I need to propose a specs in kilo ?
16:08:53 <rkukura> romilg: Is this part of a spec for a new feature, or purely a client change?
16:10:18 <rkukura> The summit topics etherpad above lists quite a few ideas related to ML2. I added an agenda item for today to discuss ML2 themes for kilo that may help us determine what summit sessions would be most useful.
16:10:56 <rkukura> Any other announcements?
16:11:26 <rkukura> #topic Action Items
16:12:07 <rkukura> We had: banix to work with mlavalle and the team to figure out best testing strategy for bulk operations
16:12:25 <rkukura> but I don’t see either banix or mlavalle online
16:12:51 <rkukura> We also had an AI for shivharis to followup with mestery regarding RC1 bugs
16:13:01 <rkukura> But shivharis is traveling
16:13:16 <rkukura> Any other AI updates?
16:13:41 <rkukura> #topic Bugs
16:14:35 <rkukura> When I last checked, there were 3 bugs blocking RC1, but none seemed to involve ML2
16:14:57 <rkukura> There was one ML2 bug regarding a deadlock that was resolved yesterday
16:15:32 <rkukura> One of the 3 bugs is the removal of the old openvswitch and linuxbridge plugins :)
16:15:52 <rkukura> Does anyone have any bugs that need discussion today?
16:16:26 <Sukhdev> rkukura: looks like our bug czar is missing today
16:16:32 <romilg_> https://bugs.launchpad.net/neutron/+bug/1179223
16:16:34 <uvirtbot> Launchpad bug 1179223 in neutron "Retired GRE and VXLAN tunnels persists in neutron db" [High,In progress]
16:16:37 <rkukura> Sukhdev: right, I mentioned that
16:16:54 <romilg_> it would be great if we could set the milestone for the same
16:17:29 <romilg_> Another
16:17:29 <romilg_> https://bugs.launchpad.net/neutron/+bug/1224978
16:17:31 <uvirtbot> Launchpad bug 1224978 in neutron "port binding on multi segment networks could lead to agent misconfiguration" [Medium,In progress]
16:17:31 <amotoki> I think it is already in good shape.
16:17:32 <rkukura> romilg_: That one does seem important, but is not currently targeted as a Juno RC. I think there is a patch, right?
16:17:56 <romilg_> yeah
16:18:02 <Sukhdev> romilg_: Shiv had action item to follow up on that bug with mestery to include in RC1
16:18:14 <romilg_> ok
16:18:24 <rkukura> The 2nd sounds like one for kilo
16:18:27 <amotoki> The first one is https://review.openstack.org/#/c/121000/
16:18:52 <amotoki> re: 2nd one, +1 for kilo.
16:19:22 <rkukura> amotoki: do you feel the 1st one should block RC1?
16:19:35 <amotoki> rkukura: no. it is not a blocking issue.
16:20:20 <rkukura> amotoki: It does involve schema changes, so would not easily be backported
16:20:22 <amotoki> rkukura: it contains db change, so we cannot backport it after the release. this is the only reason I am reviewing it.
16:21:09 <rkukura> amotoki: Seems we should talk to mestery about it.
16:21:22 <rkukura> Any other bugs to discuss today?
16:22:00 <rkukura> #topic Specs
16:22:36 <rkukura> We’ll want to update https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews#Under_Review as we post specs for Kilo
16:22:48 <rkukura> Anything else on specs for today?
16:23:18 <rkukura> #topic Kilo Themes
16:23:34 <rcurran> rkukura, will you be updating, reposting the hierarchical spec?
16:23:44 <rkukura> rcurran: yes
16:24:01 <rkukura> My goal in adding this to the agenda was to get us started prioritizing work for ML2 during Kilo
16:24:56 <rkukura> And then to use that to determine how we can make best use of the design summit
16:25:34 <rkukura> So I added a number of items, mostly things that didn’t get completed in Juno, and/or that have been discussed in the past
16:26:03 <amotoki> rkukura: are you talking about https://etherpad.openstack.org/p/kilo-neutron-summit-topics ?
16:26:21 <rkukura> amotoki: No, the list in this meeting’s agenda
16:26:36 <amotoki> rkukura: thanks
16:26:40 <rkukura> #link https://wiki.openstack.org/wiki/Meetings/ML2#Meeting_October_1.2C_2014
16:27:55 <rkukura> What do others feel are the top priorities for ML2 during Kilo (other than vendor-speciic stuff)?
16:28:43 <Sukhdev> rkukura: I think your list is good
16:29:06 <rkukura> Anything missing?
16:29:25 <rkukura> Anything anyone feels is not worth at least considering?
16:29:49 <amotoki> I think it is good coverage for ML2 items.
16:30:49 <rkukura> Lets all think about this during the next week, and try to prioritize a bit next week, and then we can start talking about which items need time at the summit
16:30:53 <amotoki> Possible items related to ml2 are external attachments, port security, vlan aware VMs.... and so on, but it is not specific to ML2.
16:31:06 <Sukhdev> rkukura: perhaps the item on moving drivers out of tree can be removed and let it be at Neutron level
16:31:30 <rkukura> Sukhdev: perhaps, but maybe we’d need to stabilize the driver API to enable that
16:32:09 <Sukhdev> rkukura: Yes, that will be a general issue across the whole Neutron APIs
16:32:17 <rkukura> Sukhdev: good point
16:33:05 <rkukura> Let’s revisist this next week then
16:33:13 <rkukura> #topic Open Discussion
16:33:44 <rkukura> I’m happy to wrap up early an have some lunch before my next meeting ;)
16:34:12 <rkukura> Anyone want to discuss anything ML2 related?
16:34:56 <amotoki> how about splitting drivers dir into type and mech in Kilo?
16:35:16 <amotoki> we see many drivers in the same dir now.
16:35:18 <rkukura> amotoki: what about extension drivers?
16:35:36 <amotoki> rkukura: ah.. just forgot it.
16:36:26 <rkukura> amotoki: I think we’ll be seeing more cases where vendors have their own type drivers for their fabrics, etc., so these might be more coupled with the mechanism drivers. Similarly with vendor-specific extensions
16:36:52 <amotoki> I am thinking similar. one point i am not sure is how to place files if a driver is related to multiple drivers (e.g, ext and mech )
16:37:04 <rkukura> Maybe we should organize into vendor subdirectories, along with a directory for the standard type drivers?
16:37:42 <rkukura> The nice thing about using entrypoints for drivers is that we can reorganize the code without breaking configs
16:37:47 <amotoki> it might be better.
16:38:22 <rkukura> Any other discussion topics?
16:38:55 <rkukura> Thanks everyone!
16:39:25 <rkukura> #endmeeting