21:00:12 <slaweq> #startmeeting networking
21:00:13 <openstack> Meeting started Mon Jan  6 21:00:12 2020 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:16 <openstack> The meeting name has been set to 'networking'
21:00:28 <slaweq> welcome back in 2020!
21:01:07 <haleyb> o/
21:01:38 <slaweq> hi haleyb, HNY!
21:02:02 <slaweq> lets wait few more minutes and check if any other people will join too
21:02:06 <haleyb> HNY to you as well!
21:02:50 <slaweq> thx
21:03:25 <haleyb> maybe everyone is still hungover from new years? :)
21:03:36 <slaweq> maybe :)
21:03:50 <slaweq> actually I'm still on PTO today
21:04:13 <slaweq> but it's my last evening and I wanted to slowly start work already
21:04:42 <njohnston> o/
21:04:48 <slaweq> hi njohnston :)
21:04:53 <slaweq> HNY to You!
21:05:06 <njohnston> HNY to you slaweq!  HNY to all!
21:08:31 <slaweq> I think that maybe mlavalle will also join soon :)
21:08:38 * mlavalle was distracted and is late to meeting
21:08:49 <slaweq> welcome mlavalle :)
21:08:52 <slaweq> HNY!
21:09:02 <mlavalle> sorry, was to ficused on what I was doing
21:09:11 <slaweq> np
21:09:13 <mlavalle> likewise
21:09:27 <slaweq> I don't have too much for today
21:09:39 <slaweq> lets start with the meeting
21:09:41 <slaweq> #topic Announcements
21:10:17 <slaweq> I have only one announcement for today
21:10:22 <slaweq> it's more like reminder
21:10:39 <slaweq> that we are still looking for new daddies for neutron-fwaas and vpnaas projects
21:10:45 <slaweq> I sent today reminder to ML also
21:11:24 <slaweq> if You have anyone interested in maintainig those projects, please ask them to reply to my emails or contact with me directly
21:12:14 <slaweq> any other announcements from the team?
21:12:35 <mlavalle> none from me
21:13:04 <slaweq> ok, so lets move on than
21:13:10 <slaweq> #topic Blueprints
21:13:17 <slaweq> list updated for Ussuri-2 is here https://launchpad.net/neutron/+milestone/ussuri-2
21:13:24 <slaweq> any updates about any of them?
21:13:39 <slaweq> I don't have any updates for today but maybe You have some
21:14:06 <mlavalle> I've been working on tagging ports during bulk creation
21:14:47 <mlavalle> Here's the neutron-lib part: https://review.opendev.org/#/c/700754/
21:14:54 <mlavalle> which seems good to go
21:15:07 <mlavalle> Yes, I'll update the api-ref in a follow up patch
21:15:14 * njohnston will take a look at that
21:15:40 <slaweq> mlavalle: thx, I though that :)
21:16:12 <mlavalle> and this is the Neutron side: https://review.opendev.org/#/c/700755/
21:16:26 <mlavalle> amotoki left a comment in the patch
21:16:37 <mlavalle> so I want to clarify here
21:17:23 <mlavalle> this work is being done so we help the kuryr guys to tag ports when they are being created on bulk
21:17:33 <mlavalle> and that code resides in the ML2 plugin
21:17:36 <mlavalle> right?
21:18:09 <njohnston> the bulk port create code resides in ML2, yes
21:18:53 <mlavalle> specifically, here: https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/plugin.py#L1442
21:19:11 <njohnston> yep
21:19:15 <mlavalle> that is why I chose to implement the tagging as an ML2 extension driver
21:19:45 <slaweq> but one question, why we want to limit that only to bulk creation? in first comment in https://bugs.launchpad.net/neutron/+bug/1815933 You wrote that it should be allowed during creation request
21:19:45 <openstack> Launchpad bug 1815933 in neutron "[RFE] Allow bulk-tagging of resources" [Wishlist,Triaged] - Assigned to Miguel Lavalle (minsel)
21:19:49 <mlavalle> so it gets called here: https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/plugin.py#L1540-L1541
21:20:05 <slaweq> so IMO it should be allowed in same way for bulk and for single port creation, no?
21:20:20 <mlavalle> oh yeah, it will work both ways
21:20:33 <mlavalle> because the ML2 etension driver will be called on both cases
21:20:40 <slaweq> ok
21:21:08 <mlavalle> I just wanted to make sure that we all understand that our target is the code for bulk creation in ML2
21:21:15 <mlavalle> do we all agree on this?
21:21:18 <slaweq> so this makes sense to be ML2 extension as ML2 supports bulk port creation
21:21:23 <njohnston> +1
21:21:25 <mlavalle> yeap
21:21:49 <slaweq> and we will add new feature for bulk creation and (as side effect) for single port creation when ML2 is used
21:22:00 <mlavalle> that way we support the new functionality and we don't pollute the ML2 plugin code with tagging functions
21:22:17 <slaweq> +1
21:22:42 <mlavalle> and that explains this patch: https://review.opendev.org/#/c/700740/
21:22:59 <mlavalle> that's all I have to say about this blueprint
21:23:41 <slaweq> thx mlavalle for update and for working on this during this holiday season :)
21:24:00 <slaweq> any other updates about BPs?
21:24:10 <mlavalle> just the policy work
21:24:19 <mlavalle> I'll get to that after the tagging
21:24:57 <slaweq> ok
21:25:34 <slaweq> ok, lets move on than
21:25:36 <slaweq> #topic Community goals
21:25:54 <slaweq> I have only one short update about "Project Specific PTL and Contributor Documentation"
21:26:03 <slaweq> this is now accepted community goal
21:26:08 <slaweq> https://governance.openstack.org/tc/goals/proposed/project-ptl-and-contrib-docs.html
21:26:30 <mlavalle> that is also mine, right?
21:26:37 <slaweq> mlavalle: can we work on this together? as Your experience as PTL is much bigger than mine
21:26:44 <mlavalle> yeap
21:26:48 <slaweq> mlavalle: thx a lot
21:27:08 <slaweq> it was originally on You but I don't want to overload You so I will be happy to help with this one
21:27:36 <mlavalle> cool
21:28:31 <slaweq> so in next week or two I will check what we are missing in our existing docs and I will sync with You about it
21:28:33 <slaweq> ok for You?
21:29:37 <mlavalle> yes
21:30:20 <slaweq> ok
21:30:35 <slaweq> that's all about community goals from me for today
21:30:46 <slaweq> njohnston: any updates about dropping py27 ?
21:31:35 <njohnston> Nothing yet, just because I am still getting through email.  I think I saw some patches merge however.
21:31:45 <njohnston> I'll get an update ready for tomorrow's CI meeting
21:31:55 <slaweq> ok, thx
21:32:10 <slaweq> next topic than
21:32:12 <slaweq> #topic Bugs
21:32:25 <slaweq> we have few bug deputy reports since last meeting
21:32:42 <slaweq> rubasov was on bug deputy for week of 16th December: http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011751.html
21:32:50 <slaweq> mlavalle was on bug deputy for week of 23th December: http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011766.html
21:32:56 <slaweq> I was on bug deputy for week of 30th December: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011831.html
21:33:22 <slaweq> mine and mlavalle's weeks were pretty quiet
21:33:41 <mlavalle> yes
21:33:48 <slaweq> from rubasov's report most of the bugs are already fixed or in progress
21:33:52 <mlavalle> the quitest possible in my case
21:34:16 <slaweq> I only wanted to raise 3 L3 related bugs here:
21:34:23 <slaweq> https://bugs.launchpad.net/neutron/+bug/1856839
21:34:23 <openstack> Launchpad bug 1856839 in neutron "[L3] router processing time increase if there are large set ports" [Medium,In progress] - Assigned to LIU Yulong (dragon889)
21:34:24 <slaweq> https://bugs.launchpad.net/neutron/+bug/1857422
21:34:24 <openstack> Launchpad bug 1857422 in neutron "neutron-keepalived-state-change and keeplived cannot be cleanup for those routers which is deleted during l3-agent died" [Undecided,New]
21:34:26 <slaweq> https://bugs.launchpad.net/neutron/+bug/1858086
21:34:26 <openstack> Launchpad bug 1858086 in neutron "qrouter's local link route cannot be restored " [Medium,Confirmed]
21:35:25 <slaweq> for https://bugs.launchpad.net/neutron/+bug/1856839 fix is already proposed by liuyulong
21:35:25 <openstack> Launchpad bug 1856839 in neutron "[L3] router processing time increase if there are large set ports" [Medium,In progress] - Assigned to LIU Yulong (dragon889)
21:35:52 <slaweq> but if You will have some time, please check proposed patch
21:36:13 <slaweq> IMO it's not new RFE but rather something like performance improvement, at least from bug description
21:36:19 <slaweq> I didn't check proposed patch yet
21:37:21 <slaweq> second one, https://bugs.launchpad.net/neutron/+bug/1857422 - it seems for me like real bug but I agree with mlavalle that from reproduce steps it may be something more like "theoretical" problem rather than something really important on production environments
21:37:21 <openstack> Launchpad bug 1857422 in neutron "neutron-keepalived-state-change and keeplived cannot be cleanup for those routers which is deleted during l3-agent died" [Undecided,New]
21:38:01 <slaweq> but I think that L3 subteam could take a look at it also
21:38:22 <slaweq> and the last one https://bugs.launchpad.net/neutron/+bug/1858086 - I confirmed it on my devstack
21:38:22 <openstack> Launchpad bug 1858086 in neutron "qrouter's local link route cannot be restored " [Medium,Confirmed]
21:38:56 <slaweq> but I'm not sure if I will have time to work on it soon so if there is any volunteer who wants to fix it, please take care of it :)
21:39:34 <slaweq> that's all from my about bugs
21:39:43 <slaweq> any other bugs You want to discuss today?
21:40:28 <slaweq> if not, lets move on
21:40:42 <slaweq> bug deputy this week is hongbin and he is already aware of it
21:40:51 <slaweq> next week our bug deputy will be haleyb
21:41:08 <slaweq> next topic
21:41:20 <slaweq> #topic performance subteam update
21:41:27 <slaweq> mlavalle You're up :)
21:41:39 <mlavalle> I didn't do much here
21:42:13 <mlavalle> I was really trying to make as much progress as possible with the tagging stuff
21:42:31 <mlavalle> so let's wait for the next Monday meeting
21:42:39 <slaweq> ok
21:42:44 <slaweq> one question mlavalle
21:42:58 <slaweq> some time ago there was email about Neutron API performance: http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011358.html
21:43:19 <slaweq> did author of this thread contacted with You maybe?
21:43:53 <mlavalle> No he didn't
21:44:04 <mlavalle> I'll shoot him an email tomorrow morning
21:44:13 <slaweq> great, thx
21:44:24 <slaweq> ok, so lets move on than
21:44:28 <slaweq> #topic docs
21:44:53 <slaweq> today there was email from Large scale SIG: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011820.html
21:45:20 <slaweq> it's about identyfing config options which may have big impact on large scale deployments
21:45:38 <slaweq> I opened bug https://bugs.launchpad.net/neutron/+bug/1858419 to track progress of this on Neutron's side
21:45:38 <openstack> Launchpad bug 1858419 in neutron "Docs needed for tunables at large scale" [Undecided,Confirmed]
21:46:02 <slaweq> I will try to reach out to liuyulong tomorrow morning as he has a lot of experience with running Neutron on scale
21:46:22 <njohnston> good idea
21:46:28 <slaweq> but if You have any ideas about what options can be markes as such, please also write comments or propose patches for it
21:47:38 <slaweq> ok, and that's all from my side for today
21:47:46 <slaweq> #topic On Demand Agenda
21:47:53 <slaweq> anything else You want to discuss today?
21:48:36 <mlavalle> not from me
21:49:10 <njohnston> I don't have anything, just happy to be back :-)
21:49:21 <slaweq> njohnston: yeah, that's great for me too :)
21:49:38 <slaweq> I was already tired a bit on PTO ;)
21:49:51 <slaweq> ok, thx for attending first meeting in 2020
21:50:00 <slaweq> see You online and have a great week
21:50:02 <slaweq> o/
21:50:04 <haleyb> o/
21:50:06 <slaweq> #endmeeting