- openstack-discuss - lists.openstack.org

April 2026 PTG Team Signup Kickoff
by Kendall Nelson 15 Feb '26

15 Feb '26

Hello Everyone! The next OpenInfra PTG[1] will take place April 20-24, 2026 and registration for the event is now open[2]! For those new to the community, or perhaps just need the reminder, the PTG is a semi-annual event where project teams come together to hash out important details for the next six-ish months during a concentrated set of meetings that often include code sprints, bug fixing, design discussion, and cross project collaboration. To sign your team up, you must complete the survey[3] by March 1st at 7:00 UTC. If your team is not interested in participating, there is no need to fill out the survey. The contact information (email and preferably also IRC nickname) in the form will be used to share important details with moderators about team signup and further logistics. To ensure you receive all communications please double check and submit *ACCURATE* information! If you are not on IRC, please get on the OFTC network[4] and join #openinfra-events as much of the coordination for the event will be done in the #openinfra-events channel. You are also encouraged to familiarize yourself with the PTGBot documentation[5] as well. If you have any questions, please reach out to ptg(a)openinfra.org! Information about signing up for time slots will be sent to moderators shortly after the team signup deadline. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.org/ptg/ [2] PTG Registration: https://ptg.openinfra.org/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/apr2026_ptg_survey [4] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [5] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 1

February 4 Meeting Recap & Next Steps
by Kendall Nelson 15 Feb '26

15 Feb '26

Hello folks! Thank you for all your participation thus far - watching the previous recording, answering the last poll, attending the meetings, etc. Here is the recording from today's meeting for those that were unable to attend it live: https://zoom.us/rec/share/9vo8njF87mFdFQhsYdZzYBrY3DSfeuo5t2EJIxMdV4CCtslQs… If you do watch, I would encourage you to add your name and details to the etherpad where we took notes on today's meeting: https://etherpad.opendev.org/p/Digital-Sovereignty-WG The next meeting date and time is to be determined by you all! Here is the poll to vote <https://beta.framadate.org/polls/fe703653fdd969cbdaf4/1e0eba4bc789b7067aa1/…> on a date/time between Feb 17th, 18th, and 19th. *I will set the deadline to vote for the end of the previous week - February 13. * Lastly, I want to remind folks of the homework we discussed on the call - using some of the words and phrases we brainstormed (and any others that get added) to craft a stance on why OpenInfra and our projects are able to support digital sovereignty. For more information on this discussion, please watch the recording of the recent meeting. Thanks! -Kendall

1 4

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2026.1/R-6)
by Goutham Pacha Ravi 15 Feb '26

15 Feb '26

Hello Stackers, We're 6 weeks away from the date of the coordinated release of OpenStack 2026.1 "Gazpacho" [1]. We have a number of release deadlines scattered between this week and next, so it's an extremely busy time for project maintainers and our release management team. The nomination window for the combined TC and PTL elections is also closing this week (at 23:45 UTC on February 18, 2026) [2]. At last count, there were 27 project teams that still needed a PTL nominee. If you'd like to volunteer to be a PTL or if you think someone else should be, please ensure a nomination is submitted prior to the deadline. If you have questions regarding the process, please feel free to ask them on this mailing list or in the #openstack-election IRC channel on OFTC. The substantive governance activity in the past week was around the CI fixes concerning the regression in setuptools [3]. We've had to resurrect some "x-static" repositories in order for the OpenStack Dashboard project team to work around the changes from the upstream Python community. We're beginning to define the tested runtimes for the OpenStack 2026.2 "Hibiscus" release cycle [4]. Please take a look and give us your feedback. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee was held over IRC on February 10, 2026 [5]. We focused on our past action items, technical debt, and the ongoing election cycle. We have officially closed the chapter on Monasca by abandoning 173 open changes across several repositories, and conversely, we’re seeing a promising revival of Cyborg with a new PTL nominee and a fresh team structure. In the hope of staffing project teams that have a large cross-project impact, we've proposed PTL nomination directories for the Requirements and Oslo teams not just to solicit candidates, but to spark a discussion on how we better support these critical dependencies. We discussed navigating a "borked" gate due to the recent setuptools' pkg_resources deprecation [3]. While we are currently merging "band-aid" pins to restore CI stability on stable branches, the situation would have been significantly worse without the proactive work done by Stephen Finucane (stephenfin) and Takashi Kajinami (tkajinam) over the last few months. Their foresight has saved project teams from a much larger headache during the feature freeze rush that's underway. Finally, we called out to project teams to review the User Survey streamlining plan [6]. Our goal is to refine this feedback loop prior to the PTG in April [7] so we can make timely improvements. The next meeting of the OpenStack Technical Committee is on Tuesday, February 17, 2026. This meeting is being held at 0800 UTC, a time that's better suited for our contributors in the Eastern Hemisphere. Please feel free to add to the agenda on the meeting's wiki page, and thank you in advance for your participation [8]. === Governance Proposals === ==== Merged ==== - Add a script to abandon changes on retired repositories | https://review.opendev.org/c/openstack/governance/+/975594 - Onboard additional xstatic packages | https://review.opendev.org/c/openstack/governance/+/976513 ==== Open For Review ==== - Define testing runtime for 2026.2 release | https://review.opendev.org/c/openstack/governance/+/976691 - Revert "Revive os_monasca" | https://review.opendev.org/c/openstack/governance/+/974775 === Upcoming Events === - 2026-02-26: 2026.1 "Gazpacho" Feature Freeze / Milestone 3 - 2026-03-10: OpenInfra Board Meeting: https://board.openinfra.org/ - 2026-03-23: KubeCon+Cloud Native Con EU begins: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/ - 2026-04-20: OpenInfra PTG begins: https://openinfra.org/ptg/ === How to Contact the TC === You can reach the TC in several ways: 1. Email: send an email with the tag [tc] on this mailing list. 2. Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC. 3. Join us at our weekly meeting: The Technical Committee meets every Tuesday at 1700 UTC, except the third Tuesday of the month, when we meet at 0800 UTC [8]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2026.1 "Gazpacho" Release Schedule: https://releases.openstack.org/gazpacho/schedule.html [2] OpenStack "2026.2" Elections: https://governance.openstack.org/election/ [3] setuptools regression: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [4] Tested runtimes for 2026.2: https://review.opendev.org/c/openstack/governance/+/976691 [5] TC Meeting IRC Log, February 10 2026: https://meetings.opendev.org/meetings/tc/2026/tc.2026-02-10-17.00.html [6] Streamlining the OpenStack User Survey: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [7] OpenInfra PTG: https://openinfra.org/ptg/ [8] TC Meeting Agenda, February 17 2026: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[all][elections][ptl][tc] Combined PTL/TC 2026.2 cycle Election Nominations Last Days
by Ian Y. Choi 13 Feb '26

