Tuesday, 2026-02-03

opendevreviewLajos Katona proposed openstack/neutron-fwaas master: CI: Add required_projects to unit test jobs  https://review.opendev.org/c/openstack/neutron-fwaas/+/97307907:05
opendevreviewGwangseok Jeon proposed openstack/neutron master: Fix lazy field access in get_port(s) to prevent premature relationship loading  https://review.opendev.org/c/openstack/neutron/+/94830607:05
opendevreviewRodolfo Alonso proposed openstack/neutron master: OVN ``Port_Binding.additional_chassis`` is supported since v22.09.0  https://review.opendev.org/c/openstack/neutron/+/97525107:07
opendevreviewRodolfo Alonso proposed openstack/neutron master: OVN ``NAT.gateway_port`` is supported since v22.06.0  https://review.opendev.org/c/openstack/neutron/+/97525607:16
opendevreviewRodolfo Alonso proposed openstack/neutron master: OVN ``NAT.gateway_port`` is supported since v22.06.0  https://review.opendev.org/c/openstack/neutron/+/97525607:18
opendevreviewRodolfo Alonso proposed openstack/neutron master: OVN ``Meter.fair`` is supported since v20.12.0  https://review.opendev.org/c/openstack/neutron/+/97525707:18
opendevreviewRodolfo Alonso proposed openstack/neutron-tempest-plugin master: Test patch 972982  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/97549007:20
opendevreviewEduardo Olivares proposed openstack/neutron master: WIP: new job tempest-multinode-with-bgp  https://review.opendev.org/c/openstack/neutron/+/96218807:35
opendevreviewPierre Libeau proposed openstack/neutron master: Add default policy on device_id param create_port  https://review.opendev.org/c/openstack/neutron/+/86116907:45
ralonsohfolks, if you have 1 min: https://review.opendev.org/c/openstack/neutron/+/97336608:04
ralonsohthanks in advance08:05
opendevreviewMerged openstack/neutron-fwaas master: CI: Add required_projects to unit test jobs  https://review.opendev.org/c/openstack/neutron-fwaas/+/97307908:24
opendevreviewMerged openstack/neutron-vpnaas master: Use project_id in some base create_* API calls  https://review.opendev.org/c/openstack/neutron-vpnaas/+/97547909:31
opendevreviewEduardo Olivares proposed x/whitebox-neutron-tempest-plugin master: Do not unset 'is_controller' parameter from discovered nodes  https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/97549409:49
*** ykarel_ is now known as ykarel09:53
opendevreviewEduardo Olivares proposed x/whitebox-neutron-tempest-plugin master: Do not disable 'is_controller' parameter from discovered nodes  https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/97549409:57
mstinskyGreetings, I have 2 patches open which fixes broken ovn vpnaas implementation. https://review.opendev.org/c/openstack/neutron-vpnaas/+/963490 and https://review.opendev.org/c/openstack/neutron-vpnaas/+/963487 I am unsure how I could get some priority on it for reviews. Best Regards Max11:31
opendevreviewMerged openstack/neutron-vpnaas master: Fix ipsec config updates not working  https://review.opendev.org/c/openstack/neutron-vpnaas/+/96349012:53
haleybwill start in a few minutes, need to let dog out quickly13:58
haleyb#startmeeting networking14:02
opendevmeetMeeting started Tue Feb  3 14:02:05 2026 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
opendevmeetThe meeting name has been set to 'networking'14:02
haleybPing list: bcafarel, elvira, frickler, mlavalle, mtomaska, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, haleyb, ralonsoh14:02
mlavalle\o dog ok now?14:02
ralonsohhello14:02
* bcafarel is tempted to sing "Who Let the Dogs Out"14:02
rubasovo/14:02
ralonsohslaweq is in PTO today14:02
lajoskatonao/14:02
haleybmlavalle: she's fine, just crying at the door14:03
haleyb"who who who"14:03
* mlavalle sighs of relief14:03
haleybso did she :)14:03
haleybalright, we can get started14:04
haleyb#announcements14:04
haleybWe are in week R-8 of Gazpacho14:04
haleyb#link https://releases.openstack.org/gazpacho/schedule.html is the release schedule14:04
haleybG3 milestone is week R-5, February 23-27th14:05
haleybso just 3 weeks away14:05
haleybplease make sure any work for an approved spec is getting wrapped up, or is already proposed14:06
haleybJust a reminder to use the priority dashboard for anything neutron/networking related14:06
haleyb#link https://tinyurl.com/59z278km14:07
haleybRP +1 for "ready to merge" changes, RP +2 for gate blockers and similar14:07
haleybthere are a few things there at the moment14:07
haleybReminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers14:08
haleybi will not be around this friday, and i see nothing on the agenda, so i will cancel, i'll send an email reminder14:08
ralonsohwe usually have tight quorum14:09
haleybyup14:09
ralonsohif you won't be present, it will be better to directly postpone anything for the next friday14:09
haleybralonsoh: i do plan on canceling14:10
haleyblast announcement is about PTG, hopefully everyone saw the email from kendall14:11
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/65JHXUYJJUPSAXPY7AJFR2VYWNZUJTWT/14:11
haleybThe next OpenInfra PTG[1] will take place April 20-24, 2026 ,,,14:11
haleybthere is a registration link in the email, and it's virtual as usual14:12
haleybi will sign-up neutron in the survey14:13
haleybthat was all i had, any other announcements?14:13
opendevreviewRodolfo Alonso proposed x/whitebox-neutron-tempest-plugin master: Retrieve the metadata service name during the resource setup  https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/97551114:14
haleyb#topic bugs14:14
haleybykarel was the bug deputy last week, his report is at14:14
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/WP7ZNORKXUCGDUNLHYUQSHXGNBRG2YK2/14:15
haleybthe critical/high/medium are assigned or fixed already :)14:15
haleybso we have just two to discuss14:15
haleyb#link https://bugs.launchpad.net/neutron/+bug/213941614:16
haleyb[doc] Document what changes are needed when changing supported Python version14:16
haleybright, we need to put that in the contributors guide14:16
haleybi'll see if i can pick it up this week14:17
ralonsohwe have several projects (vpaans, taas, etc) and is difficult to remember all the needed changes14:17
ralonsohthanks haleyb!14:17
lajoskatonagood idea14:17
haleybyes, and i just found another yesterday that wasn't testing py313 (vpnaas?) and proposed a patch14:18
lajoskatonawe should have an AI bot fr such works :P14:18
ralonsohfor sure ^^14:18
haleybif someone has the time for AI they can take that one :)14:19
haleyba lot is just auditing all the repos and making sure things are running as expected14:20
haleybnext bug14:21
haleyb#link https://bugs.launchpad.net/neutron/+bug/213958314:21
haleybneutron-openvswitch-agent native driver: Permanent flow loss after OVS restart due to unhandled 'unknown dpid' during rpc_loop14:21
haleybykarel asked for more info, so incomplete at the momend14:22
ralonsohthat usually happens when the OF connection (os-ken) disconnects14:23
lajoskatonaI can keep an eye on it, it sounds something our QA team can find sooner or later anyway :-)14:23
ralonsohmaybe it is not reconnecting, but more logs could be useful here14:23
lajoskatonais it master with threading or eventlet?14:23
lajoskatonaoh I see flamingo 2025.214:24
lajoskatonathere we had eventlet still, or am I wrong?14:24
haleyband i do see the logs, hadn't refreshed the page14:24
haleyblajoskatona: should be threading, but could have been a bug there as well?14:24
ralonsohyes, should be threading (native)14:25
haleyblajoskatona: thanks for keeping an eye on it, i'll watch for now as well14:26
haleybthose were the only bugs i had to discuss, any others?14:27
ralonsohrelated to the RPC bug14:27
ralonsoh#link https://review.opendev.org/c/openstack/neutron/+/97440414:27
ralonsohif you have some minutes to review it, thanks!14:28
haleybsure, it's on my list14:28
haleybthis week otherwiseguy is the deputy, next week is mtomaska - is that good for both?14:29
haleybalthough terry isn't in the channel14:29
ralonsohI'll ping him14:30
mlavalleI'll ping him in slack14:30
haleyboh, and there was an OVN question on the ML regarding metadata and sriov, i have not had cycles to look, don't know if someone else does14:30
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/I32KDQUVGD457APA4CTLXVA2BFW3F7JR/14:31
ralonsohI'll check it14:31
haleybralonsoh: thanks, even if they just file a bug we can track it14:32
haleybok, moving on14:33
haleyb#topic specs14:33
haleyb#link https://review.opendev.org/q/project:openstack/neutron-specs+status:open14:33
haleybi see the PVLAN spec is there, thanks elvira14:34
haleybthere are a few others, not sure if they are ready to merge at the moment, will look later14:35
haleyb#topic community goals14:35
haleyblajoskatona: any update on the sdk series?14:36
mlavalleotherwiseguy is ok being bugs deputy this week14:36
haleyb#link https://review.opendev.org/q/topic:%22sdk_for_neutron%2214:36
haleybmlavalle: ack, thanks!14:36
lajoskatonayes, I have a chat with Nova team, and they started to review the series14:36
lajoskatonaI have a recurring slot in the nova weekly meeting to keep the attention :-)14:37
haleybwoo-hoo :) sorry no dance emojis here14:37
haleyband thanks for continuing the work!14:38
ralonsohlajoskatona++14:38
haleybwe actually had some downstream code we changed to use the sdk, i had pointed at your code for reference14:39
lajoskatonahaleyb, thanks, I have to go back check the coming comments also14:39
haleyback14:40
lajoskatonaso I hope sometimes it will be on master and you can point to that14:40
haleybok, moving on14:42
haleyb#topic on-demand14:42
* fungi waves14:42
fungii added "Bridging the Gap Flamingo Cycle Retrospective" if there's time14:42
haleybfungi: sure, go ahead, i had a topic can go after14:43
fungithanks14:43
fungiildiko posted openstack-wide 2025.2 (flamingo) cycle retrospective contributor/maintainer survey results and metrics to openstack-discuss last month:14:43
fungi#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/XZZYFHMUCB3IZU5AXM366AY7WJXQMTBX/ Bridging the Gap Flamingo Cycle Retrospective Survey Results14:43
fungi#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/FD4JALJN7OB2YNBUVWCPZZ6YNJMIL2JT/ Bridging the Gap Flamingo Cycle Retrospective Metrics Analysis14:43
fungii and the other community managers on the openinfra foundation staff have also been digging into team-specific details and i'm doing a round of outreach similar to last cycle, to go over how things may have changed14:43
fungithe neutron team had 2 contributors and 1 maintainer submit survey responses; while this is more than most other teams had, i'd still like to find a way to get it in front of more folks next time14:43
fungiboth of the contributors self-identified as being new to neutron, and indicated that they each contribute to one other open source project as well14:44
fungiaverage ratings on the contributor survey questions were positive overall, with actionable reviewer feedback coming in highest at 4.5 out of 5 and testing reliability the lowest with 2.5, but both diverged widely in their experiences14:44
fungiwhen analyzing the survey responses, we found it interesting that the two contributors gave very different ratings, so maybe there was some inconsistency between the interactions they encountered (hard to say with so few responses)14:44
fungiease of getting reviewers to look at their changes was cited as the biggest challenge by both though14:44
fungithe new survey questions about priorities were insightful: both contributors followed prioritization through launchpad blueprints and discussions in irc or the mailing list, while one of them also mentioned gerrit change topics14:44
fungithis mostly overlapped the maintainer's response about priority tracking, though they called out specs first, and also review-priority votes in gerrit (neither of which were mentioned by the contributors)14:44
fungithe rankings on the one maintainer survey response was high, all 4 or 5 out of 5, though like the contributors they noted struggles getting reviews on their changes from other maintainers14:44
fungias for challenges reviewing the work of others, they called out unresponsive change proposers, changes that weren't a priority for the team, and to parts of the code outside their area of expertise, highlighting the project's complexity14:44
fungimetrics: active maintainer count fell by 11% while reviewer count rose by 6%, though more generally both numbers have been on a steady decline over the past 5 release cycles14:45
fungithe team closed more changes than were open in flamingo (unlike epoxy), though the overall number of both also fell by around 8-9% from the volume in the previous cycle, suggesting the workload might have decreased somewhat at least14:45
fungibut all three respondents (the contributors and maintainer) pointed at review inattention as a continuity, which has been fairly common across all the projects that got survey responses, and paints a different picture14:45
fungirelated, the time to merge and time to review interestingly both saw slower median values but were faster on average (mean), which implies an increase in consistency (and were better than every other recent cycle except epoxy)14:45
fungioverall, statistics for flamingo were more like those in dalmatian, except that there were more active maintainers and reviewers in the dalmatian cycle, so it's possible epoxy was more of an outlier14:45
fungithough epoxy looked superficially similar to caracal... maybe this is a side effect of the slurp/not-slurp release cadence playing out?14:45
fungithe maintainer response about project complexity and also about changes being outside their sphere of expertise/comfort zone echoed similar concerns raised in epoxy too, so maybe there's a missing maintainer onramp or similar opportunities14:45
fungithe community managers have been distilling feedback from last year's discussions, and are working on compiling a concise set of techniques/recommendations for improving communication and efficiency, which i can get into more next week14:46
fungiwe're also hoping to get some case studies done in concert with successful contributors and maintainers to highlight how specific practices and behaviors help them achieve better throughput, in hopes of being able to replicate them14:46
fungianyway, that was a quick dump, i know it's a lot to take in but i didn't want to eat up too much of your meeting, so i'll put this on the agenda again for next week to give everyone time to digest and come up with questions or ideas14:46
fungithough i'm happy to answer any immediate feedback now if there's time, otherwise i'll cede the floor to haleyb14:46
haleybi can't say i looked at the survey results, not sure if others had and have questions?14:47
haleybi can look at the links later14:48
ralonsohno questions, thanks for the info14:49
fungimy pleasure!14:49
lajoskatonanot from me, perhaps we can add it to the coming PTG agenda to spend few minutes on it as part of the retrospective?14:49
haleybthanks fungi, and i guess it's also a reminder to have more of us fill out the survey14:49
fungiwanted to get it in front of folks to mull over, then i'll try to check back in next week14:50
haleyblajoskatona: that would be a good idea as well14:50
fungiand yes, of course, please do, we'll try to have the gazpacho survey out around rc week14:50
fungii hope we can have some base analysis for a gazpacho retrospective around or just after the ptg14:51
fungibut we haven't worked out a precise schedule for thatquite yet14:51
haleybI had one topic for on-demand as well14:52
haleybwe had two similar patches for fixing a floating IP issue that was seen14:53
haleyb#link https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/97501214:53
haleyb#link https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/97086514:53
haleybi wasn't sure if anyone had an opinion on one versus the other14:53
haleyband they have separate bugs linked and descriptions, so a double-check that are fixing the same thing would help me :)14:54
ralonsohboth LP bugs are the same?14:54
haleybralonsoh: different bugs, but i think they seemed related14:55
haleybboth are trying to create servers in the same AZ14:56
haleybanyways, that was all i had14:58
haleybother topics?14:58
haleybok, thanks for attending, have a great week everyone!14:58
haleyb#endmeeting14:58
opendevmeetMeeting ended Tue Feb  3 14:58:47 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:58
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2026/networking.2026-02-03-14.02.html14:58
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2026/networking.2026-02-03-14.02.txt14:58
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2026/networking.2026-02-03-14.02.log.html14:58
ralonsohbye14:58
lajoskatonao/14:59
mlavalle\o15:00
opendevreviewRodolfo Alonso proposed openstack/neutron master: OVN ``Meter.fair`` is supported since v20.12.0  https://review.opendev.org/c/openstack/neutron/+/97525716:02
opendevreviewMerged openstack/neutron master: Use project_id in HANetworkConcurrentDeletion()  https://review.opendev.org/c/openstack/neutron/+/97424716:13
opendevreviewMerged openstack/neutron master: Drop redundant description of default values  https://review.opendev.org/c/openstack/neutron/+/97272416:22
fricklerhaleyb: fyi the current acls for gerrit only allow neutron-core to vote Review-Priority. you could amend the acl to allow anyone to set this if you want, though16:28
haleybfrickler: ah, didn't know that, makes sense given the comment on ML16:32
opendevreviewPierre Libeau proposed openstack/neutron master: Set default policy on device_id for create_port/update_port  https://review.opendev.org/c/openstack/neutron/+/86116916:36
opendevreviewLajos Katona proposed openstack/neutron-dynamic-routing master: [S-RBAC] New default API policies for n-d-r  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/94846517:50
opendevreviewMerged openstack/neutron master: Add TXT records to dnsmasq  https://review.opendev.org/c/openstack/neutron/+/95048618:20
opendevreviewJakub Libosvar proposed openstack/neutron master: WIP: new job tempest-multinode-with-bgp  https://review.opendev.org/c/openstack/neutron/+/96218819:49
opendevreviewJakub Libosvar proposed openstack/neutron master: bgp: Don't include all bridge IPs in openflow  https://review.opendev.org/c/openstack/neutron/+/97556719:50
opendevreviewJakub Libosvar proposed openstack/neutron master: bgp: Use UpdateLocalOVSEvent  https://review.opendev.org/c/openstack/neutron/+/97557020:13
opendevreviewMerged openstack/neutron-lib master: Remove tenant_id from HANetworkConcurrentDeletion()  https://review.opendev.org/c/openstack/neutron-lib/+/97424820:38
opendevreviewBrian Haley proposed openstack/neutron master: Use project_id key in port plugin code  https://review.opendev.org/c/openstack/neutron/+/97298221:35
opendevreviewMerged openstack/neutron-tempest-plugin master: Fix FloatingIpTestCasesAdmin.test_two_vms_fips  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/97086523:35
opendevreviewMerged openstack/neutron master: Add information to network ip availabilities  https://review.opendev.org/c/openstack/neutron/+/96508323:35

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!