14:01:00 <ralonsoh> #startmeeting networking
14:01:00 <opendevmeet> Meeting started Tue Mar 21 14:01:00 2023 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:00 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:00 <opendevmeet> The meeting name has been set to 'networking'
14:01:01 <mlavalle> o/
14:01:02 <ralonsoh> hello all
14:01:05 <mtomaska> o/
14:01:09 <rubasov> o/
14:01:14 <obondarev> o/
14:01:26 <slaweq> o/
14:01:40 <ykarel> o/
14:01:52 <frickler> \o
14:01:53 <bcafarel> o/
14:02:05 <lajoskatona> o
14:02:06 <lajoskatona> o/
14:02:19 <ralonsoh> ok, I think we have quorum
14:02:34 <ralonsoh> #topic announcements
14:02:45 <ralonsoh> #link https://releases.openstack.org/antelope/schedule.html
14:02:55 <ralonsoh> and that's all folks!
14:02:59 <ralonsoh> R+0
14:03:06 <ralonsoh> this week is the release week
14:03:09 <ralonsoh> thank you all!
14:03:39 <ralonsoh> last week (thanks slaweq) we updated the RC candidate hashes for Neutron and ovn-octavia-provider
14:03:53 <ralonsoh> the other projects will keep the same as 2 weeks ago
14:04:10 <ralonsoh> and what is next?
14:04:13 <ralonsoh> #link https://etherpad.opendev.org/p/neutron-bobcat-ptg
14:04:36 <ralonsoh> we have a list of topics and some votes in the poll
14:04:39 <ralonsoh> #link https://doodle.com/meeting/organize/id/eZ83mmvb
14:04:47 <ralonsoh> ^^^ please if you want to vote, I'll close it today
14:05:04 <ralonsoh> and tomorrow I'll send (a bit late) the Neutron schedule
14:05:13 <elvira> o/
14:05:30 <ralonsoh> I think we'll have enough with 3 hours per day, from tuesday to friday
14:06:12 <ralonsoh> and according to the votes, we will probably use the 14 to 17 UTC time slots
14:06:19 <ralonsoh> ^^ what do you think?
14:06:32 <lajoskatona> fine, sounds good
14:06:43 <ralonsoh> (14UTC is now_
14:06:58 <ralonsoh> so we will start same as today
14:07:11 <frickler> will be 1h later in most of europe next week
14:07:43 <lajoskatona> yeah be careful with that :-)
14:07:56 <ralonsoh> "just this weekend..."
14:08:04 <ralonsoh> what a coincidence...
14:08:22 <ralonsoh> so let me re-write my sentence
14:08:31 <lajoskatona> again a PTG with jet-eg but without flight
14:08:36 <ralonsoh> the meeting will start at 13 UTC
14:08:54 <ralonsoh> (in other words, same as this meeting)
14:09:23 <ralonsoh> but I'll be more cautious when sending the schedule
14:09:31 <frickler> nope, this meeting starts at 14 UTC
14:09:54 <ralonsoh> I know
14:10:00 <ralonsoh> this meeting is UTC
14:10:07 <ralonsoh> I'm talking as a reference of today
14:10:13 <ralonsoh> at least not for US folks
14:10:15 <slaweq> lets just use UTC and nothing else :)
14:10:20 <ralonsoh> I'll send the mail with UTC references
14:10:25 <mtomaska> UTC ++
14:10:39 <slaweq> everyone will calculate it for their TZ :)
14:11:20 <ralonsoh> ok, any other missing bit in this topic?
14:11:45 <ralonsoh> ah yes
14:11:47 <ralonsoh> one sec
14:11:49 <ralonsoh> #link https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032523.html
14:12:18 <ralonsoh> Vancouver: I still don't know the traction of this community on this event
14:12:45 <ralonsoh> so I don't know if the Neutron community is going to celebrate any meeting/event/whatever
14:13:25 <ralonsoh> to be honest, this "abbreviated" PTG is driving me crazy#
14:13:53 <haleyb> fly halfway across the world for a short meeting for you :(
14:14:32 <frickler> just as if there's no climate crisis, no pandemic ...
14:14:44 <ralonsoh> so please fill https://etherpad.opendev.org/p/neutron-vancouver-2023 if you think we can have any meeting/discussion/topic
14:14:55 <ralonsoh> yes but we have next week PTG
14:15:13 <ralonsoh> and seeing the number of topics, it will be enough
14:15:51 <ralonsoh> I think I spend 60-70% of my time fixing bugs (some of them mine) and taking care of the CI
14:16:04 <lajoskatona> the big advantage would be to meet personally with the magic of it
14:16:21 <slaweq> lajoskatona++
14:16:26 <mlavalle> Defibirely there is value in that
14:16:28 <lajoskatona> but true it is expensive now from management perspective for sure
14:17:03 <ralonsoh> ok, I'll talk to Kendall to know how to proceed in this case
14:17:17 <lajoskatona> +1
14:17:37 <lajoskatona> I don't know others but we got "promise" to have some feedback on the trvel in 1 month
14:18:06 <lajoskatona> or latest in early May
14:18:36 <ralonsoh> ok, let's move to the next topic
14:18:40 <ralonsoh> #topic bugs
14:18:45 <ralonsoh> Last week haleyb was the deputy. This is the report: https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032825.html
14:19:01 <ralonsoh> we have some bugs still not assigned
14:19:08 <ralonsoh> #link https://bugs.launchpad.net/neutron/+bug/2011600
14:19:28 <haleyb> was not too busy a week for bugs, most were picked-up
14:19:57 <haleyb> ^^ was filed by ihar
14:20:16 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2012104
14:20:28 <ralonsoh> one sec
14:20:33 <ralonsoh> about the first one
14:20:54 <ralonsoh> I pushed a patch 2 months ago
14:20:55 <ralonsoh> https://review.opendev.org/c/openstack/neutron/+/868311
14:21:03 <ralonsoh> but seems that this is not enough
14:21:10 <ralonsoh> or at least this is not solving the issue
14:21:31 <ralonsoh> slaweq, have you seen this problem during the last month?
14:22:20 <slaweq> ralonsoh are You asking about https://bugs.launchpad.net/neutron/+bug/2011600 ?
14:22:25 <ralonsoh> yes
14:22:43 <ralonsoh> I didn't see that after the patch I sent 2 months ago
14:22:48 <slaweq> I didn't saw error like that recently
14:23:07 <slaweq> but it seems that ihrachys had it about 2 weeks ago
14:23:29 <ralonsoh> ok, let's move this to the CI meeting and keep an eye on this one. If we see it again, we'll need to find a better fix
14:23:55 <slaweq> ++
14:24:00 <ralonsoh> ok, next one
14:24:04 <ralonsoh> #link https://bugs.launchpad.net/neutron/+bug/2011800
14:24:08 <ralonsoh> I'll pick this one
14:24:16 <ralonsoh> I'm 120% responsible of it
14:24:44 <ralonsoh> I saw fnordahl sent a patch testing this feature better
14:24:51 <haleyb> +1
14:24:52 <ralonsoh> so it will be easier to fix and test it
14:24:59 <ralonsoh> thanks fnordahl
14:25:25 <ralonsoh> ok, next one
14:25:32 <ralonsoh> #link https://bugs.launchpad.net/neutron/+bug/2012104
14:26:12 <haleyb> ralonsoh: i was going to ask you to look at this since you fixed a related issue recently, did not know if there was a manual step required
14:26:32 <ralonsoh> that happens when you stop the ovn-controller not gracefully
14:26:44 <ralonsoh> and the chassis register is deleted but not the chassis_private
14:26:59 <ralonsoh> so, IMO (of course I need to check that), this is not a Neutron problem
14:27:11 <ralonsoh> but they need to manually cleanup the SB database
14:27:25 <ralonsoh> I'll pick this one to check what is actually happening
14:27:45 <haleyb> ack, they did ask if they had to manually fix SB
14:27:51 <lajoskatona> So perhaps some extra warning in the doc would be helpful to say this manual step
14:28:13 <ralonsoh> yeah, with the patch I sent Neutron doesn't raise an exception
14:28:25 <ralonsoh> but it is better to document what are the next steps
14:28:35 <lajoskatona> +1
14:28:38 <ralonsoh> but I need to read it in detail (I'm just speculating)
14:29:17 <ralonsoh> and last one was already attended but not assigned
14:29:21 <ralonsoh> #link https://bugs.launchpad.net/neutron/+bug/2012069
14:29:23 <ralonsoh> so all good
14:29:49 <ralonsoh> and as usual, the nominees
14:29:52 <ralonsoh> This week amotoki is the deputy, next week will be mlavalle.
14:30:16 <ralonsoh> ok?
14:30:22 <haleyb> there was one more
14:30:30 <ralonsoh> sure please
14:30:36 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2012144
14:30:55 <haleyb> ykarel noticed it might just be an OVN version issue, submitter was going to check
14:31:57 <ralonsoh> exactly
14:32:00 <ralonsoh> this is the problem
14:32:18 <ralonsoh> and I remember seen that in out internal CI last week
14:32:39 <ralonsoh> I'll check the versions released and I'll close the bug if needed
14:32:55 <ralonsoh> ykarel, thanks for finding the problem (and the fix)
14:34:01 <haleyb> that's all the bugs i had
14:34:12 <ralonsoh> thanks, I missed that one
14:34:23 <ralonsoh> ok, let's move to the next topic
14:34:29 <ralonsoh> #topic community_goals
14:34:35 <ralonsoh> 1) Consistent and Secure Default RBAC
14:34:43 <ralonsoh> slaweq, did you have time to check the timeouts?
14:34:51 <slaweq> not yet
14:35:00 <slaweq> I have it on my todo but didn't get to it yet
14:35:09 <ralonsoh> no problem
14:35:11 <ralonsoh> qq
14:35:18 <ralonsoh> do we have these issues in master?
14:35:24 <ralonsoh> or in 2023.1?
14:35:34 <slaweq> I don't think so
14:35:49 <ralonsoh> btw, I'm talking about the n-t-p-patch
14:35:54 <ralonsoh> adding CI support for Zed
14:35:56 <ralonsoh> one sec
14:36:04 <slaweq> time of that job with "new-defaults" is similar to other jobs
14:36:14 <ralonsoh> #link https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/874709
14:36:52 <ralonsoh> because in master this job is taking 1h11m
14:36:56 <ralonsoh> same as others
14:36:56 <lajoskatona> so we can merge this one?
14:37:08 <ralonsoh> but in Zed this is taking more that 2h
14:37:25 <slaweq> are You sure? I'm looking now at https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/874709/6
14:37:27 <ralonsoh> one sec: 2023.1 job is missing, right?
14:37:51 <ralonsoh> actually no, we need new n-t-p jobs for 2023.1
14:37:54 <slaweq> and neutron-tempest-plugin-openvswitch-enforce-scope-new-defaults is faster than other jobs
14:38:00 <lajoskatona> generally the jobs were merged: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/877613
14:38:02 <frickler> ralonsoh: iirc you wanted to add those some time ago
14:38:17 <ralonsoh> ^^ there it is
14:38:51 <ralonsoh> slaweq, do you mind rebasing https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/874709 and adding 2023.1 job?
14:39:03 <slaweq> yeah, I will do that
14:39:07 <ralonsoh> thanks!
14:39:44 <ralonsoh> ok, next one is
14:39:49 <ralonsoh> 2) Neutron client deprecation
14:39:59 <ralonsoh> first of all, sorry: I didn't review any patch
14:40:05 <lajoskatona> the usual etherpad: https://etherpad.opendev.org/p/python-neutronclient_deprecation
14:40:24 <lajoskatona> and the open patches: https://review.opendev.org/q/topic:bug/1999774+status:open
14:40:48 <lajoskatona> the SDK side of BGPVPN is in good shape, so I can move on to the next one
14:41:11 <lajoskatona> this is the bgpvpn patch: https://review.opendev.org/c/openstack/openstacksdk/+/875530
14:41:33 <lajoskatona> that's all news regarding this topic I think
14:41:51 <ralonsoh> yeah, sdk looks fine
14:42:19 <ralonsoh> thanks a lot for your commitment on this topic
14:42:55 <ralonsoh> ok, let's move to the last topic
14:42:59 <ralonsoh> #topic on_demand
14:43:07 <ralonsoh> one qq
14:43:09 <ralonsoh> https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032770.html
14:43:24 <ralonsoh> to transition Tran to EOL
14:43:42 <ralonsoh> I think it is time for this and most of the projects are doing that
14:43:52 <ralonsoh> do you agree?
14:44:02 <mlavalle> +1
14:44:10 <lajoskatona> +1
14:44:11 <mlavalle> You meant Train, right?
14:44:16 <ralonsoh> yeah, sorry
14:44:50 <haleyb> +1
14:44:53 <ralonsoh> slaweq, obondarev, rubasov ?
14:45:07 <obondarev> no objections, +1
14:45:14 <slaweq> +1 from me
14:45:29 <rubasov> +1
14:45:46 <slaweq> EOL train and we are finally done with python 2 once and forever :)
14:45:54 <ralonsoh> exactly
14:45:58 <mlavalle> \o/
14:46:07 <mtomaska> \o/
14:46:21 <ralonsoh> cool, let's check, after the PTG, what to do with Victoria. But we can discuss this in 2 weeks, no rush
14:46:24 <ralonsoh> and second one
14:46:29 <ralonsoh> #link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers
14:46:51 <ralonsoh> ihrachys, slaweq do want to keep this topic here? or the mail sent and next week PTG will be enough?
14:47:11 <slaweq> we don't need that topic anymore I guess
14:47:22 <slaweq> please read and reply to ihrachys' email
14:47:32 <slaweq> and that should be enough
14:47:35 <ralonsoh> yeah, I have it open
14:47:50 <ralonsoh> thanks!
14:48:02 <ralonsoh> nothing else from me
14:48:10 <slaweq> on qq
14:48:12 <slaweq> *one qq
14:48:19 <opendevreview> Dmitrii Shcherbakov proposed openstack/neutron-lib master: ext-gw-multihoming: api-def and api-ref  https://review.opendev.org/c/openstack/neutron-lib/+/870887
14:48:36 <slaweq> will You cancel next week's meeting ralonsoh? As there's PTG then
14:48:56 <ralonsoh> yeah, I'll send a mail cancelling all Neutron meetings
14:49:03 <slaweq> thx
14:49:09 <haleyb> one question on DB branch from me... https://review.opendev.org/c/openstack/neutron/+/876051 - i'm assuming we merge when 2023.1 is tagged?
14:49:48 <haleyb> it's the Bobcat branch commit
14:49:49 <ralonsoh> yes, when a branch is released, we close it in the DB migration
14:49:59 <ralonsoh> neutron_milestone = [migration.RELEASE_2023_1]
14:50:29 <haleyb> i just knew someone was waiting, 2023.1 should be soon i hope
14:50:36 <ralonsoh> so we can merge that one now
14:50:50 <slaweq> 2023.1 branch is already there
14:50:59 <slaweq> And final release will be this week AFAIK
14:51:44 <haleyb> right, and i couldn't see a backport doing a DB migration, so someone can +2
14:51:53 <ralonsoh> no
14:52:12 <ralonsoh> db migrations, api changes or config changes are not allowed
14:52:28 <haleyb> well, a backport needed for 2023.1 RC2 i mean
14:52:30 <ralonsoh> but DB migrations are blocked by the migration tool itself
14:52:59 <ralonsoh> not anymore
14:53:12 <ralonsoh> what patch are you talking about?
14:53:19 <ralonsoh> just to have some context
14:53:40 <haleyb> there is no patch, it was hypothetical
14:53:54 <ralonsoh> so no, no db migration backports
14:54:22 <ralonsoh> anything else?
14:54:39 <ralonsoh> thank you all and remember that the CI meeting is in 5 mins, in this channel
14:54:45 <ralonsoh> #endmeeting