14:00:42 <jlibosva> #startmeeting networking
14:00:43 <openstack> Meeting started Tue Jan  2 14:00:42 2018 UTC and is due to finish in 60 minutes.  The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:46 <openstack> The meeting name has been set to 'networking'
14:00:51 <mlavalle> o/
14:00:52 <jlibosva> Happy New Year everyone
14:00:52 <slaweq> hi
14:01:00 <slaweq> Happy New Year
14:01:01 <bcafarel> o/
14:01:06 <bcafarel> happy new year!
14:01:06 <annp> happy new year
14:01:12 <jlibosva> #topic Announcements
14:01:48 <jlibosva> We're moving fast towards the last milestone of this release cycle - the m3 should be in the week of January 22
14:02:39 <jlibosva> That gives us effectively 3 weeks to finish our work on blueprints, more about that in its own topic
14:02:46 <cleong> hi
14:02:50 <mlavalle> yeap
14:03:05 <jlibosva> next one: don't forget to register for the upcoming PTG in Dublin
14:03:30 <jlibosva> I don't have any other announcements, mlavalle do you have any?
14:03:43 <mlavalle> no, you covered them all
14:04:10 <jlibosva> alrighty :)
14:04:12 <jlibosva> #topic Blueprints
14:04:17 <jlibosva> #link https://launchpad.net/neutron/+milestone/queens-3
14:05:16 <jlibosva> we have some scheduled to be finished in this milestone
14:05:31 <jlibosva> does anybody have anything to share with the team regarding the blueprints?
14:05:45 <mlavalle> just to mention that with https://blueprints.launchpad.net/neutron/+spec/live-migration-portbinding
14:05:48 <slaweq> I think that "Strict minimum bandwidth support (scheduling aware)" will not be done for sure now
14:05:59 <mlavalle> I made great progress last week
14:06:09 <mlavalle> it was a quite week so I was able to focus
14:06:39 <annp> regarding to logging, thank slaweq for your great reviewing
14:06:46 <mlavalle> the plugin work is compplete (there are a couple of nits I need to fic)
14:07:31 <mlavalle> annp: do you have links to the remaining patchsets?
14:07:35 <mlavalle> or are we done?
14:07:42 <jlibosva> mlavalle: should we move out from Queens the Strict minimum bandwidth support as slaweq said so we can focus on other things?
14:07:51 <slaweq> annp: You welcome :)
14:07:56 <mlavalle> jlibosva: yes
14:08:05 <mlavalle> I can take care of that
14:08:24 <slaweq> mlavalle: jlibosva: thx
14:08:52 <jlibosva> as per logging, seems like remaining patches to land are here: https://review.openstack.org/#/q/topic:bug/1468366+(status:open+OR+status:open)
14:08:54 <mlavalle> done
14:09:36 <mlavalle> Looks doable
14:09:37 <annp> jlibosva: thanks. :)
14:10:37 <mlavalle> This one is done on Neutron side: https://blueprints.launchpad.net/neutron/+spec/floating-ip-rate-limit
14:11:01 <mlavalle> the docs looked good last time I looked (about 10 days ago)
14:11:11 <mlavalle> there is a tempest test and the client remaining
14:11:43 <slaweq> docs patch is marked as WIP now
14:11:49 <slaweq> https://review.openstack.org/#/c/526033/
14:12:00 <mlavalle> it is because of the client patch
14:12:06 <slaweq> yep
14:12:26 <mlavalle> but the patch itself looked good to me, as I said
14:12:38 <amotoki> I will take care of it once I am back from new year holidays
14:12:53 <mlavalle> amotoki: thanks :-)
14:12:54 <amotoki> about the client patch
14:13:55 <mlavalle> and I will follow up with FWaaS today on https://blueprints.launchpad.net/neutron/+spec/fwaas-api-2.0
14:14:35 <mlavalle> amotoki: you off the entire week, right?
14:15:02 <amotoki> mlavalle: I will be back on Friday
14:15:13 <mlavalle> amotoki: cool, enjoy!
14:15:18 <amotoki> thanks
14:16:00 <jlibosva> any other blueprint worth awareness?
14:16:06 <annp> regarding to fwaas, there is remain my patch https://review.openstack.org/#/c/515368/ :)
14:16:09 <mlavalle> not from me :-)
14:16:24 <jlibosva> annp: thanks :)
14:16:47 <annp> jlibosva: please go ahead
14:16:52 <jlibosva> #topic Starter Approved RFEs
14:16:56 <annp> jlibosva: thanks
14:17:23 <jlibosva> we still have the one from last meeting that is looking for an owner
14:17:25 <jlibosva> #link https://bugs.launchpad.net/neutron/+bug/1653932
14:17:27 <openstack> Launchpad bug 1653932 in neutron "[rfe] network router:external field not exported" [Wishlist,Triaged]
14:17:36 <mlavalle> yeap, still orphan :-(
14:18:20 <jlibosva> hopefully for Rocky it will find its owner ;)
14:18:22 <jlibosva> #topic Bugs
14:18:46 <jlibosva> as we didn't have meeting last week, let's start with bug deputy report from the week before the holidays
14:19:39 <jlibosva> Lujin left a bug report here
14:19:39 <mlavalle> jlibosva: no, yamamoto sent update
14:19:42 <jlibosva> #link http://lists.openstack.org/pipermail/openstack-dev/2017-December/125853.html
14:19:57 <mlavalle> I posted it in the meeting agenda
14:20:22 <mlavalle> but we can start with Lujin's report for sure :-)
14:20:39 <jlibosva> yeah :) I thought we could do it chronologically and then continue as usual
14:20:48 <mlavalle> got it :-)
14:22:02 <jlibosva> so from the report, I think we should highlight the critical one: https://bugs.launchpad.net/neutron/+bug/1738768
14:22:02 <openstack> Launchpad bug 1738768 in tripleo "Dataplane downtime when containers are stopped/restarted" [High,Triaged]
14:22:05 <jlibosva> #link https://bugs.launchpad.net/neutron/+bug/1738768
14:22:09 <mlavalle> yes
14:22:26 <jlibosva> it has no assignee
14:23:55 <jlibosva> the summary is that when using containerized l3 agent, stopping container causes fips to stop working because of namespaces being nested in container
14:25:00 <jlibosva> other than that, it seems like other bugs are just ordinary bugs and some are already handled
14:26:07 <jlibosva> does anybody have cycles to work on the bug?
14:26:52 <haleyb> jlibosva: i can look, i know we had an internal one as well
14:26:59 <jlibosva> haleyb: cool :) thanks
14:27:08 <haleyb> if i remember what l3 is :)
14:27:17 <jlibosva> let's jump to yamamoto's report then
14:27:19 <jlibosva> #link http://lists.openstack.org/pipermail/openstack-dev/2018-January/125912.html
14:27:38 <jlibosva> yamamoto couldn't attend meeting, I hope he'll get better soon :)
14:28:06 <jlibosva> there is one similar bug opened to the containerized one: https://bugs.launchpad.net/neutron/+bug/1740450
14:28:06 <openstack> Launchpad bug 1740450 in neutron "Restarting l3 agent results in lost of centralized fip in snat ns" [Undecided,New]
14:29:04 <haleyb> i was asked by yamamoto to triage that but have not yet
14:29:30 <jlibosva> looks like haleyb is gonna solve all l3 related issues :) good
14:29:57 <haleyb> that's what they pay me for :)
14:30:06 <jlibosva> the bug deputy for this week is mlavalle, right?
14:30:11 <mlavalle> yes
14:30:36 <jlibosva> alright
14:30:43 <jlibosva> I think we can move to the next topic then
14:30:58 <jlibosva> #topic Docs
14:31:06 <jlibosva> I don't see boden around
14:31:47 <jlibosva> does anybody have anything related to docs?
14:32:19 <jlibosva> then we shall move on
14:32:21 <jlibosva> #topic OSC
14:32:25 <jlibosva> amotoki: hi, do you have any updates re OSC?
14:32:44 <amotoki> I have no updates due to holidays
14:33:04 <mlavalle> have fun!
14:33:10 <amotoki> does anyone have some patches to raise?
14:33:35 <jlibosva> right, holidays :) I like that
14:33:36 <slaweq> amotoki: I have one
14:33:37 <slaweq> https://review.openstack.org/#/c/515401/
14:33:52 <slaweq> amotoki: it could be good if You could look at it
14:34:09 <amotoki> slaweq: thanks. will look at it
14:34:15 <slaweq> amotoki: thx a lot
14:34:43 <mlavalle> amotoki: https://review.openstack.org/#/c/517845/6
14:34:51 <mlavalle> that's the one for FIP QoS
14:35:08 <amotoki> yeah, that's what we discussed :)
14:35:39 <amotoki> thanks all for the list :)
14:36:44 <jlibosva> thanks :) moving on
14:36:46 <jlibosva> #topic neutron-lib
14:36:59 <jlibosva> does anybody have anything related to neutron-lib?
14:37:17 <amotoki> one thing on milestone 3
14:37:31 <amotoki> we have the deadline one week before Queens-3
14:37:38 <amotoki> it is worth aware of it
14:37:54 <jlibosva> aha, thanks, it is
14:38:16 <slaweq> I just want to ask You to check https://review.openstack.org/#/c/526181/1/neutron_lib/api/definitions/tag_ext.py and clarify policy for removing deprecated extensions
14:38:16 <mlavalle> I also want to mention that I worked on https://review.openstack.org/#/c/529661/
14:38:47 <mlavalle> This will allow us to add more people with W+ power in neutron lib
14:39:03 <mlavalle> our hands were tied with the previous setup
14:39:54 <jlibosva> nice
14:39:55 <mlavalle> as soon as it merges I will give W+ power to boden and some additional neutron cores
14:40:17 <mlavalle> and that will allow us to take care of the review backlog there
14:41:12 <jlibosva> I guess we can jump to open discussion unless there are no other comments related to neutron-lib
14:41:15 <jlibosva> #topic Open Agenda
14:41:37 <jlibosva> I don't see any topic on the wiki page. Does anybody have a topic to discuss here?
14:41:44 <chandankumar> Hello Do we have any updates on tempest plugin split for stadium projects
14:41:48 <chandankumar> ?
14:42:02 <chandankumar> Are we going to merge it in the neutron tempest plugin?
14:42:31 <mlavalle> chandankumar: we had a conversation in neutron drivers meeting last time
14:42:38 <mlavalle> let's look at the logs
14:42:43 <mlavalle> offline
14:42:47 <chandankumar> sure
14:43:10 <chandankumar> mlavalle: Thanks :-)
14:43:10 <bcafarel> oh nice I probably missed that one
14:44:00 <jlibosva> mlavalle: perhaps it could be announced on the ML? I remember bcafarel started a thread
14:44:06 <jlibosva> http://lists.openstack.org/pipermail/openstack-dev/2017-October/123814.html
14:44:15 <mlavalle> chandankumar, bcafarel: http://eavesdrop.openstack.org/meetings/neutron_drivers/2017/neutron_drivers.2017-12-22-14.00.log.html#l-20
14:44:25 <mlavalle> jlibosva: yes, that's a good point
14:44:41 <jlibosva> cool, thanks for the link :)
14:44:49 <amotoki> i thought the same feeling as jlibosva. sounds a good idea
14:44:52 <mlavalle> with the holidays I didn't take care of that
14:45:07 <mlavalle> but I'll take care of it
14:46:55 <jlibosva> so do I understand it correctly that who wants can propose tests to tempest-plugin or tests can be left in original repo containing the prod code?
14:47:10 <jlibosva> s/tempest-plugin/neutron-tempest-plugin/
14:47:22 <mlavalle> correct
14:47:32 <jlibosva> ok, thanks
14:47:43 <jlibosva> chandankumar: thanks for bringing this up
14:47:55 <mlavalle> we don't want to force anyone to take an approach
14:48:04 <mlavalle> and create more artificial work
14:48:16 <mlavalle> bcafarel, chandankumar: does that work for you?
14:48:29 <chandankumar> mlavalle: yup!
14:49:20 <bcafarel> mlavalle: yes, sounds pretty reasonable!
14:49:28 <mlavalle> perfect :-)
14:49:45 <jlibosva> we have 10 mins left :) any other topics to discuss?
14:50:39 <jlibosva> we can those minutes back then. thank everyone for coming
14:50:42 <jlibosva> #endmeeting