14:00:17 #startmeeting networking 14:00:17 Meeting started Tue Feb 27 14:00:17 2024 UTC and is due to finish in 60 minutes. The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:17 The meeting name has been set to 'networking' 14:00:25 Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki 14:00:26 \o 14:00:29 o/ 14:00:30 o/ 14:00:31 hi 14:00:34 o/ 14:00:44 o/ 14:01:21 hello 14:01:26 o/ 14:01:41 ok, lets get started 14:01:42 o/ 14:01:50 #topic announcements 14:02:01 #link https://releases.openstack.org/caracal/schedule.html 14:02:33 o/ 14:02:43 We are in C-3 milestone week 14:03:20 that means we shouldn't be landing a feature after this week 14:03:33 unless we grant an exception 14:04:18 the week of March 11 is RC1 14:04:46 that said, we still have one open feature 14:04:58 #link https://review.opendev.org/q/topic:%222023-aa-l3-gw-multihoming%22 14:06:09 fnordahl has been busy rebasing and addressing comments, would like to merge that since a lot of the changes have landed 14:07:17 I for one would be very interested in seeing that land, and happy to answer any questions. 90% of the feature has landed already. The remaining pieces is handling of the BFD records, the anti affinity support for scheduling of LRPs and of course client and documentation. 14:08:10 Are there any open issues as you see it preventing the review? 14:08:18 i cound 7 neutron patches, 2 n-t-p and 2 client 14:08:24 s/count 14:08:58 fnordahl: i think you have addressed all my comments, just need to re-review the chain 14:09:50 Helpfully it went into merge conflict this morning, which would be the reason for there not being test results on all of them right now, but the results are trickling in 14:10:03 I also want to draw attention to https://review.opendev.org/c/openstack/neutron/+/901513. It is the last part of OVN router flavors that we merged earlier during the cycle 14:10:35 I'll address lajoskatona comments from yesterday (thanks!) later today 14:11:37 mlavalle: ack, will take a look 14:12:02 haleyb: wait for me to fix what lajoskatona pointed out. I'll ping you 14:12:05 thanks! 14:12:23 sure 14:13:35 i would encourage people to ping reviewers if it helps to get things in this week 14:14:17 any other features to talk about? 14:15:05 one other announcement, i did self-nominate myself for ptl again, so if noone else runs you're stuck with me for 2024.2 :) 14:15:27 +1 14:15:46 thanks haleyb 14:15:46 Great! 14:15:52 thanks! 14:16:08 also, the TC nomination period is still open through today i think 14:16:44 please check the schedule to be sure if you are interested 14:17:23 #topic bugs 14:17:32 lucasgomes was deputy last week 14:17:40 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/PK7JYOJK55WKEC4LGW25V7OWRG6DYEZH/ 14:17:58 there were only 3 (!) bugs 14:18:21 #link https://bugs.launchpad.net/neutron/+bug/2054435 14:18:29 Testing errors when using new netaddr library 14:19:11 that is related with the topic I would like to comment later 14:19:26 about grouping the netaddr=1.0.0 problems in one LP bug 14:20:07 ralonsoh: ack, we can discuss in on-demand 14:20:27 next bug 14:20:32 #link https://bugs.launchpad.net/neutron/+bug/2054324 14:20:55 Iptables rule wrong if created a rule with protocol 4 14:21:21 i picked this up and proposed two changes, one in neutron-lib and one in neutron, which is temporary and backportable 14:21:34 #link https://review.opendev.org/c/openstack/neutron/+/909943 14:21:41 #link https://review.opendev.org/c/openstack/neutron-lib/+/909942 14:22:10 i wrote up a description in the bug since it's an odd one 14:22:57 qq about the n-lib patch 14:23:01 write-up is cool; would be even cooler to have it in the commit message :) 14:23:14 we are adding a new variable to a constants list 14:23:21 that is already used in the API 14:23:32 is that acceptable because this is a bug? 14:23:47 (because that was a missing value in this list) 14:24:30 ralonsoh: i think it's ok since neutron is the only user of that list afaik, let me check codesearch 14:25:10 but only if Neutron is using it 14:25:22 yes, it's only used in the iptables firewall driver when determining what to use with iptables-save/restore 14:26:15 ihrachys: i can put in the commit message, i might be the only one left with that esoteric knowledge of the iptables driver 14:28:09 the final bug here is an older one 14:28:14 #link https://bugs.launchpad.net/nova/+bug/2008238 14:28:20 SRIOV port binding_profile attributes for OVS hardware offload are stripped on instance deletion or port detachment 14:28:55 we are no longer writing any value in the port binding dict 14:28:56 https://review.opendev.org/c/openstack/neutron/+/898556 14:29:03 so this is no longer affecting Neutron 14:29:25 ack, i see you removed neutron from it, so --bug 14:30:24 Current bug count this week: 739, down 6 from last week 14:30:50 once we go into freeze i will spend more time pruning, thanks to others that have done the same 14:31:22 This week bug deputy is jlibosva 14:31:28 i don't see him here 14:31:39 I'll ping him later 14:31:39 next week is obondarev - is that good? 14:32:13 yep 14:32:50 thanks 14:33:14 topic #specs 14:33:19 #link https://review.opendev.org/q/project:openstack%252Fneutron-specs+status:open 14:33:56 there are still 2 open specs regarding bgp, if we don't merge this cycle will move them to next 14:34:21 it's really too late to merge any code related to them 14:35:09 #topic community_goals 14:35:52 i realize lajoskatona is not able to make it, his horizon patch is waiting for the sdk to be released 14:35:59 #link https://review.opendev.org/c/openstack/horizon/+/891205 14:36:40 so hopefully that happens soon since it's a step to removing rest of the neutronclient code 14:36:53 moving on 14:37:02 #topic on_demand 14:37:14 i did not update wiki, but we have one item from ralonsoh 14:37:32 very quick: we are finding new netaddr>=1.0.0 errors 14:37:47 now we have 2 LP bugs but I found another one this morning 14:37:58 IMO, we should track them all in a single LP bug 14:38:14 or at least have some kind of prefix in the commit message 14:38:23 same as sqlalchemy-20 14:39:18 +1 14:39:44 ralonsoh: what was the third one? 14:39:54 #link https://bugs.launchpad.net/neutron/+bug/2054435 14:40:03 #link https://bugs.launchpad.net/neutron/+bug/2054203 14:40:06 no, I didn't open a LP 14:40:13 https://review.opendev.org/c/openstack/neutron-lib/+/910331 14:40:23 oh, "now we have 2 LP bugs" 14:40:29 i thought you found a third 14:40:41 yes, this patch is a new bug 14:42:22 ah, ok 14:43:50 i did see takashi had proposed a netaddr patch so we could use the old style behavior, which would then require a change in neutron or oslo.utils 14:44:09 #link https://github.com/netaddr/netaddr/pull/377 14:44:26 because we still need to support things like 10/8 because they used to work 14:44:56 this is one of the issues reported in on LP bug 14:44:59 that's the point 14:45:16 nevermind, if we find new bugs, we should open new LP bugs 14:45:26 that's all, thanks 14:45:54 ralonsoh: ack, thanks 14:46:25 any other topics? 14:46:57 neutron-ci meeting is top of hour, irc this time i believe 14:47:09 yes right 14:48:27 ok, thanks everyone for attending, reach out on irc for reviews etc as it will be a busy week 14:48:30 #endmeeting