16:01:49 #startmeeting networking_ml2 16:01:49 Meeting started Wed Feb 25 16:01:49 2015 UTC and is due to finish in 60 minutes. The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:50 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:53 The meeting name has been set to 'networking_ml2' 16:02:16 #topic: Agenda 16:02:38 #link: https://wiki.openstack.org/wiki/Meetings/ML2 16:02:50 #topic: Announcements: 16:03:11 Feature freeze for Kilo is next week 16:03:41 If you are working on a new feature, keep it in mind 16:04:11 shivharis is absent - not feeling well 16:04:31 That is all I have 16:04:47 Anybody has any thing which team should be aware of? 16:05:37 #topic: ML2 Driver Decomposition Discussion 16:06:03 We have been having good discussion on this topic for past few weeks 16:06:12 Sukhdev: were you planning to post the info on a wiki? 16:06:16 How are your drivers coming along? 16:06:52 banix: I have been bad (actually swamped) - will try to do it this week 16:07:15 banix: but, I am available to help out - 16:07:24 Sukhdev: np. it would be most helpful now that you have gone through the hard work of figuring things out 16:07:27 feel free to ping me on irc 16:07:38 great thanks 16:08:27 There was a great discussion on this topic in Neutron Core meeting earlier this week - related to distros 16:09:49 The process is being documented - but, in general one has to have CI functional and the library uploaded at pypi to be included 16:10:26 armax is putting together a list of "ready" drivers 16:10:50 these drivers will become candidates for inclusion 16:11:25 Any body has any question or require any clarification on this? 16:11:42 is it the open for review? (the process I mean) 16:12:15 moshele: I do not believe it is yet 16:12:25 ok 16:12:29 It really is not a big process per se 16:13:08 As soon as your driver is ready and meets those two criteria you make sure to add the etherpad (or spreadsheet) that armax will create 16:13:43 that spreadsheet or etherpad will be used to track the ready drivers/plugins 16:14:29 One last thing I want to say on this topic is: 16:14:54 Please share your expeiences with the team - so that others can benefit 16:15:08 this process will continue through the Liberty cycle 16:15:40 #topic: ML2 Sync and Error Handling 16:15:58 manish does not seem to be here 16:16:18 I reviewed his patch - https://review.openstack.org/#/c/154333/ 16:16:33 This is looking good 16:16:48 He is beefing it up - but, not there yet 16:17:15 Please do spend some time to become familiar with this - and provide your feedback/suggestions to him 16:17:41 Since he is not here to provide update, we can move on... 16:18:03 #topic: Potential ML2 impacting BPs 16:18:33 rkukura made a note that there are couple of BPs that are being worked on which could potentially impact ML2 16:19:01 So, we thought we bring it to your attention so that you are aware of it and you should review them 16:19:18 #link: https://blueprints.launchpad.net/neutron/+spec/nfv-vlan-trunks 16:19:36 #link: https://blueprints.launchpad.net/neutron/+spec/restructure-l2-agent 16:20:05 banix: second one is about L2 agent refactoring - you may want to look at it 16:20:40 Is that different from modular l2 agent? 16:20:56 yamahata: I believe so 16:21:03 Sukhdev: yamahata: yes different 16:21:10 okay thanks 16:21:43 rkukura want to say anything about the first one? 16:22:28 The two patches so far don’t impact ML2, but I’m assuming ML2, or at least some drivers, will need some changes to support trunking 16:23:42 I admit I haven’t taken time to re-read the spec, so details on what’s coming could be in there 16:24:43 I think it is worth for all of us to give it a read 16:24:53 hence, we brought it up here 16:24:53 Sukhdev: right - I plan to 16:25:13 anything else on this? 16:25:51 #topic: ML2 Extension Driver API enhancements 16:26:03 This one is in good shape - 16:26:27 I reviewed https://review.openstack.org/#/c/152759/ - this is ready to merge 16:26:39 +1 16:26:55 https://review.openstack.org/#/c/129178/ - is also moving along well 16:26:58 I just posted a comment on the 2nd patch suggesting to fix the consistency issue the opposite way. 16:27:25 rkukura: I'm fine with that. 16:27:42 any objections? 16:28:14 seems no. I'll update it today. 16:28:26 yamahata: thanks 16:28:38 yamahata: please do 16:28:59 and https://review.openstack.org/#/c/126552/ 16:29:05 for the another patchset https://review.openstack.org/#/c/126552/ 16:29:08 yes 16:29:30 I am not sure if we need a functional test on it 16:30:16 it's a patch to add port-security feature 16:30:55 it will modify the iptables rules, Muller leave comments to add functional test 16:31:25 to test the connectivy before and after set the port-sec attr 16:31:33 yalie: past experience suggests UTs should do - and you can propose a separate patch for tempest tests in addiition 16:31:34 but I think that looks like a tempest case. 16:31:58 yalie: Since the extension itself is being integrated as an extension driver, I’m wondering if the changes you are making to plugin.py could be integrated as a mechanism driver? 16:32:06 Sukhdev: thanks 16:32:55 I think not 16:32:59 rkukura: the issue is the dependency on security group. 16:33:24 yes ,and address-pairs 16:33:35 rkukura: to address it, security group needs to be converted to extension driver and the sg ED needs to be processed first. 16:33:59 So I suppose the conversion takes a while, so for L cycle. 16:34:09 yamahata: I see what you mean 16:34:27 modular agents! 16:34:32 We are willing to work on the conversion 16:34:36 for L cycle. 16:34:53 I’d suggest adding TODO comments for followup work where appropriate 16:35:06 I see 16:35:13 Makes sense. 16:35:37 rkukura: thanks 16:35:38 OK, thanks 16:35:52 on to the next topic - 16:36:17 BTW, L cycle now has a name - and it is Liberty 16:36:41 #topic: Bugs 16:36:53 Our bug czar is under weather - 16:37:06 any specific bug we want to discuss here? 16:37:19 #link: https://bugs.launchpad.net/neutron?field.searchtext=ml2 16:37:38 * Sukhdev waiting 16:38:00 #Open Discussion 16:38:13 Any thing to discuss? 16:38:42 If not, we are done - 16:39:03 it is good to keep it short and simple :-) 16:39:09 * Sukhdev waiting 16:39:13 +1 16:39:21 Thanks Sukhdev! 16:39:26 sounds good! 16:39:31 Thanks folks 16:39:36 see you next week 16:39:37 bye 16:39:40 bye 16:39:41 #endmeeting