Tuesday, 2026-08-11

opendevreviewThomas Bachman proposed openstack/neutron master: Fix use of NetworkContext  https://review.opendev.org/c/openstack/neutron/+/99493600:47
opendevreviewMiro Tomaska proposed openstack/neutron-tempest-plugin master: Add dynamic VNI provisioning for EVPN tests  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/99860401:17
opendevreviewMiro Tomaska proposed openstack/neutron-tempest-plugin master: Add EVPN network advanced server operations tests  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/100019401:19
opendevreviewMiro Tomaska proposed x/whitebox-neutron-tempest-plugin master: [DNM] POC whitebox test which will allow inspecting state of chassis  https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/100036601:20
opendevreviewEduardo Olivares proposed openstack/neutron master: BGP job: enable more tempest scenarios and cross-compute scheduling  https://review.opendev.org/c/openstack/neutron/+/99816206:54
opendevreviewRoman Hros proposed openstack/neutron master: Ignore missing Port_Group when detaching ports in update_port  https://review.opendev.org/c/openstack/neutron/+/100041207:25
opendevreviewEduardo Olivares proposed x/whitebox-neutron-tempest-plugin master: Fix IGMP snooping test failure after OVS restart  https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/100041307:48
opendevreviewMerged openstack/neutron-vpnaas master: vpn: decouple LibreSwan from OpenSwan implementation  https://review.opendev.org/c/openstack/neutron-vpnaas/+/99980108:06
opendevreviewMerged openstack/neutron-vpnaas master: tests: replace ``load_tests`` with stestr regex filtering  https://review.opendev.org/c/openstack/neutron-vpnaas/+/99979108:06
opendevreviewMerged openstack/neutron-vpnaas master: Add LibreSwan functional tests  https://review.opendev.org/c/openstack/neutron-vpnaas/+/99960608:06
opendevreviewMiro Tomaska proposed openstack/neutron master: Add upstream EVPN multinode Zuul job  https://review.opendev.org/c/openstack/neutron/+/99425709:09
opendevreviewMerged openstack/neutron-vpnaas master: driver: remove OpenSwan driver implementation  https://review.opendev.org/c/openstack/neutron-vpnaas/+/99983209:11
opendevreviewMerged openstack/neutron-vpnaas master: Remove dead variable TEMPLATE_PATH  https://review.opendev.org/c/openstack/neutron-vpnaas/+/99985709:11
opendevreviewMerged openstack/neutron master: Add agnostic WSGI support for API worker election and identification  https://review.opendev.org/c/openstack/neutron/+/99566609:21
opendevreviewMerged openstack/neutron master: Add mod_wsgi support to ``get_api_worker_count()``  https://review.opendev.org/c/openstack/neutron/+/99580009:21
opendevreviewLajos Katona proposed openstack/neutron-vpnaas master: Rally changed in the past how plugins can import  https://review.opendev.org/c/openstack/neutron-vpnaas/+/100041709:21
opendevreviewMerged openstack/neutron-vpnaas master: Remove dead method ``add_ipsec_connection``  https://review.opendev.org/c/openstack/neutron-vpnaas/+/99985809:21
opendevreviewMerged openstack/neutron-vpnaas master: Remove empty OVN process subclasses  https://review.opendev.org/c/openstack/neutron-vpnaas/+/99985909:21
opendevreviewMerged openstack/neutron-vpnaas master: vpn: fix misleading ``os.path.join()`` with absolute path  https://review.opendev.org/c/openstack/neutron-vpnaas/+/99986109:21
opendevreviewMerged openstack/neutron master: Make ``get_start_time()`` server-agnostic  https://review.opendev.org/c/openstack/neutron/+/99580209:24
opendevreviewMerged openstack/neutron-vpnaas master: Remove unused ``debtcollector`` and ``oslo.serialization`` deps  https://review.opendev.org/c/openstack/neutron-vpnaas/+/99986210:07
opendevreviewMerged openstack/neutron-vpnaas master: Register ``libreswan_opts`` in config sample generator  https://review.opendev.org/c/openstack/neutron-vpnaas/+/99987210:26
tbachmanHi neutron devs! Just an FYI: I've updated both the bug in launchpad and my patch re: HPB10:41
tbachmanhttps://bugs.launchpad.net/neutron/+bug/216275210:41
tbachmanhttps://review.opendev.org/c/openstack/neutron/+/99493610:42
tbachmanThe bug contains a little longer description of the issue.10:42
opendevreviewMerged openstack/neutron master: Add ASGI worker count support to wsgi_utils  https://review.opendev.org/c/openstack/neutron/+/99516211:13
lajoskatonaslaweq, haleyb: Hi, I have a patch series for migrating taas to OVO: https://review.opendev.org/q/topic:%22bug/2150209%22 if you have time please check it (based on slaweq's similar work for fwaas)11:15
lajoskatonaI also started to push patches for other stadiums to migrate them to OVO:11:16
lajoskatonavpnaas: https://review.opendev.org/q/topic:%22bug/2150206%2211:16
lajoskatonan-d-r: https://review.opendev.org/q/topic:%22bug/2150207%2211:16
lajoskatonabut these are under construction currently11:16
opendevreviewLajos Katona proposed openstack/neutron-vpnaas master: Rally scenario plugin API changed  https://review.opendev.org/c/openstack/neutron-vpnaas/+/100041711:23
*** LarsErik1 is now known as LarsErikP12:18
slaweqlajoskatona: sure, I will check them 12:28
lajoskatonaslaweq: thanks12:29
haleyblajoskatona: ack, can look after meeting13:00
haleyb#startmeeting networking13:00
opendevmeetMeeting started Tue Aug 11 13:00:22 2026 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
opendevmeetThe meeting name has been set to 'networking'13:00
haleybPing list: bcafarel, elvira, frickler, mlavalle, mtomaska, slaweq, ykarel, lajoskatona, jlibosva, haleyb, ralonsoh13:00
* fungi is around for his topic13:00
lajoskatonao/13:00
mlavalle\o13:01
ykarelo/13:01
mtomaskao/13:01
haleyb#topic announcements13:01
haleybwe can get started13:01
bcafarelo/13:01
haleybWe are currently in Week R-7 of Hibiscus13:02
haleybWeek R-5 is the Hibiscus- milestone (August 24th)13:02
haleyb#link https://releases.openstack.org/hibiscus/schedule.html13:02
haleybthis is the release countdown email13:02
lajoskatonasomebody else is older again....13:02
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/N6IA4TYCGVI5OE3JK7WXKSLVEOFLYCBH/13:02
haleyblajoskatona: is there a happy birthday?13:03
lajoskatonano, just nearly over another cycle :-)13:04
haleybah, yes, will it be 34 releases?13:04
lajoskatonaaround that as I count13:05
haleybi'll have a toast to one more year then :)13:06
haleyb2027.1 election nominations opened last week13:06
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/FDPHRND5ZM4CTGRXLGAQD7FGHK5NE34G/13:07
haleybCandidates interested in serving for the next calendar year (TC), or development cycle (PTL) should announce their candidacies and platforms during this week. Please see the Election site for specific timing information13:07
haleyb#link https://governance.openstack.org/election/13:07
haleyblet me know if anyone has any interest in being PTL (again), otherwise I'll be happy to stay on another cycle13:08
haleybthe other thing coming up is the PTG13:10
haleyb"Indri" PTG October 12-16, 202613:10
haleybPTG Website: https://openinfra.org/ptg/13:10
haleybi signed-up Neutron, will link the etherpad once it's created13:11
lajoskatonathanks13:11
haleybi had added an item on the Neutron user survey revisions from slaweq, but now see he added a topic in on-demand so we can talk about that then13:12
haleybReminder to please use the priority dashboard for anything neutron/networking related13:12
haleyb#link https://tinyurl.com/59z278km13:12
haleybRP +1 for "ready to merge" changes, RP +2 for gate blockers and similar13:12
haleybnothing in the +2 list at the moment which is good13:13
haleybthat was all i had for announcements, is there anything else?13:13
haleybReminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers13:13
haleybthere is nothing new on the list at the moment, will send email thursday night if canceled13:14
haleyb#topic bugs13:15
haleybotherwiseguy was the deputy last week, but i did not see an email13:15
haleybguess i could have run the new script to generate a summary13:16
haleybare there any bugs people want to discuss?13:16
haleybfrom what i'm remembering by looking most have owners and/or patches proposed, can go through them later13:18
haleybthis week mtomaska is the deputy, next week is bcafarel - is that ok for both of you?13:18
* bcafarel sets a reminder for next week13:19
bcafarelgood for me!13:19
haleybgreat, thanks!13:19
haleybhopefully it's ok for miro as well13:20
haleyb#topic specs13:20
haleyb#link https://review.opendev.org/q/project:openstack/neutron-specs+status:open13:20
haleybthe port group security group rules spec was updated last week13:21
haleyb#link https://review.opendev.org/c/openstack/neutron-specs/+/98778613:21
haleybi'll look again and encourage others that have commented to do the same13:21
haleybthere are a couple of others needing updates13:22
haleyb#topic community goals13:22
haleybthere are a few active series here13:22
haleyb#link https://review.opendev.org/q/topic:%22sdk_for_neutron%2213:22
haleybthis is the set of nova patches to move to the sdk13:23
lajoskatonaslow progress on the SDK side to have fields=[name, etc] filtering for Neutron resources13:23
lajoskatonahttps://review.opendev.org/c/openstack/openstacksdk/+/99572413:23
slaweqI will review port group spec tomorrow as I see that my previous comments seems to be addressed already13:23
haleybslaweq: ack, thanks13:24
haleyblajoskatona: ok, so that's needed for the nova changes?13:24
lajoskatonayes, to have the same optimization that we have in neutronclient, and fetch only the necessary fields 13:25
lajoskatonafrom Neutron API13:25
haleybright, i see the first i the series depends on it now13:26
haleybso we should prioritize, i can look later13:26
lajoskatonayes, I tested locally, and I can go through the series when there is an SDK release with it13:26
haleybgreat, and i can rebase mine in that series once i see you push updates13:27
haleybthanks again for working on this13:27
haleybnext series is for your heat changes13:28
haleyb#link https://review.opendev.org/q/topic:%2522neutron_openstacksdk%252213:28
lajoskatonaI have some review from Takashi/tkajinam, so kind of progress, I have to find the hiding other Heat core to push it :-)13:29
haleybi can go through that later this week, but don't have +2 there :(13:29
haleybthis one is closer13:30
haleyb#link https://review.opendev.org/q/topic:%2522migrate_stadium_osc%252213:30
haleybjust two changes left :)13:30
lajoskatonaI have to go and fix the osc patch as the SDK for onboard subnets were merged13:30
haleyb#link https://review.opendev.org/c/openstack/python-openstackclient/+/99599113:31
lajoskatonaafter that as I remember the logging is the only thing to move13:31
lajoskatonaif we don't count sfc13:32
haleybyes, i need to start the networking-sfc removal13:32
opendevreviewMerged openstack/neutron-tempest-plugin master: Skip broken network segment range update test  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/100036413:32
lajoskatonaI think that's all for the SDK related topics13:33
haleyb#link https://docs.openstack.org/project-team-guide/repository.html#deprecating-a-repository13:33
haleyblajoskatona: yes, thanks for updates13:33
haleybfinal community topic is the tenant_id removal work13:33
haleyb#link https://review.opendev.org/q/topic:%22neutron-project-id-migration%2213:33
haleybit's a little stuck waiting for the nova series above to merge13:34
haleybi haven't found a way to get around that yet, will throw some credits at it later13:34
lajoskatonacan't you remove the dependency and at least the tenant_id removal can progress ?13:35
haleybat this point i'll likely defer merging anything until 2027.113:35
haleyblajoskatona: the one neutron change? let me find it13:35
lajoskatonaack13:35
haleyb#link https://review.opendev.org/c/openstack/neutron/+/98696113:36
haleybi think that's the one you're talking about13:36
haleybmy only worry is breaking something at the end of the cycle with only 7 weeks left, don't mind breaking things at beginning of next one13:37
lajoskatonaI think yes13:37
haleybwell, i don't want to break anyone, but there's not a lot of runway left :)13:38
lajoskatona+1, we are really close to the end of cycle13:38
haleybi did get some feedback on my tempest patch, i'll work on merging that since it's a dependency13:39
haleybthat's all i had on that for the moment13:39
haleyb#topic on-demand13:40
opendevreviewEduardo Olivares proposed x/whitebox-neutron-tempest-plugin master: Fix IGMP snooping test failure after OVS restart  https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/100041313:40
haleybthere were a few topics in the on-demand section13:40
haleybfungi: you are first on the list13:40
fungithis was for the "bridging the gap" gazpacho cycle retrospective followup discussion13:40
fungibriefly revisiting this topic from a few weeks back, now that folks have hopefully had time to digest it better... i've got more that came out of a closer look into the data but also wanted to see if anyone had additional thoughts13:41
fungisomething i missed calling out is that the average time to response on reviews improved noticeably in gazpacho compared to flamingo; changes got reviewed 23% faster on average (mean), though the typical (median) response time held steady13:41
fungiif the team's reviewing habits have been changing that would be something to continue as it seems to have made a some impact, in fact the average time to review has trended faster for at least the past 5 cycles (halving since bobcat)13:41
fungifairly impressive given that the active maintainer count has also fallen steadily cycle after cycle and you're still essentially closing as many changes as are being opened each cycle13:41
fungiwe had takeaway suggestions, some similar to the previous round... contributors still aren't clear on where maintainers are tracking review priorities, so continuing to work on addressing that communication gap may help13:41
fungithere may also be some communication breakdown in the review process, since maintainers felt the contributors weren't following their guidance while at the same time contributors felt some review feedback they were getting wasn't useful13:41
fungiit might be that many people are not finding or understanding the project's contributor documentation, or don't remember to refer to it, so finding ways to get it in front of them better could help13:41
fungialso the change and reviewer numbers are growing while the active maintainer count is falling, so if possible try to find some time to evaluate new maintainer candidates from the pool of established reviewers and code contributors13:42
fungiif anybody has follow-up thoughts or questions on any of the above, as well as for the survey and metrics analysis from last week now that you've had time to mull it over, i'm happy to answer questions and entertain feedback here13:42
fungi(or in the #openstack-neutron irc channel after the meeting, or on the openstack-discuss mailing list, or even directly/in private for that matter)13:42
fungiand if there are no questions, i'll yield the floor to other topics13:43
haleybthanks for the feedback there13:43
haleybi think they are all valid points, we can definitely add things to PTG discussions13:44
fungii'm also happy to join ptg sessions about this sort of stuff, just let me know13:45
haleybfungi: i don't remember exactly, but how many people provided input?13:45
fungineutron had 3 contributors and 1 maintainer fill out surveys13:45
haleybright13:45
fungithough the metrics were based on evaluation of all official neutron deliverable repository activity13:45
fungiobviously if more neutron contributors and maintainers can be encouraged to fill out the hibiscus surveys, that will help us draw better conclusions too13:46
haleybright, statistics :)13:46
fungiwe'll be evaluating those right after the ptg this time, so it's an opportunity to remind everyone13:47
haleybat least one of those, priority tracking, is addressed via our dashboard, but if i'm remembering correctly, only cores can set those flags13:47
fungi(surveys will be opening during rc1 week, is the current plan)13:47
haleybit could be opening-up that to anyone will allow people to put something on the RP +1 list (i.e. ready to go)13:48
fungiwe're still finalizing the questions for the hibiscus surveys, trying to make them focus a little more on identifying maintainer burn-out and also gauging contributor interest in helping with maintenance tasks13:48
cardoeI'll throw out as a contributor (and operator), the neutron team has been pretty responsive and helpful relative to other OpenStack projects so I want to say thank you.13:49
haleybfungi: i think we'll also be working on AI-in some of the maintenance tasks as we do the same things every cycle...13:49
fungiyes, i think the metrics we collected bear out cardoe's kudos too, sadly survey bias tends to focus responses on negative experiences rather than positive, so having hard numbers to analyze helps balance that out13:50
fungihaleyb: all interesting ideas, looking forward to seeing what the team comes up with13:51
haleybcardoe: thanks for saying that, i do know everyone here tries pretty hard on getting things reviewed/merged13:51
haleybi'll have to remind everyone to fill-out the survey to get a better view13:52
haleybalright, there were a couple of other topics on the list13:52
haleybmlavalle: you added one on your review series13:52
mlavalleThe series of patches implementing routed networks with multiple segments for ML2/OVN are ready for the next round of reviews. All the reviewers comments have been addressed. There are 4 patches that start here: https://review.opendev.org/c/openstack/neutron/+/99560813:52
mlavallethat's all13:53
mlavallereviews are needed13:53
haleybmlavalle: ack, it's on my list, probably on others as well, thanks for working on it!13:53
haleybslaweq: and you had a topic on the user survey revision(s)13:54
haleyb#link https://etherpad.opendev.org/p/OpenStack-User-Survey-2026-Neutron-updates13:54
slaweqyes, thx13:54
slaweqI already sent email about it13:55
cardoemlavalle: I'll review it as well since I use segments quite a bit for the physical networks.13:55
haleybDeadline for this is Aug 24th so please review before Aug 21st13:55
slaweqI did took a look at the questions from the survey and I have proposed changes to those13:55
mlavallecardoe, thnaks13:55
haleybslaweq: ack, thanks13:55
slaweqI wanted to ask al of you to take a look at those my proposals of changes and provide feedback in the etherpad13:55
slaweqI think that it could be good to simplify it a bit and limit numer of possible answers in some questions13:56
slaweqthat's all13:56
slawequnless anyone have any questions or comments now so I am open to talk about it13:56
lajoskatonathanks slaweq, I checked the etherpad but will read it again to comment on it13:57
haleybgreat thanks will take a look13:57
slaweqthank You13:57
haleybcardoe: you mentioned you had a topic13:57
cardoeI was hoping we could get py.typed added on neutron-lib before the final release for this cycle. I know there's not a lot of typing in there but as stephenfin said we don't need it all typed.13:58
cardoeBut we could start pulling that in for type checking as an optional opt-in.13:58
cardoeWith a goal of getting more of it typed for the next release.13:59
haleybcardoe: i don't have a problem moving forward with typing, is there a series for it you can link here?14:00
haleyband maybe we can get on the priority dashboard14:00
cardoeThere's been a few patches around confusion of what a field is between neutron and neutron-lib. Like tbachman's bug/patch that he's been talking about relates to that. The field on PortContext is sometimes a "Network" DB obejct and sometimes it's a NetworkContext and it would be good to nail down which that is.14:00
cardoeI can put together a series by putting the same topic on some patches. There's a number of folks that have made one offs for types. Give me just a bit and I'll ping you with it.14:01
tbachmanFWIW - my bug and patch: https://bugs.launchpad.net/neutron/+bug/2162752 https://review.opendev.org/c/openstack/neutron/+/99493614:01
haleybcardoe: right, maybe create a topic if there isn't one already14:01
cardoeWill do14:02
haleybhttps://review.opendev.org/q/topic:%22type_tooling%22 - that was an old one14:02
haleybbut feel free to make a new one, doesn't matter to me14:02
cardoeThe other ask was to add https://review.opendev.org/c/openstack/neutron/+/998562 to RP.14:02
haleybok, we are over time14:02
haleybcardoe: ack, will do14:03
cardoeI'll make a new topic and pull the patches together and ping you haleyb.14:03
haleybthanks everyone for attending, and have a great week!14:03
haleyb#endmeeting14:03
opendevmeetMeeting ended Tue Aug 11 14:03:25 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:03
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2026/networking.2026-08-11-13.00.html14:03
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2026/networking.2026-08-11-13.00.txt14:03
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2026/networking.2026-08-11-13.00.log.html14:03
mlavalle\o14:03
lajoskatonao/14:03
haleyblajoskatona: hey, if you have a minute can you look at https://review.opendev.org/c/openstack/neutron/+/999831 ? 2024.1 cherry-pick, tia14:20
opendevreviewDoug Goldstein proposed openstack/neutron master: Use separate VNI and VLAN physnets in VNIVLANAllocator  https://review.opendev.org/c/openstack/neutron/+/100048214:34
opendevreviewDoug Goldstein proposed openstack/neutron master: Use separate VNI and VLAN ScopedRanges in VNIVLANAllocator  https://review.opendev.org/c/openstack/neutron/+/100048514:36
cardoetwo different approaches... the bottom one is a bigger change but provides a more exacting API. Since that whole file and it's APIs were introduced this cycle I'm hoping we can fix it before a release happens so that there's no breakage.14:37
opendevreviewLajos Katona proposed openstack/neutron-vpnaas master: Rally scenario plugin API changed  https://review.opendev.org/c/openstack/neutron-vpnaas/+/100041715:06
opendevreviewMerged openstack/neutron master: Re-set BGP bridges on Chassis_Private after ovn-controller restart  https://review.opendev.org/c/openstack/neutron/+/99927915:46
opendevreviewMerged openstack/neutron master: BGP job: enable more tempest scenarios and cross-compute scheduling  https://review.opendev.org/c/openstack/neutron/+/99816215:46
opendevreviewMerged openstack/neutron unmaintained/2024.1: Fix accidental removal of router external gateway info  https://review.opendev.org/c/openstack/neutron/+/99983116:12
opendevreviewElvira García Ruiz proposed openstack/neutron master: Manage PVLAN PGs in OVN after PVLAN plugin is enabled or disabled  https://review.opendev.org/c/openstack/neutron/+/99818416:14
opendevreviewFiorella Yanac proposed openstack/neutron-tempest-plugin master: Add PVLAN cold migration scenario test  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/99852316:18
opendevreviewMerged openstack/neutron master: [CI] Bump swap cs10 fips job  https://review.opendev.org/c/openstack/neutron/+/99973217:12
opendevreviewFiorella Yanac proposed openstack/neutron-tempest-plugin master: Add PVLAN cold migration scenario test  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/99852317:28
opendevreviewBrian Haley proposed openstack/neutron master: Fix use-dict-literal pylint warnings  https://review.opendev.org/c/openstack/neutron/+/100064821:07

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