13 Feb '26

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Feb 18, 2026 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at[1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. All members of the community are encouraged to confirm their email address and opt in to the CIVS election as described at: https://governance.openstack.org/election/#electorate Election statistics[2]: Nominations started @ 2026-02-04 23:45:00 UTC Nominations end @ 2026-02-18 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 5 days, 0:17:37 Nominations progress : 64.20% --------------------------------------------------- Projects[1] : 40 Projects with candidates : 13 ( 32.50%) Projects with election : 1 ( 2.50%) --------------------------------------------------- Need election : 1 (Horizon) Need appointment : 27 (Adjutant Barbican Cinder Cloudkitty Heat Keystone Masakari Mistral Neutron Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms Oslo Puppet_OpenStack Quality_Assurance Rally Requirements Skyline Storlets Sunbeam Swift Tacker Trove Venus Vitrage Zun) --------------------------------------------------- TC Candidates : 2 (5 Required) =================================================== Stats gathered @ 2026-02-13 23:27:23 UTC This means that with approximately 2 days left, 27 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.opendev.org/q/project:openstack/election+is:open+file:candid… have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[manila][election][ptl] Carlos da Silva Candidacy for 2026.2 PTL
by Carlos Silva 13 Feb '26

13 Feb '26

Hello, I would like to announce my candidacy for Manila PTL for the 2026.2 (Hibiscus) cycle. I have been serving as Manila PTL for the past couple of releases and am happily investing time and energy into working with this very talented and passionate group of contributors. Over these releases, we have been creating more and more opportunities for contribution, ranging from code to involving cloud users and operators in our discussions to collect feedback. This helps us deliver valuable enhancements and fixes. We still have lots to do, and that includes enhancing our contributor experience. Therefore, in the upcoming cycle, I would like to direct our focus to: Eventlet: python-manilaclient is successfully migrated. We are now completing the migration in the manila code base, so we will focus on finalizing it and testing the changes we are making while moving away from eventlet. Tech debt: Continue the efforts to reach parity between Manila APIs and Manila UI, and complete the rootwrap -> privsep migration. VirtioFS: Closing the scenario testing gap for VirtioFS. Mentorship: Continue shepherding and encouraging more active reviewer participation and preparing new core reviewers. Communication: Reshaping the way we communicate and document our team priorities. Thank you for your consideration. Carlos da Silva IRC: carloss

2 1

[release] Release countdown for week R-6
by Thierry Carrez 13 Feb '26

13 Feb '26

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non client library freeze" on February 19th, 2026. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2026.1 branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (February 26th, 2026) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, February 26th, 2026. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/2026.1 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2026.1 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2026.1 "Gazpacho" will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 19th, 2026 (R-6 week) Client library freeze: February 26th, 2026 (R-5 week) Gazpacho-3 milestone: February 26th, 2026 (R-5 week) Cycle Highlights Due: March 5th, 2026 (R-4 week) 2026.1 "Gazpacho" final release: April 1st, 2026 2026.2 "Hibiscus" (virtual) PTG: April 20-24, 2026 -- Thierry Carrez (ttx)

1 0

[neutron][ovn-bgp-agent] Fix for missing /etc/iproute2/rt_tables after iproute2 upgrade
by Maximilian Stinsky-Damke 13 Feb '26

13 Feb '26

Hi everyone, I wanted to bring attention to an issue that affects ovn-bgp-agent deployments after upgrading to newer versions of the iproute2 package. Problem: In newer iproute2 package versions, the default rt_tables file has been moved from /etc/iproute2/rt_tables to /usr. This change was introduced as part of iproute2's move to a "stateless" configuration pattern where configuration files are read from /etc first, falling back to /usr if they don't exist. You can see the related iproute2 commit here: https://github.com/iproute2/iproute2/commit/0a0a8f12fa1b03dd0ccbebf5f85209d… When iproute2 is upgraded on Rocky Linux (and other RHEL-based systems), if /etc/iproute2/rt_tables was modified, it gets moved to /etc/iproute2/rt_tables.rpmsave and the original file isn't recreated. See https://access.redhat.com/solutions/7123966 for more details. I suspect Debian-based systems have the same issue. The ovn-bgp-agent has a hard requirement on /etc/iproute2/rt_tables existing, which causes it to fail with a FileNotFoundError when it attempts to read the file: FileNotFoundError: [Errno 2] No such file or directory: '/etc/iproute2/rt_tables' The error occurs in ensure_routing_table_for_bridge() when the agent tries to check for existing routing table entries for bridges. Proposed Solution: I've proposed a fix that ensures the /etc/iproute2/rt_tables file exists before attempting to read it. The solution: 1. Creates a new privileged function ensure_routing_tables_file() that: - Creates the /etc/iproute2/ directory if it doesn't exist - Copies the default rt_tables file from /usr/share/iproute2/rt_tables to /etc/iproute2/rt_tables if the latter doesn't exist 2. Calls this function before reading rt_tables in ensure_routing_table_for_bridge() This approach maintains backward compatibility while handling the new iproute2 package structure gracefully. Bug Report: https://bugs.launchpad.net/ovn-bgp-agent/+bug/2141421 Proposed Patch: https://review.opendev.org/c/openstack/ovn-bgp-agent/+/976242 Has anyone else hit this issue? We didn't find any upstream fix for it yet, so we'd appreciate feedback on the patch. Thanks, Max

1 0

[neutron] Drivers meeting canceled Friday, February 13th
by Brian Haley 12 Feb '26

12 Feb '26

Hello Neutrinos: I am going to cancel tomorrow's Drivers meeting as there are no topics on the agenda. Just a reminder that our open spec list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

[charms][sunbeam] Proposing Ahmad Hassan for sunbeam-core
by Guillaume Boutry 12 Feb '26

12 Feb '26

Hi all, Ahmad has been working for a year actively on Sunbeam charms and has proven to be an able reviewer and contributor. I'd like to propose Ahmad as a member of the sunbeam-core team. Cheers, Guillaume

3 2

[tc][election] gouthamr's TC Candidacy for 2026.2
by Goutham Pacha Ravi 11 Feb '26

11 Feb '26

Hello Stackers, I am submitting my candidacy for another term on the OpenStack Technical Committee. It's been two years since I was first elected, and I've served as TC Chair during this time. In these past two years, we've gotten some important things done: the CLA-to-DCO transition that our community asked for over a decade ago, extending the VMT's mandate to all project teams, setting clear expectations around project retirements and governance transitions, and consolidating our governance repositories. I'm proud of this work, and I'm running again because there's more to do. One thing that has become clear to me as Chair is that the people who keep OpenStack running by fixing gates, reviewing code across projects, reporting and triaging bugs, maintaining infrastructure and other myriad things don't get enough recognition for it. I'm hoping to change that by creating an objective, tangible way to acknowledge valuable contributions and enthuse our community to do more of this work. We are one of the largest open source projects in the world, and the community that's responsible for it is a bedrock needs constant care. I also want the TC to stay engaged with where cloud infrastructure is headed. OpenStack should be the free and open source choice for Sovereign Clouds and AI workloads. We'd do this not by chasing trends, but by ensuring our project teams are equipped and positioned for these use cases as they mature. On the governance side, I'll keep working to eliminate bottlenecks that slow our project teams down while maintaining the consistent maintenance model that has made our successful projects sustainable. The Technical Vision for OpenStack Clouds hasn't been modified in a while, and I'd like to help draft its next iteration. I'll take the opportunity to also include a process for evolving it. Lastly, two years on the TC have shown me how much we benefit from experienced, engaged leaders across our projects. I want to build mentoring pathways for future TC members, so our leadership pipeline is as durable as the software we produce. Thank you for your consideration. Goutham Pacha Ravi (gouthamr) Affiliation: Red Hat Inc. OpenInfra Profile: https://openinfra.dev/a/community/members/35705 Nomination: https://review.opendev.org/c/openstack/election/+/976553

1 0