21:00:20 #startmeeting networking 21:00:22 Meeting started Mon Dec 10 21:00:20 2018 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:25 The meeting name has been set to 'networking' 21:00:27 o/ 21:00:42 o/ 21:00:48 o/ 21:01:20 hi 21:01:23 Today's agenda is here: https://wiki.openstack.org/wiki/Network/Meetings 21:01:24 hi 21:01:41 o/ 21:01:45 #topic Announcements 21:02:44 First of all, the next milestone Stein-2 is fast approaching. With the holidays season between now and then, the milestone is really around the corner 21:03:34 Today, after the customary one week wait period, I added njohnston and hongbin to the Neutron core team 21:03:49 #link http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000780.html 21:03:53 \o/ 21:03:54 o/ 21:03:58 congrats, both of you :) 21:04:08 #link http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000783.html 21:04:28 congrats :) 21:04:38 Congratulations to both of you! Thanks for all your hard work and use your superpowers wisely 21:04:52 yes, congrats! 21:05:09 thank you. it is a pleasure to work in neutron team 21:05:12 Special thanks to mlavalle who has been teaching me the trade 21:05:34 and I echo hongbin - this is a wonderful team, and I am honored to be a part 21:05:40 i would like to thank slaweq for his mentorship to me 21:05:56 Any other announcements? 21:06:35 ok, let's move on 21:06:54 #topic Blueprints 21:07:34 These are the blueprints we are working on during this cycle: https://launchpad.net/neutron/+milestone/stein-2 21:08:09 njohnston: please note that I updated the assignee to you of https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch 21:08:09 I am going to try to push hard to get the remaining patch for bulk port upgrades ready this week, as I am on PTO from 12/15 to EOY - so as you mentioned before, not much time before S-2. 21:08:33 mlavalle: Got it! 21:08:42 njohnston: ok, will keep an eye on those patches 21:09:10 thanks mlavalle 21:09:23 I also updated the assignee to tidwellr of https://blueprints.launchpad.net/neutron/+spec/subnet-onboard 21:10:22 Please note that I added to the Stein-2 dashboard https://blueprints.launchpad.net/neutron/+spec/network-segment-range-management 21:11:01 We recently approved the spec: https://review.openstack.org/#/c/599980/ 21:11:47 and Kailun Qin has indicated that he will push code in bite size patches this week 21:11:54 so please keep an eye on those 21:12:50 Finally, this sr-iov mirroring spec seems to be close to merge: https://review.openstack.org/#/c/574477/ 21:13:19 yamamoto left a question in the patch, that I would like answered before merging 21:13:43 earlier today I sent an email to munish. Hopefully he will respond soon 21:14:39 Yes, I do have a question 21:14:54 This one is done as far as I know: https://blueprints.launchpad.net/neutron/+spec/router-gateway-ip-qos 21:15:21 we even merged the update to the Networking Guide, right slaweq? 21:15:31 mlavalle: I think so 21:15:41 ok, I'll mark it complete 21:15:42 I will check it and update BP tomorow morning 21:16:37 ok.... 21:16:41 let's move on 21:16:56 #topic Community Goals 21:17:32 I have an update on policy-in-code 21:17:39 Great! 21:17:44 First, FYI, I changed the blueprint URL to https://blueprints.launchpad.net/neutron/+spec/neutron-policy-in-code (from get-policy-from-neutron-lib) because the old slug is no longer correct. 21:17:56 ack 21:18:07 I succeeded to identify the root cause of unit test and func test failures 21:18:13 It is because policy-in-code default rules inside the code are loaded before API extensions. 21:18:21 As a result, convertor functions used in FieldCheck are not initialized properly. 21:18:43 I am testing the latest one in https://review.openstack.org/#/c/619898/5 and waiting for the whole test results 21:19:02 I will merge thsi into the main patch and address slaweq's comments then. 21:19:23 ok 21:19:24 I hope all things are addressed in neutron side by this. 21:19:42 thx amotoki 21:19:47 do you have the pointer to the main patch handy? 21:20:07 the main patch is https://review.openstack.org/#/c/585037/ 21:20:13 Thanks! 21:20:41 any other updates on community goals? 21:22:10 ok, let's move on then 21:22:16 #topic Bugs 21:22:30 Last week, rubasov was our deputy 21:22:52 Here's the report: http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000770.html 21:23:13 you beat me to pasting it :-) 21:23:32 he has some training at it ;) 21:24:13 I see that the critical bug already has a fix proposed 21:24:33 #link https://review.openstack.org/#/c/623275/ 21:25:00 Reviwers, please take a look ^^^^ 21:26:19 I see that the for the two undecided bugs, haleyb has volunteered: https://bugs.launchpad.net/neutron/+bug/1807153 and https://bugs.launchpad.net/neutron/+bug/1807157 21:26:20 Launchpad bug 1807153 in neutron "Race condition in metering agent when creating iptable managers for router namespaces" [Undecided,New] 21:26:21 Launchpad bug 1807157 in neutron "Metering doesn't work for DVR routers on compute nodes" [Undecided,New] 21:26:27 Thanks! 21:26:44 yes, i need to take a look at those 21:27:33 and we are looking for a volunteer to take over this patch: https://review.openstack.org/#/c/581360/ 21:27:34 haleyb: thank you, I did not feel qualified for those 21:27:54 which addresses https://bugs.launchpad.net/neutron/+bug/1807396 21:27:55 Launchpad bug 1807396 in neutron "With many VMs on the same tenant, the L3 ip neigh add is too slow" [Medium,In progress] - Assigned to Thomas Goirand (thomas-goirand) 21:28:37 this has been an issue in the past 21:28:48 the patch is about optimizing it by batching it up 21:29:35 any takers? 21:30:07 mlavalle: i had found a previous patch from years ago, i think ralansoh was looking into it 21:30:12 just can't find the tab now 21:30:30 haleyb: I can ping him tomorrow morning 21:30:39 https://bugs.launchpad.net/neutron/+bug/1511134 21:30:40 Launchpad bug 1511134 in neutron "Batch DVR ARP updates" [Undecided,New] 21:31:00 that was the old original bug, we punted thinking pyroute2 would solve the problem 21:31:37 https://review.openstack.org/#/c/431197/ was the change 21:31:49 haleyb: so the bugs are duplicated? 21:32:49 yes, seem to be, even updated the same code 21:33:18 ok, I'll update one of them 21:33:20 but the proposed change isn't great since we've moved away from running /sbin/ip 21:33:55 IMO we should go with this proposed solution and we should move to pyroute2 here also 21:33:59 haleyb++ 21:34:17 I'll check with ralonsoh and see if he is taking it 21:34:48 slaweq: yes, we might be able to localize the batching to a few places, instead of in the ip_lib code 21:35:28 any other bugs we should discuss today? 21:36:13 ok, let's move on 21:36:16 On bug deputy, I am assigned to the week of Dec 31 but this week is a holiday week in Japan. Can anyone swap weeks? 21:36:43 amotoki: I can take it 21:37:04 slaweq: thanks. 21:37:19 amotoki: so you'' be on duty the week of February 4th 21:37:19 amotoki: sure, np 21:37:36 slaweq: did you ping pasuder? 21:37:48 yeah, I will care the week of Feb 4 21:37:49 mlavalle: yes, and he confirmed me that he will do it 21:38:03 slaweq: great! 21:38:38 hongbin: just to make sure, uou are scheduled for the week of December 24th. Is that ok with you? 21:38:58 mlavalle: i am fine with that 21:39:03 cool! 21:39:12 hongbin: that should be "easy" week :) 21:39:12 should be a quiet week 21:39:13 #topic neutron-lib 21:40:01 boden: any updates this week? 21:40:11 hi, just a few quick things 21:40:52 a reminder that we released neutron-lib last week... and the neutron requirements were recently bumped to use it.. other projects should consider using the latest as they get time/need 21:41:52 also a follow-up from last week's discussion on work items for neutron-lib.. I sent a note to the ML, but to recap some items are now listed on https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list 21:42:44 boden: ahhh nice. Last week I had a conversation with Sandhya form Cisco 21:43:06 she is interested in helping with items in this list 21:43:21 Sandhya, you around? 21:43:28 yes, I am here 21:43:35 perfect 21:43:55 so take a look at the items in the list 21:44:00 mlavalle ok great... I'd suggest one at a time (some require some research/design), but if someone feels optimistic grab a more than one :) 21:44:22 sadasu: please take a look at the list 21:44:33 I did take a look at the list earlier. can I take something that is unassigned? 21:44:37 even if you are not completely sure, pick one 21:44:40 sadasu and feel free to ping/email me with questions 21:44:53 boden: thank you! will do 21:45:21 if we are done with that topic, just 1 last thing 21:45:33 go ahead 21:46:18 I asked for some input/buy-in on https://review.openstack.org/#/c/621000/ njohnston found time, but was hoping at least 1 more core could have a looksee before I spend the time completing the patch 21:46:45 boden: my bad, I should have taken the time. I'll will tomorrow 21:47:01 mlavalle great thanks.. 21:47:10 and that's all I have for neutron-lib 21:47:21 * mlavalle seems to have inveneted a new form of the future tense 21:48:15 innovative! ;-) 21:48:25 ok, let's move on 21:48:33 #topic os-ken 21:48:42 hi 21:48:53 a few things about os-ken 21:49:05 1. os-ken 0.3.0 is release: https://review.openstack.org/#/c/623025/ 21:49:30 2. i am working on the migration from ryu to os-ken in neutron : https://review.openstack.org/#/c/607008/ 21:49:52 i am waiting for the CI result and see what is the next step 21:50:06 doesn't seem too bad 21:50:15 3. there is a similar effort in other project as well: https://review.openstack.org/#/c/608357/ 21:50:15 as far as the amount of change 21:50:42 yes, see if it will pass the CI or not 21:50:50 mlavalle: that is all from my side 21:51:24 hongbin: https://review.openstack.org/#/c/608357/ needs to be rebased due to come recent changes, but it's ready to go as soon as we want to pull the trigger 21:51:44 hongbin: mhhhh, should we send a message to the ML with a heads up indicating that we are changing in Neutron and dynamic-routing, in case other projects need to do the same? 21:52:06 tidwellr: ack 21:52:24 mlavalle: sure 21:52:40 hongbin: would you take care of it? 21:52:41 mlavalle: i will take care of the ML 21:52:50 hongbin: thanks! 21:53:05 let's move on then 21:53:15 #topic on demand agenda 21:53:26 amotoki: anyhting on CLI? 21:53:34 tidwellr: one thing though, you might want to bump to os-ken 0.3.0 on your patch 21:53:43 mlavalle: nothing from me on CLI 21:53:51 hongbin: will do 21:54:05 any other topics we should discuss today? 21:54:13 mlavalle: sorry I was late, but I had a question about subnet onboard 21:54:24 shoot, tidwellr 21:54:38 I can take it to the mailing list or discuss in the channel 21:54:59 if you want, send a message to the ML 21:55:38 I'm scratching my head at why the API was defined a certain way, it's poorly designed if you ask me and I'm wondering what flexibility we have to change the defininition 21:56:03 ahhh, those are interesting discussions.... 21:56:11 let's take it to the ML 21:56:14 yes, they consume more time than we have here :) 21:56:20 :) 21:56:43 but this one is worth it (at least for feature usability) 21:57:24 ok team, thanks for attending 21:57:30 #endmeeting