14:00:29 <mlavalle> #startmeeting networking 14:00:30 <openstack> Meeting started Tue Apr 9 14:00:29 2019 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:33 <openstack> The meeting name has been set to 'networking' 14:00:35 <njohnston> o/ 14:00:37 <lajoskatona> o/ 14:00:40 <bcafarel> \o 14:00:41 <rubasov> o/ 14:00:50 <tidwellr> \o/ 14:01:35 <mlavalle> Welcome everybody! 14:01:54 <haleyb> hi 14:02:06 <mlavalle> Let's get going 14:02:20 <mlavalle> #topic Announcements 14:03:21 <mlavalle> Per https://releases.openstack.org/stein/schedule.html, this is the week the community releases Stein 14:03:36 <slaweq> hi 14:03:55 <mlavalle> we had a last minute small hicup last week with some of the bulk port creation code 14:04:10 <mlavalle> but we merged the fix on time, so everything is good 14:04:25 <haleyb> mlavalle: so do we need to push a tag for stable/stein ? 14:04:28 <njohnston> \o/ thanks ralonsoh 14:05:01 <mlavalle> haleyb: I'll ask and ping you 14:05:54 <bcafarel> hmm we merged a few commits since rc1 14:05:55 <haleyb> mlavalle: ack. i just pushed reviews to tag rocky/queens/pike - https://review.openstack.org/#/c/651234/ https://review.openstack.org/#/c/651235/ https://review.openstack.org/#/c/651236/ - think pike will need an update 14:06:37 <mlavalle> With that, we should focus on the PTG 14:06:44 <amotoki> hi 14:07:07 <davidsha_> o/ 14:07:19 <mlavalle> I remind the team that we are collecting topics in the etherpad: https://etherpad.openstack.org/p/openstack-networking-train-ptg 14:07:19 <njohnston> yes just 3 weeks and a day until the PTG starts if I'm not mistaken 14:07:37 <liuyulong> yes, recently stable branches have backported many patches. 14:08:22 <amotoki> (after looking at the log) perhaps we need to cut a stable/stein update release soon after the stein release. 14:08:53 <mlavalle> amotoki: yeah that's what I think we are going to do 14:09:28 <mlavalle> This week I am going to start organizing the topics in the PTG etherpad in sessions 14:09:30 <amotoki> sounds good 14:09:40 <mlavalle> so we have an agenda for the PTG 14:10:53 <mlavalle> and I see we have 16 people confirmed to attend our social event on May 3rd. So it is going to be a fun dinner \o/ 14:10:56 <amotoki> regarding the stable branches, I also remind http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004594.html (pike extended maintenance). 14:11:20 <mlavalle> amotoki: I added a topic to the on demand agenda to talk about that 14:11:20 <amotoki> we still do not mark ocata as EM. Pike is a newcommer 14:11:52 <amotoki> let's discuss it later or in the next meeting :) 14:12:11 <mlavalle> any other announcements? 14:12:39 <mlavalle> #topic Blueprints 14:13:19 <mlavalle> The only thing that I want to mention in regards to blueprints is the openflow based DVR effort 14:14:09 <mlavalle> https://blueprints.launchpad.net/neutron/+spec/openflow-based-dvr 14:14:29 <mlavalle> This is the only blueprint that we targeted for Stein that we didn't complete 14:14:59 <mlavalle> The plan that we have discused in the L3 subteam meetings is to merge this as early as possible in TRain 14:15:08 <mlavalle> so we have time to debug it 14:15:39 <mlavalle> Here's the series of patches: https://review.openstack.org/#/q/topic:openflow-based-dvr+(status:open+OR+status:merged) 14:16:07 <mlavalle> Please help reviewing 14:16:19 <mlavalle> I know tidwellr is already working on it. Thanks 14:16:48 <slaweq> I have one question about it 14:16:57 <slaweq> https://bugs.launchpad.net/neutron/+bug/1705536 is marked as rfe-postponed 14:16:58 <openstack> Launchpad bug 1705536 in neutron "[RFE] L3-agent agent-mode dvr bridge." [Wishlist,Triaged] 14:17:03 <slaweq> should it be changed to approved? 14:17:54 <mlavalle> slaweq: done 14:18:06 <slaweq> thx mlavalle :) 14:18:27 <slaweq> I wasn't sure if that was already discussed or not yet. Now it's clear :) 14:18:43 <davidsha_> I think that might need to be reworded from Agent_Mode to Agent_Backend 14:19:03 <davidsha_> I'll do that now 14:19:10 <mlavalle> The other RFE that is approved and will start showing up in our reviews screen is https://bugs.launchpad.net/neutron/+bug/1764738 14:19:11 <openstack> Launchpad bug 1764738 in neutron "routed provider networks limit to one host" [Wishlist,In progress] - Assigned to David Bingham (wwriverrat) 14:19:32 <amotoki> in my understanding rfe-postponed RFEs are approved but we fail to find persons who work on.... if we have volunteers we can move them to rfe-approved. 14:19:57 <mlavalle> amotoki: yeap, we have people actively working on it 14:20:33 <mlavalle> going back to 1764738, here's the wip patch: https://review.openstack.org/#/c/623115 14:20:58 <mlavalle> it would be good if the team takes a look at it so we can have a fruitful discussion about it in Denver 14:21:12 <slaweq> amotoki: ok, thx. I didn't know that :) 14:22:34 <mlavalle> This week also I will attend the StarlingX networking meeting. I know they are planning to propose blueprints for Train. So I'll make sure they add them to the PTG etherpad 14:23:01 <mlavalle> any other blueprints we should discuss today? 14:24:05 <amotoki> mlavalle: is there any handy link? or can I find it in the openstack meeting page? 14:24:33 <mlavalle> amotoki: link for what? 14:24:45 <amotoki> mlavalle: starlingX meeting 14:24:50 <mlavalle> hang on 14:25:22 <mlavalle> amotoki: https://wiki.openstack.org/wiki/Starlingx/Meetings#0615am_PDT_.2F_1415_UTC_-_Networking_Team_Call_.28Bi-weekly.29 14:25:47 <amotoki> thanks 14:25:47 <mlavalle> it's a high bandwidth meeting in zoom 14:25:59 <amotoki> I still need to watch zoom log.. 14:26:35 <mlavalle> cool 14:26:45 <mlavalle> #topic Community goals 14:28:34 <njohnston> For python3 looking at the stadium jobs I plan on getting back to that once the stadium tempest plugin transition is done 14:28:50 <mlavalle> thanks njohnston 14:29:03 <njohnston> I haven't followed the ML discussions; are the community goals for T set? 14:29:16 <mlavalle> there was also an update in the ML on community goals for Train 14:29:18 <mlavalle> http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004517.html 14:29:30 <mlavalle> njohnston: you read my mind ;-) 14:30:09 <amotoki> regarding the community goals, we've done the WSGI goal, but we haven't switched to neutron-api with WSGI by default. we can make it as default in Train. 14:30:53 <mlavalle> so it seems the community is talking about docs in PDF and IPv6 support for Train 14:30:53 <slaweq> amotoki: we should IMO first promote wsgi based ci jobs to be working in check and gate queues 14:31:04 <njohnston> Isn't WSGI by default a deployer decision that would be done in TripleO or something like that? 14:31:10 <amotoki> slaweq: totally agree 14:31:19 <njohnston> slaweq++ 14:31:35 <slaweq> for now it is only in experimental queue 14:31:46 <amotoki> neutron is the only project which hasn't switched it to WSGI in devstack 14:32:03 <mlavalle> yeah, I think we should switch it 14:32:08 <amotoki> it would be a good follow-up :) 14:32:15 <boden> sorry I just joined, but are we expecting any hits to plugin projects as part of this? 14:32:44 <mlavalle> boden: just in the initial conversation 14:32:54 <mlavalle> nothing is imminent yet 14:32:55 <bcafarel> sounds like a great goal for neutron train 14:33:09 <amotoki> eventlet dependencies might affect plugin projects. we can validate the impact in train 14:33:38 <boden> ack IMO it would be nice to give plugin teams a heads up so we can make sure the transisiton is smooth 14:34:04 <mlavalle> boden: good feedback. Thanks! 14:34:33 <mlavalle> we can even talk about it in Denver, while boden and other representatives of out of tree plugins are present 14:34:38 <mlavalle> is that fair? 14:34:46 <slaweq> mlavalle++ 14:34:53 <amotoki> +1 14:35:02 <boden> +1 14:35:05 <mlavalle> boden: do you want to add the topic to the etherpad? 14:35:18 <boden> mlavalle sure 14:35:31 <mlavalle> cool 14:35:38 <mlavalle> moving on 14:35:43 <mlavalle> #topic Bugs 14:36:05 <mlavalle> our deputy last week was bcafarel 14:36:12 <mlavalle> here's the report: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004696.html 14:37:02 <bcafarel> small update the in progress review for midonet failure was merged too (https://review.openstack.org/#/c/650599/) 14:37:52 <mlavalle> so all the critial and high priority bugs have merged fixes, right? 14:38:17 <bcafarel> mlavalle: indeed, all good for these sections! 14:39:56 <mlavalle> so the two medium priority bugs lack owners 14:41:02 <mlavalle> https://bugs.launchpad.net/neutron/+bug/1822591 14:41:03 <openstack> Launchpad bug 1822591 in neutron "neutron-keepalived-state-change doesnt reap zombies if rootwrap-daemon is used" [Medium,Confirmed] 14:41:28 <mlavalle> this one seems to be l3 ha dvr related 14:41:35 <mlavalle> adding the tag 14:42:43 <bcafarel> mlavalle: these zombies also happen on other agents (I tried with dhcp agent) 14:43:00 <mlavalle> bcafarel: ack 14:43:03 <bcafarel> apparently this behaviour appeared recently 14:43:05 <mlavalle> https://bugs.launchpad.net/neutron/+bug/1823297 14:43:06 <openstack> Launchpad bug 1823297 in neutron "create of segment range for vlan network type fails with error 500" [Low,Fix released] - Assigned to Slawek Kaplonski (slaweq) 14:43:20 <mlavalle> I approved the fix for this one yesterday 14:43:25 <mlavalle> thanks slaweq 14:43:33 <slaweq> this one was easy :) 14:43:46 <mlavalle> bcafarel: anything else you wnat to highlight? 14:44:26 <liuyulong> https://review.openstack.org/#/q/topic:bug/1811352+(status:open+OR+status:merged), I started the port forwarding OSC patches. 14:44:34 <bcafarel> just a general reminder (I had forgotten), os-ken is in the list of projects using storyboard :) 14:44:44 <liuyulong> https://bugs.launchpad.net/neutron/+bug/1811352 14:44:45 <openstack> Launchpad bug 1811352 in neutron "[RFE] Include neutron CLI floatingip port-forwarding support" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889) 14:44:59 <mlavalle> liuyulong: Thanks! 14:45:02 <liuyulong> We've been missing this for too long. 14:45:07 <bcafarel> so remember to redirect reporters there if you see open launchad bugs (thanks slaweq for reminding me) 14:45:23 <mlavalle> bcafarel: thanks for the reminder 14:45:29 <haleyb> liuyulong: i am reviewing the osc change, will have comments soon 14:45:42 <mlavalle> the deputy for this week is slaweq 14:45:45 <liuyulong> haleyb, cool 14:45:59 <mlavalle> and next week it will be hongbin 14:46:27 <slaweq> ok 14:46:32 <mlavalle> I want to point out that this week we lost a member of the bugs deputy rotation 14:46:45 <mlavalle> so I adjusted the schedule last night 14:46:46 <slaweq> I already started it this week :) 14:47:12 <bcafarel> ah that's why I saw your name on recent bugs this week :) 14:47:29 <slaweq> bcafarel: yep :) 14:47:43 <mlavalle> so for most of you, your duty week is going to be one week earlier than originally schedule 14:47:58 <mlavalle> so pleae take a look and reconfirm your duty week 14:48:20 <mlavalle> #topic neutron-lib 14:48:32 <mlavalle> boden: you are up 14:48:34 <boden> hi 14:49:14 <boden> so for the most part I think we are waiting for Stein to officially go out the door before doing too much 14:49:32 <boden> once it does IMO it'd be nice to cut a new neutron-lib as there are some patches to consume 14:49:45 <boden> also I will refresh a number of consumption patches I've been holding off on 14:49:54 <mlavalle> boden: let's plan to do that next week 14:50:02 <boden> ok 14:50:06 <boden> and that's about it 14:50:12 <mlavalle> cool 14:50:16 <mlavalle> thanks for the update 14:50:25 <mlavalle> #topic On demand agenda 14:51:01 <mlavalle> Back in January, we sent this message to the ML: http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001383.html 14:51:54 <mlavalle> smcginnis in the release team wanted to clarify that: "A stable branch enters extended maintenance after 18 months of initial release. It is not up to the project team to decide that" 14:52:19 <slaweq> so we are "bit late" with Ocata :) 14:52:42 <bcafarel> we did the release mostly in time :) 14:52:46 <mlavalle> and actually that conversation with me reminded him of sending http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004594.html 14:53:17 <amotoki> I am not sure what "extended maintenance phase" means in general. 14:53:35 <bcafarel> https://review.openstack.org/#/c/650467/ will tag all last ocata releases as ocata-em (there will be another one soon for pike I suppose) 14:53:36 <amotoki> EM is a decision of each project team per document. 14:53:41 <mlavalle> bcafarel: yes, he agrees on that. we did a good job. he was just concerned with clarifyin the semantics 14:54:10 <mlavalle> amotoki: staying in EM is a decision of the project 14:54:37 <mlavalle> but we get to EM at the 18 months mark regardless 14:54:38 <amotoki> mlavalle: ah, I see. EM or EOL is up to the project. 14:54:45 <bcafarel> yep 14:54:51 <elod> hi, was eavesdropping so far :) for some detail about EM: https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html#end-of-life 14:55:17 <elod> this is the resolution about Extended Maintenance from last year 14:55:57 <amotoki> we seem to miss tagging on ocata in time. we need to tag last pike stable releases in time. 14:56:13 <mlavalle> we can maintain a stable branch in EM as long as we are willing to actively work on it 14:56:28 <elod> also, smcginnis created a general patch for ocata: https://review.openstack.org/#/c/650467/ 14:56:47 <mlavalle> but if nobody is working on it, then it is time to EOL 14:56:56 <mlavalle> does this make sense? 14:57:20 <njohnston> mlavalle: makes sense to me 14:57:21 <elod> yes, that's it 14:57:48 <bcafarel> that was my understanding (and yes makes sense) 14:58:09 * mlavalle had to be slapped twice by smcginnis befory getting this ;-) 14:58:23 <amotoki> one question from me is whether it is aware of plugin maintainers? 14:58:54 <smcginnis> Hah. There was a lot of confusion around it. ;) 14:58:56 <amotoki> around ocata EM, what we struggled is how we coordinate all stadium projects. 14:59:26 <mlavalle> in our case we should be careful in letting our eco-system know what is happening with stable branch 14:59:36 <mlavalle> a consequence of our plugin architecture 15:00:04 <mlavalle> ok guys, we ran out of time 15:00:09 <mlavalle> thanks for attending 15:00:12 <amotoki> plugin is not the only eco-system we ahve thohgh..... 15:00:23 <mlavalle> #endmeeting