13:00:19 <haleyb> #startmeeting networking
13:00:19 <opendevmeet> Meeting started Tue Jul 29 13:00:19 2025 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:19 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:19 <opendevmeet> The meeting name has been set to 'networking'
13:00:21 <haleyb> Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, haleyb, ralonsoh
13:00:29 <lajoskatona> o/
13:00:30 <mtomaska> o/
13:00:33 <frickler> \o
13:00:35 <cbuggy> o/
13:00:58 <bcafarel> o/
13:01:01 <mlavalle> \o
13:01:53 <haleyb> hi everybody, i'm back :)
13:02:07 <haleyb> #announcements
13:02:16 <haleyb> We are currently in Week R-9 of Flamingo
13:02:31 <haleyb> Our next milestone in this development cycle will be Flamingo-3, week of August 25th
13:02:40 <haleyb> Final 2025.2 Flamingo release: October 3rd, 2025
13:02:48 <haleyb> #link https://releases.openstack.org/flamingo/schedule.html
13:03:45 <slaweq> o/
13:03:49 <haleyb> The next OpenInfra PTG will take place October 27-31, 2025 and registration for the event is now open
13:03:55 <haleyb> #link https://ptg.openinfra.dev/
13:04:25 <haleyb> The release schedule for Gazpacho has also been proposed
13:04:33 <haleyb> #link https://review.opendev.org/c/openstack/releases/+/954614
13:04:49 <haleyb> April 1st, 2026 planned release date
13:05:49 <haleyb> Reminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers
13:06:19 <haleyb> that was all my announcements, any others?
13:06:45 <haleyb> moving on
13:06:48 <haleyb> #topic bugs
13:07:11 <haleyb> last week jlibosva was the bug deputy, his report is at
13:07:19 <haleyb> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/5QTZKYN3PZ55MHGUX5EHXSNFYNMRTODP/
13:07:43 <haleyb> first critical bug is
13:07:49 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2118902
13:07:57 <haleyb> tobiko jobs failing while download fedora qcow2 image
13:08:24 <haleyb> being fixed in https://review.opendev.org/c/x/tobiko/+/955769
13:09:20 <haleyb> ykarel: should we close that neutron bug as you mentioned?
13:10:12 <haleyb> yatin might not be here, can follow-up
13:10:26 <ykarel> haleyb, yes can be done, was just for tracking
13:10:36 <haleyb> ah, ok, thanks
13:10:44 <haleyb> next bug
13:10:50 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2117405
13:10:56 <haleyb> test_subport_delete random failure
13:11:43 <haleyb> this was seen a couple of times in logs
13:12:21 <haleyb> and i see rodolfo has assigned to himself
13:13:03 <haleyb> the other two high priority bugs have patches proposed already
13:13:16 <haleyb> moving on to medium ones
13:13:42 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2116927
13:13:50 <haleyb> Horizon shows all prefix lengths when creating subnet from subnet pool
13:14:02 <lajoskatona> I pushed patch for it yesterday
13:14:12 <haleyb> #link https://review.opendev.org/c/openstack/horizon/+/956006
13:14:18 <haleyb> lajoskatona: ack, thanks!
13:15:54 <haleyb> next one was about eventlet hacking checks
13:16:00 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2117373
13:16:09 <haleyb> [eventlet-removal] Add N535 hacking check to ban eventlet imports
13:16:54 <haleyb> neutron-lib had already done this, fwaas and vpnaas patches proposed as part of this bug
13:17:12 <lajoskatona> yes we can reuse the check in n-lib for this
13:17:20 <haleyb> we'll eventually add it to neutron as well
13:18:19 <haleyb> next one
13:18:27 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2117383
13:18:35 <haleyb> [neutron-tempest-plugin] Test ``test_create_router_update_external_gateways`` failing
13:19:10 <haleyb> mlavalle picked this up, thanks miguel
13:19:54 <haleyb> next one
13:19:57 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2117477
13:20:03 <haleyb> [unmaintained-only] unknown keyword flow_group_id
13:20:26 <haleyb> rubasov took this and i think proposed all necessary patches
13:21:19 <haleyb> seems to have just affected v/w/x/y releases
13:22:42 <bcafarel> and all merged now I think
13:22:57 <haleyb> excellent
13:23:19 <haleyb> next medium has a patch so we can skip to low one
13:23:26 <haleyb> https://bugs.launchpad.net/neutron/+bug/2118360
13:23:32 <haleyb> NotFoundException: 404 error when associating FIP with an unreachable network
13:24:20 <lajoskatona> another one for Horizon, I try to check it this week to see the root cause
13:25:56 <haleyb> lajoskatona: ack, thanks. i don't exactly understand the failure case, it sounds familiar from a neutron perspective though
13:27:12 <lajoskatona> yes, not fully clear what is the exact expectation and if it is realted to the SDK migration or something else
13:28:24 <haleyb> yeah, i wonder if it happens with just OSC and not horizon
13:28:41 <lajoskatona> I will check it
13:29:15 <haleyb> great
13:29:18 <ykarel> iirc same response is returned with openstackcli
13:29:58 <lajoskatona> ykarel: thanks
13:30:24 <haleyb> i'll look at old bugs later to see if there is a match
13:30:39 <lajoskatona> +1 good idea
13:31:25 <lajoskatona> in comments on this patch there are some hints https://review.opendev.org/c/openstack/horizon/+/938488 from Ivan Anfimov from where the exception is comming
13:33:28 <haleyb> ack
13:33:55 <haleyb> there were some incomplete bugs, can go through them quickly
13:33:58 <haleyb> https://bugs.launchpad.net/neutron/+bug/2116723
13:34:04 <haleyb> VPN Perfect Forward Secrecy (PFS) is deactivated although configured as active
13:35:56 <haleyb> he shared his neutron.conf bug someone will need to go through it that maybe better understands vpnaas
13:37:01 <haleyb> next one
13:37:05 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2116837
13:37:11 <haleyb> Performance Tuning for Nested VXLAN Tunnel in OpenStack (OVS Backend)
13:37:38 <haleyb> i asked a number of question but have not seen a response, will keep watching
13:38:24 <haleyb> next one
13:38:31 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2117078
13:38:37 <haleyb> OVN: Intermittent metadata failures for SR-IOV VMs
13:39:13 <haleyb> seems rodolfo is actively trying to help, so in good hands
13:39:48 <haleyb> last one
13:39:52 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2117153
13:39:58 <haleyb> neutron-openvswitch-agent crashes on start
13:41:13 <haleyb> this was on bobcat, which is EOL, i asked for reproducer on caracal but submittor responded they are having problems reproducing
13:41:25 <haleyb> i'll keep watching
13:41:33 <haleyb> that was all the bugs
13:41:59 <haleyb> any others to discuss?
13:42:19 <haleyb> this week ykarel is the bug deputy, next week will be otherwiseguy
13:42:42 <ykarel> thx for reminding, i might have lost that last week
13:43:30 <haleyb> ack, i don't see terry here maybe someone can ping him internally and make sure he can do next week?
13:44:29 <haleyb> moving on
13:44:33 <haleyb> #topic community goals
13:45:03 <haleyb> lajoskatona: any updates for neutronclient? besides the bug fix?
13:45:21 <lajoskatona> just the bugs and fixe for mone of them we covered already
13:45:51 <lajoskatona> for one of them (sorry seems like my keyboard is not in sync with me today)
13:46:51 <haleyb> ack, thanks
13:47:36 <haleyb> and i don't see rodolfo for an eventlet update, but seems he's still working on unit tests
13:47:46 <haleyb> #link https://review.opendev.org/c/openstack/neutron/+/952258
13:49:49 <haleyb> i have no more updates on that
13:50:00 <haleyb> #topic on-demand
13:50:15 <haleyb> there was nothing on the agenda, but does anyone have a topic?
13:51:00 <fungi> i have something that i neglected to add to the agenda, but can punt to next week if there's not time
13:51:17 <haleyb> fungi: we have 9 minutes so think we have time
13:51:23 <fungi> (not sure if on-demand is the same as open discussion, sorry)
13:51:37 <haleyb> yes, open discussion
13:51:42 <fungi> i'll try to be quick, but there's a lot we dug into... for some background on openstack-wide metrics analysis see ildikov's most recent ml post from about a month ago:
13:51:50 <fungi> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/NTBNI7YIDCWBR6BTPEKVZIODWTVUIOXO/ BtG metrics analysis
13:51:58 <fungi> also could be worthwhile to revisit her previous post in that thread going over the contributor and maintainer survey results (and anyone who hasn't filled those out for epoxy, please see if you can find a few minutes to do that!)
13:52:06 <fungi> as a follow-up activity, we've started doing some team-specific analyses, focusing on teams that had multiple contributor and maintainer survey responses (already did nova, cinder, ironic, octavia and kolla in recent weeks)
13:52:14 <fungi> we're early in the process of analyzing these stats with a focus on improving the experience for maintainers and contributors, so for now this is probably a lot of stuff you already know, or at least confirming what you expected
13:52:22 <fungi> a big part of this is establishing a baseline so that we can better gauge whether future attempts at improving have any observable impact, but we aren't at the point where we have much in the way of guidance or recommendations yet
13:52:34 <fungi> we have plans to continue with this sort of surveying and metrics analysis over coming release cycles; as for the initial results...
13:52:41 <fungi> the contributor survey had 3 responses for neutron and all respondents had contributed for at least two years and were contributors to at least two other open source projects
13:52:48 <fungi> feedback was overwhelmingly positive (averages of 4-4.67 out of 5) with the highest score on "[contributor docs] You were able to find information about the processes the project team is using"
13:52:58 <fungi> lowest was a tie between getting timely reviews, test failures identifying problems with the contribution, and contributor docs helping apply better practices/achieve faster results
13:53:07 <fungi> the top challenges reported were trouble with review attention or blanket rejection on changes for smaller/ancillary repositories, as well as an overall shortage of available reviewers (this one is pretty common across all the teams anyway)
13:53:14 <fungi> the maintainer survey had only response so far, ranking 5 on everything except for a 4 on contributor documentation being up to date
13:53:30 <fungi> contributing challenge reported by that maintainer was similar to those from the contributor survey (review attention), but also a need for specialist domain expertise in many parts of the code
13:53:42 <fungi> top challenges with reviewing were a lack of familiarity with certain parts of the code base, and contributors not addressing review feedback or test failures in a timely manner
13:53:54 <fungi> additional feedback noted the stability of test jobs has been crumbling over time, with a lack of maintainer failiarity in the tests and a shortage of maintainers overall this poses a potential sustainability risk
13:54:13 <fungi> looking at metrics we gathered from gerrit for the past 5 development cycles, review response was varied with faster results in the main repositories while things tended to sit more in the periphery
13:54:26 <fungi> it's likely that the practice of closing changes when it's clear they're not going anywhere due to lack of reviews contributes to this, but in every cycle except one (bobcat) the team closed more changes than were open
13:54:39 <fungi> metrics also indicated a steady shrinkage of reviewers, which supports survey responses on the subject
13:54:45 <fungi> sorry, i know that's a pretty big info dump (i tried to pare it down as much as possible), and i'm happy to answer questions or take feedback either here in the meeting or any time after
13:55:10 <haleyb> so the epoxy survey you mentioned at the beginning is
13:55:14 <haleyb> #link https://openinfrafoundation.formstack.com/forms/openstack_contributor_satisfaction_survey
13:55:39 <fungi> there are two, the other is the maintainer survey, but yes
13:56:03 <haleyb> #link https://openinfrafoundation.formstack.com/forms/openstack_maintainer_satisfaction_survey
13:56:26 <haleyb> just in case someone here has not seen them and wants to take them
13:56:39 <fungi> yeah, it's hard to draw concrete conclusions with only a handful of responses so far, so more responses definitely help
13:57:03 <haleyb> fungi: is there a plan to dig deeper on neutron? i see you mentioned it had been done for other projects
13:57:11 <fungi> and they're designed to be super quick (under 5-minute) surveys, though i guess you can take longer if you want to write a bunch in the freeform fields
13:58:09 <fungi> well, the summary above was the deep digging we did into neutron-specific responses and metrics so far. as much as anything the data we collected will serve as a baseline to compare future cycles against
13:58:45 <fungi> each of the teams i mentioned, i attended one of their meetings and delivered a similar summarization
13:59:18 <fungi> if there are specifics anyone's interested in, i can pull out more details as long as i keep things from the surveys properly anonymous
13:59:51 <fungi> hopefully the above is enough to get you thinking about what else you're curious to dig into though
14:00:05 <fungi> and as i said i'm happy to answer more specific questions later when you have them
14:00:28 <haleyb> fungi: i'll have to look through the dump, and hopefully others do as well
14:00:58 <fungi> that's all i had to present on the topic for now
14:01:09 <haleyb> it would be good to have some kind of action item to work if we see a deficiency
14:01:22 <haleyb> ok, i have to call it as i have another meeting
14:01:31 <fungi> thanks!
14:01:33 <haleyb> thanks for attending everyone, and have a good week!
14:01:37 <haleyb> #endmeeting