14:00:12 <mlavalle> #startmeeting networking
14:00:12 <openstack> Meeting started Tue Dec 18 14:00:12 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:15 <openstack> The meeting name has been set to 'networking'
14:00:49 <lajoskatona> o/
14:00:59 <amotoki> hi
14:01:03 <haleyb> hi
14:01:08 <rubasov> o/
14:01:12 <bcafarel> hello
14:01:14 <slaweq> hi
14:01:18 <liuyulong_> hi
14:01:22 <boden> howdy
14:01:25 <mlavalle> hello everybody!
14:01:37 <mlavalle> welcome to our last meeting of the year!
14:01:50 <mlavalle> #topic Announcements
14:02:41 <mlavalle> First a reminder that our Stein 2 milestone will be on January 7 - 11
14:03:11 <mlavalle> Second there is a proposal by amotoki to release Neutron "Beta"
14:03:46 <mlavalle> please remember that in the new model, we don't release necessarily code in the milestone weeks
14:04:05 <mlavalle> and ecently we have landed some important stuff:
14:04:17 <mlavalle> ryu -> os-ken switch
14:04:28 <mlavalle> policy-in-code support framework
14:04:50 <mlavalle> upgrade-checker framework (which landed or is about to)
14:05:01 <mlavalle> amotoki: do you want to add something
14:05:03 <mlavalle> ?
14:05:34 <amotoki> I hope I covered all imporant things
14:05:55 <amotoki> nothing I need to add
14:06:10 <mlavalle> any objections from anybody?
14:06:31 <bcafarel> none, that's a great "progress" list to end the year!
14:06:51 <amotoki> ah, one thing. note that this is about 'neutron' itself.
14:07:03 <mlavalle> amotoki: good ctach!
14:07:11 <amotoki> if you need a beta release for stadium projects, it can be released separately.
14:08:13 <mlavalle> ok, so lets wait for https://review.openstack.org/#/c/615196/ to land and then we can go ahead with the release, agree?
14:08:24 <slaweq> +1
14:08:25 <amotoki> +1
14:09:01 <mlavalle> cool
14:09:48 <mlavalle> The other thing we wanted to discuss today (outside our normal topics) is Ocata branch to be put under EM (Extended Maintenance)
14:10:01 <mlavalle> bcafarel: do you want to add to this?
14:10:21 <bcafarel> just some quick context
14:10:29 <bcafarel> #link https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance
14:10:50 <bcafarel> for those scared, extended maintenance is not end-of-life yet :)
14:11:29 <bcafarel> we will still accept patches and get them in as time permits (I see it as "best effort" support)
14:11:35 <mlavalle> correct, we can still merge fixes when they are deemed necessary
14:11:54 <mlavalle> and bandwidth allows
14:11:55 <amotoki> it means the upsream developer team does not take care of such branches much and no new release is coming, while we accept backports
14:12:23 <amotoki> someone interested in maintaining some branch can raise their hand
14:12:50 <mlavalle> that's an excellent point amotoki
14:13:07 <mlavalle> any objections from the team to take this step?
14:13:44 <slaweq> it's fine for me
14:14:50 <mlavalle> ok, we will move ahead with this.
14:15:01 <mlavalle> bcafarel: do you have anything you need for this?
14:15:18 <mlavalle> everything^^^
14:15:24 <bcafarel> :)
14:15:39 <amotoki> it might be better to ask maintainers of driver projects like netwokring-ovn
14:16:31 <mlavalle> amotoki: message to the ML?
14:16:37 <bcafarel> one question remaining, as said we plan to do a final ocata release (before tagging), should we do it for neutron only or include stadium? (stadium projects have mostly test fixes, from amotoki's findings)
14:16:55 <amotoki> mlavalle: yes, I think so. as they usually cut their release separately
14:17:15 <bcafarel> ack, a heads-up warning message sounds like a good idea
14:17:31 <mlavalle> bcafarel: so let's send a message to the ML and lets ask this question there. makes sense?
14:17:49 <bcafarel> mlavalle: good for me :)
14:18:06 <mlavalle> ok, I think we can move on then....
14:18:08 <amotoki> sounds good
14:18:40 <mlavalle> #topic Blueprints
14:19:43 <mlavalle> Does anybody have updates on blueprints?
14:20:02 <tidwellr> mlavalle: I do
14:20:52 <bcafarel> feedback on http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000796.html I guess?
14:21:44 <tidwellr> bcafarel: yes, I'm not sure if any of that made sense :)
14:22:22 <mlavalle> tidwellr: I need to go over that slowly and carefully. I'll provide feedback today or tomorrow. Does that help?
14:23:01 <tidwellr> mlavalle: that would be great, I've got subnet onboard in a pretty good spot now, the last outstanding bit is what to do with what I think is a mistake in the API definition
14:23:36 <tidwellr> I'm unclear with how to handle this since we merged the API definition so long ago
14:23:59 <mlavalle> ok, let's do that. I encourage other to take a look and lend a helping hand
14:24:01 <slaweq> tidwellr: sorry, I was reading Your email and I forgot to answer to it
14:24:19 * bcafarel notes to finish his reply email to that too
14:24:20 <slaweq> tidwellr: I will do it tomorrow morning or today evening
14:24:40 <tidwellr> I've been meaning to just push a review up to neutron-lib that removes the troublesome bits from the definition just to jump-start a discussion
14:25:00 <tidwellr> thanks everyone, that's all I had
14:25:26 <mlavalle> tidwellr: if you have the patch ready, go ahead and push it. it will provide more context to the email
14:25:45 <tidwellr> I'll push that up today
14:26:20 <mlavalle> great
14:27:30 <mlavalle> yamamoto: you around?
14:28:11 <mlavalle> maybe not
14:28:14 <mlavalle> let's move on
14:28:23 <mlavalle> #topic neutron-lib
14:28:51 <mlavalle> Let's talk about neutron-lib out of our normal order, so boden can take care of his paternal duties
14:29:03 <boden> :) thanks
14:29:35 <boden> just wanted to mention that I've recently updated the neutron meeting wiki for neutron-lib https://wiki.openstack.org/wiki/Network/Meetings#Neutron-lib.2C_planned_refactoring_and_other_impacts
14:30:02 <boden> there's a section titled "PATCHES THAT NEED REVIEWS"... if folks get bored and want to help with reviews, that's probably the best place to start
14:30:23 <mlavalle> ahh, very good
14:30:28 <boden> any questions/comments on that?
14:30:38 <mlavalle> no, I think this will be helpful
14:30:49 <boden> ok well 1 last thing that has nothing to do with neutron-lib
14:30:53 <mlavalle> I will go over that section between today and tomorrow
14:31:17 <boden> I threw out a patch to test the lower-constraints with python 3.6 https://review.openstack.org/#/c/625922/
14:31:26 <boden> just to make sure things won't break... details in the commit message
14:31:49 <boden> and that's it from me unless there are comments/questions
14:32:10 <mlavalle> boden: thanks for that patch!
14:32:28 <boden> mlavalle np... it did break some other projects for the record :)
14:32:43 <mlavalle> let's keep an eye on it
14:32:54 <mlavalle> ok, let's move on
14:33:16 <mlavalle> #topic Community goals
14:33:57 <mlavalle> First of all, I want to congratulate and THANK amotoki, slaweq and njohnston for their hard work on this goals
14:34:38 <mlavalle> as mentioned before, https://review.openstack.org/#/c/615196 seems that will merge soon
14:35:03 <mlavalle> and with that we can claim victory with upgrade checks
14:35:19 <slaweq> yes :)
14:35:21 <mlavalle> and with policy in code, we are set, right amotoki?
14:35:31 <amotoki> re: policy-in-code, thanks for your review on the first basic work in neutron.
14:35:48 <amotoki> in the neutron repo side, I plan to send several clean up patches (including docs)
14:36:14 <amotoki> I also sent a mail on the progress to the list http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001019.html
14:36:44 <amotoki> I hope individual project teams review and test pending policy-in-code patches
14:37:00 <mlavalle> perfect
14:37:34 <amotoki> that's all from me
14:38:16 <mlavalle> Thanks for your hard work
14:38:22 <mlavalle> let's move on
14:38:27 <mlavalle> #topic Bugs
14:38:44 <mlavalle> The bugs deputy last week was bcafarel
14:39:02 <mlavalle> and his report is here: http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001022.html
14:39:33 <bcafarel> indeed, relatively quiet week, just wanted to highlight a few ones here
14:39:48 <mlavalle> go ahead please
14:40:15 <bcafarel> https://bugs.launchpad.net/neutron/+bug/1808731 - Needs the method to
14:40:17 <openstack> Launchpad bug 1808731 in neutron "[RFE] Needs the method to stop metadata proxy" [Undecided,New] - Assigned to cheng li (chengli3)
14:40:17 <bcafarel> stop metadata proxy I left as undecided, there is some discussion already there (slaweq, haleyb, etc)
14:41:04 <slaweq> I marked this one as RFE to discuss it on drivers meeting
14:41:29 <bcafarel> ack, good idea
14:41:37 <bcafarel> https://bugs.launchpad.net/neutron/+bug/1808541 is about some race condition with ovs flows, it would benefit from some expert eyes
14:41:38 <openstack> Launchpad bug 1808541 in neutron "Openflow entries are not totally removed for stopped VM" [High,New]
14:41:46 <mlavalle> I see it alreade has the rfe tag. we will capture it in the drivers agenda
14:42:17 <bcafarel> other high bugs have patches in review
14:43:16 <bcafarel> and one gate failure in nova https://bugs.launchpad.net/neutron/+bug/1808171
14:43:17 <openstack> Launchpad bug 1808171 in neutron "TaggedBootDevicesTest.test_tagged_boot_devices intermittently fails waiting for network-vif-plugged event which neutron does not send" [Medium,Confirmed]
14:43:40 <mlavalle> I don't see comments to the one on OVS flows. I'll look at it
14:44:06 <bcafarel> mlavalle: thanks
14:44:20 <bcafarel> other bugs are in good shape or progressing (or tagged as rfe)
14:45:11 <mlavalle> thanks for the good report bcafarel :-)
14:45:49 <liuyulong> That network-vif-plugged event bug is related to this, IMO, https://bugs.launchpad.net/neutron/+bug/1760047
14:45:50 <openstack> Launchpad bug 1760047 in neutron "some ports does not become ACTIVE during provisioning" [High,Triaged]
14:45:56 <mlavalle> so this week our deputy will be pasuder
14:46:54 <mlavalle> the following week will be hongbin
14:46:59 <liuyulong> And this: https://bugs.launchpad.net/neutron/+bug/1778616, we recently still meet such issue during a VM starting storm.
14:47:00 <openstack> Launchpad bug 1760047 in neutron "duplicate for #1778616 some ports does not become ACTIVE during provisioning" [High,Triaged]
14:47:20 <mlavalle> and the one after that will be slaweq
14:47:34 <mlavalle> liuyulong: thanks for pointing this out
14:47:44 <slaweq> yep, I will be first one in 2019 :)
14:48:05 <bcafarel> happy new year of bugs to slaweq :)
14:48:08 <mlavalle> liuyulong: should we mark some of those dulicated?
14:48:50 <liuyulong> 1778616 has been set duplicated.
14:48:59 <mlavalle> perfect, thanks
14:49:14 <mlavalle> ok, moving on
14:49:24 <mlavalle> #topic os-ken
14:49:49 <mlavalle> hongbin couldn't make it to the meeting today
14:49:58 <mlavalle> but he gave me his update yesterday
14:50:39 <mlavalle> First, we merged the swicth to os-ken in neutron last week: https://review.openstack.org/#/c/607008/
14:50:56 <mlavalle> Great job, hongbin
14:52:15 <mlavalle> and second there is a corresponding patch in neutron-dynamic-routing: https://review.openstack.org/#/c/608357/
14:52:39 <mlavalle> tidwellr: would you take a look?
14:52:49 <tidwellr> that's my patch :)
14:53:06 <mlavalle> ah ok?
14:53:16 <mlavalle> I will review it then
14:53:33 <mlavalle> that's it for os-ken
14:53:42 <mlavalle> #topic On demand agenda
14:54:01 <mlavalle> bcafarel: we covered all that you added to this section, right?
14:54:24 <amotoki> I added it but forgot to add my name :(
14:54:38 <amotoki> we already covered it
14:54:40 <bcafarel> :)
14:54:47 <mlavalle> perfect
14:54:53 <bcafarel> yes everything coverted
14:54:59 <mlavalle> anything else we should discuss today?
14:55:52 <mlavalle> ok, please keep in mind that we will skip the next two meetings
14:55:58 <amotoki> will the next meeting at Jan 1?
14:56:05 <mlavalle> we will resume on January 7th
14:56:12 <amotoki> ah...
14:56:24 <amotoki> I see my calendar wth JST :)
14:56:56 <mlavalle> I wish everybody great Holidays
14:57:06 <mlavalle> and a very succesful 2019
14:57:13 <slaweq> thx, You too mlavalle :)
14:57:24 <mlavalle> and I also thank everybody for your contributions during 2018
14:57:34 <mlavalle> let's go have some fun \o/
14:57:49 <mlavalle> #endmeeting