- openstack-discuss - lists.openstack.org

[all][election] Check your voting eligibility for the OpenStack PTL & TC elections
by Goutham Pacha Ravi 06 Feb '26

06 Feb '26

Hello Stackers, Election season is here, and we want to ensure every voice that helps build OpenStack is heard. I would like you to take a moment to verify your "Active Contributor" [1] and OpenInfra Foundation membership status so you don't miss your chance to vote. To receive a ballot for the OpenStack TC elections, you must be a contributor to OpenStack repositories _and_ hold the status of "OIF Individual Member." To receive a ballot for a PTL election, you must have contributed to any of a project team's repositories _and_ hold the status of "OIF Individual Member." Check your membership level: ======================== Log in to your profile at https://openinfra.org/a/profile. Even if you’ve been a member for years, the OpenInfra Foundation (OIF) has a policy that automatically downgrades memberships to "OIF Community Member" if you haven't voted in recent Governing Board elections [2]. Upon logging in, if you see that you are an "OIF Community Member," you can restore your "OIF Individual Member" status on that profile page. Get recognized as an "Active Contributor": ================================ While our policy traditionally focuses on contributors to OpenStack's git repositories, we know that impactful work happens far beyond just code and documentation. We definitely value the "intangible" work that keeps this community running. If you haven’t contributed code or documentation to a repository during the 2025.2–2026.1 timeframe (March 14, 2025 – February 18, 2026), you can still vote! Please reach out to the PTL or DPL liaison of the project team you’ve supported and request to be added as an "Extra AC" (Extra Active Contributor) today [3]. The deadline to do this is February 13, 2026. If you run into issues or have questions about your eligibility, the TC would be happy to help. Simply reply to this thread, or chime in on OFTC's #openstack-tc IRC channel. Thanks, Goutham Pacha Ravi (gouthamr) [1] "Active Contributor": https://governance.openstack.org/tc/reference/charter.html#voters-for-tc-se… [2] OIF membership page: https://openinfra.org/join/individual/ [3] Extra AC deadline: https://releases.openstack.org/gazpacho/schedule.html#g-extra-acs

5 6

[release] Release countdown for week R-7
by Thierry Carrez 06 Feb '26

06 Feb '26

Development Focus ----------------- We are entering the last weeks of the 2026.1 " Gazpacho" development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-AC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Contributor and allowed to vote. This is done by adding extra-acs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-AC freeze on February 12th. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * Oslo libraries are entering feature freeze next week, February 12th. * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 19th). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 26th) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 26th. Any feature addition beyond that date should be discussed on the mailing list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 12th) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 26th) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to one week after Feature freeze (March 5th). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… jeremy [at] openstack.org/fungi on IRC is available if you need help selecting or writing your highlights. Upcoming Deadlines & Dates -------------------------- Extra-AC freeze: February 12th, 2026 (R-7 week) Oslo feature freeze: February 12th, 2026 (R-7 week) 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 deadline: March 5th, 2026 (R-4 week) Hibiscus (virtual) PTG: April 20-24, 2026 -- Thierry Carrez (ttx)

1 0

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

05 Feb '26

Hello Neutrinos: I am going to cancel tomorrow's Drivers meeting as there are no topics and I will be out. 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

[kolla][cinder] strange behavior with 2 storage nodes
by Alexander Luedtke 05 Feb '26

05 Feb '26

Hello Everyone, I have an strange behavior here on an cinder installation deployed with Kolla: The Setup: - 1 Controller node - some compute nodes - 2 Storage nodes (storage0, storage2) - later it should be 3. both with NFS Setup what is working. both storage nodes are shown on Skyline. The Problem: 1. in Skyline both storage nodes are shown but both are shown with the same size of one of both. 2. When I created a Volume then it was created on the other host as shown (in DB, skyline and so on) Anyone an idea what I can do to correct this problems ? Thanks a lot for your help ! Alexander -- Alexander Luedtke Systemadministrator Technische Universität München TUM School of Computation, Information and Technology Chair of IT Security Garching Boltzmannstr. 3 Room 01.08.036 85748 Garching b. Muenchen Tel. +49 89 289 18039 www.sec.in.tum.de

1 1

[policy] Updating RBAC (policy-popup team) meeting time
by Ghanshyam Maan 04 Feb '26

04 Feb '26

Hello Everyone, I have a conflict at the current time, so I am rescheduling the RBAC meeting to an hour later. Monday, Monthly 17:00 UTC. -> Monday, Monthly 18:00 UTC. I will update the wiki and the ICS file. Details: https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… ICS File: https://meetings.opendev.org/#Secure_Default_Policies_Popup-Team_Meeting -gmann

1 0

[cinder] festival of reviews friday 2026-02-06
by Brian Rosmaita 04 Feb '26

04 Feb '26

Hello Argonauts, This is a reminder that the twice-monthly Cinder Festival of Reviews will be held at the end of this week on Friday 6 February. who: Everyone! what: The Cinder Festival of Reviews when: Friday 6 February 2026 from 1400-1600 UTC where: videoconf info on the etherpad etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews This recurring meeting, that happens on the first and third Friday of each month, can be placed on your calendar by using this handy ICS file: https://meetings.opendev.org/calendars/cinder-festival-of-reviews.ics See you there!

1 0

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

04 Feb '26

Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Feb 18, 2026 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/2026.2/<Project_Name or "TC">/<email_address> (for example, "candidates/2026.2/TC/stacker(a)example.org"). The name of the file should match an email address for your current Foundation Individual Membership. Take this opportunity to ensure that your Open Infrastructure Foundation member profile contains current information: https://openinfra.org/a/profile Any Open Infrastructure Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an Open Infrastructure Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Feb 25, 2026 23:45 UTC through to Mar 18, 2026 23:45 UTC. The electorate for the TC election are the Open Infrastructure Foundation Individual Members who have a code contribution to one of the official teams over the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 00:00 UTC, as well as any Extra ACs who are acknowledged by the TC. The electorate for a PTL election are the Open Infrastructure Foundation Individual Members who have a code contribution over the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ACs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ACs. Please find below the timeline: PTL + TC nomination starts @ Feb 04, 2026 23:45 UTC PTL + TC nomination ends @ Feb 18, 2026 23:45 UTC TC campaigning starts @ Feb 18, 2026 23:45 UTC TC campaigning ends @ Feb 25, 2026 23:45 UTC PTL + TC elections start @ Feb 25, 2026 23:45 UTC PTL + TC elections end @ Mar 18, 2026 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2026-02-18 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and Foundation individual member profiles can be updated at https://review.opendev.org/#/settings/contact and https://openinfra.org/a/profile accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials

1 0

[nova][ci] nova-next job is failing 100%
by melanie witt 04 Feb '26

04 Feb '26

Hey all, Just a heads up that we currently have a 100% fail rate broken nova-next job due to the following bug: https://bugs.launchpad.net/cinder/+bug/2127196 Fixes on both the Cinder and Nova side are proposed: * https://review.opendev.org/c/openstack/cinder/+/975540 * https://review.opendev.org/c/openstack/nova/+/975542 Please hold your rechecks until at least one of these patches is merged. Cheers, -melwitt

1 1

[qa][ptg] Call for 2026.2 vPTG QA topic
by Ghanshyam Maan 04 Feb '26

04 Feb '26

Hi All, I have created the etherpad to collect the QA topics for the coming vPTG (2026.2 cycle). Based on the topics, we will decide if we need any slots in PTG. Seeing the PTG signup deadline, please add your topics before Feb 17th so that we can discuss the same in Feb 18th QA office hour. - https://etherpad.opendev.org/p/qa-2026.2-ptg -gmann

1 0

[all][elections][ptl][tc] Combined PTL/TC 2026.2 cycle Election Season
by Ian Y. Choi 04 Feb '26

04 Feb '26

Election details: https://governance.openstack.org/election/ The nomination period officially begins Feb 04, 2026 23:45 UTC. Please read the stipulations and timelines for candidates and electorate contained in these governance documents[1][2][3]. Due to circumstances of timing, PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. Similarly, there will only be a TC poll if there are more than 5 candidates stepping forward the available TC positions. All members of the community are encouraged to confirm their email address as described at: https://governance.openstack.org/election/#electorate All candidates and prospective voters need to make sure they have reestablished their individual memberships in the Open Infrastructure Foundation https://openinfra.org/a/renew-membership (if this URL redirects you to your profile page, your membership is already renewed and nothing more is required), otherwise their nominations won't be verified and ballots will not be sent. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you wish to discuss in private please email any of the election officials[4] so that we may address your concerns. Thank you, [1] https://governance.openstack.org/tc/reference/charter.html [2] https://governance.openstack.org/tc/reference/role-of-the-tc.html [3] https://docs.openstack.org/project-team-guide/ptl.html [4] https://governance.openstack.org/election/#election-officials

1 0

[ironic] A first-class physical location API?
by Jay Faulkner 03 Feb '26

03 Feb '26

Something I've seen come up in a few discussions over the last couple of cycles is the need for Ironic to contain more useful information about the physical world. It's made me wonder if there's an opportunity to add bigger support for physical characteristics/locations? I'm thinking metadata like: - Datacenter the server is in - Computer room (or other DC subdivision) - Row - Rack - Slot # - Physical cabling (e.g. what switches you might be connected to and how) Do other folks see this need? I'm trying to tease out if there's something here or not, so just curious about use cases and what people think. -Jay

4 5

[tc][ptls] Streamlining the OpenStack User Survey
by Allison Price 03 Feb '26

03 Feb '26

Hi everyone, Today in the OpenStack TC meeting, I shared the intention of streamlining the OpenStack User Survey[1] in an effort to increase participation while still preserving the valuable insights we get from the responses. As a next step, I wanted to share an etherpad[2] with some context on what we are trying to achieve with this process as well as some pointed questions to help guide us as we make changes to improve the survey. If you have taken or reviewed the results of the OpenStack User Survey, please share your insights. This is an incredibly valuable tool and I want to ensure that any changes that we make are intentional and can help support the upstream community. I know everyone is in the middle of 2026.1 Gazpacho work, so we have some time. If possible, I would like to have as much input as possible in the etherpad by April 15 so we can then use the upcoming virtual PTG[3] to go through the responses and make a plan. Then, we can implement the changes in August 2026 for the next version of the survey. If you have any questions or would like to ensure you’re a part of this process, please let me know. I will send reminders as we get closer to the PTG. Thanks, Allison [1] https://www.openstack.org/user-survey [2] https://etherpad.opendev.org/p/OpenStack-User-Survey-Streamlining [3] https://openinfra.org/ptg

1 0

[neutron] IPv6 DVR for OVN - Seeking feedback on patch review prospects
by Maximilian Stinsky-Damke 03 Feb '26

03 Feb '26

Hello, I'm reaching out about the IPv6 DVR feature for OVN (bug #1998609: https://bugs.launchpad.net/neutron/+bug/1998609) and the associated patch (https://review.opendev.org/c/openstack/neutron/+/867513) As noted in the bug comments, Roberto Bartzen Acosta maintained this patch across multiple release cycles, but it hasn't received reviews from core maintainers and is currently blocked by merge conflicts. Roberto mentioned that the feature hasn't been getting traction despite the work put in. This feature would enable distributed routing for IPv6 GUA addresses in OVN deployments, similar to how IPv4 FIPs work with DVR today. The spec was approved and merged (https://review.opendev.org/c/openstack/neutron-specs/+/867979) indicating community interest. Before I invest time rebasing the patch and resolving merge conflicts, I'd like to understand: 1. Are there technical or architectural concerns that have prevented review? 2. Is there a reason this hasn't been prioritized, or is it a matter of reviewer availability? 3. Would core maintainers be willing to review if the patch is rebased and updated? I'm happy to do the rebase work, but I'd prefer not to spend time on something that won't be merged. Any guidance on the status and viability of this feature would be appreciated. Thanks, Max

2 5

OVN issues
by engineer2024 03 Feb '26

03 Feb '26

HI, I am trying to setup an extport host to act as host for an sriov vm IP. Set it up using ovs-vsctl set Open_vSwitch . external_ids:ovn-cms-options=enable-chassis-as-extport-host But when a vm is created with this sriov port, it is not able to reach the metadata service at 169.254.169.254. Inside the vm vm:~# ip r 10.1.0.0/24 dev ens5 proto kernel scope link src 10.1.0.20 169.254.169.254 via 10.1.0.12 dev ens5 proto dhcp src 10.36.160.60 metric 100 On the node marked as the extport host for this vm's ip, its ovn-controller log shows --------- 2026-01-29T11:52:26.922Z|00069|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf up in Southbound 2026-01-29T11:52:27.849Z|00070|binding|INFO|Releasing lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf from this chassis (sb_readonly=0) 2026-01-29T11:52:27.851Z|00071|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf down in Southbound 2026-01-29T11:52:28.480Z|00072|binding|INFO|Claiming lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf for this chassis. 2026-01-29T11:52:28.480Z|00073|binding|INFO|a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf: Claiming fa:16:3e:f3:82:f9 10.1.0.20 2026-01-29T11:52:28.482Z|00074|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf up in Southbound 2026-01-29T11:52:29.486Z|00075|binding|INFO|Releasing lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf from this chassis (sb_readonly=0) 2026-01-29T11:52:29.489Z|00076|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf down in Southbound ------------ It is fluctuating intermittently and not stable. Why is this flapping ? Also the metadata proxy is running fine on the extport host ip netns exec ovnmeta-7d9a4c21-1e6f-4f2b-9a84-3c8e1b7d62f0 telnet 169.254.169.254 80 Trying 169.254.169.254... Connected to 169.254.169.254. # ip netns exec ovnmeta-7d9a4c21-1e6f-4f2b-9a84-3c8e1b7d62f0 ss -ln | grep 80 tcp LISTEN 0 1024 169.254.169.254:80 <http://169.254.169.254/> 0.0.0.0:* # ps -ef | grep ovn-meta root 408634 1 9 11:52 ? 00:02:45 neutron-ovn-metadata-agent (/openstack/venvs/neutron-29.2.3/bin/python3 /openstack/venvs/neutron-29.2.3/bin/neutron-ovn-metadata-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_ovn_metadata_agent.ini) root 408673 1 0 11:52 ? 00:00:00 haproxy -f /var/lib/neutron/ovn-metadata-proxy/7d9a4c21-1e6f-4f2b-9a84-3c8e1b7d62f0.conf root 421770 388277 0 12:21 pts/12 00:00:00 grep --color=auto ovn-meta

2 1

[manila] Removal of the "manila" CLI
by Carlos Silva 03 Feb '26

03 Feb '26

Hello everyone, Following up on our deprecation of the manila shell client, we are officially announcing its removal in the 2026.1 Gazpacho release [1]. The legacy manila shell was first deprecated in the OpenStack Zed release. Since then, we have achieved full feature parity with our OpenStackClient (OSC) plugin. Moving forward, Manila will exclusively support the "openstack share" command set. No new features have been added to the legacy "manila" client since its deprecation, and it did not support recent API microversions. The manila executable will no longer be installed or supported. All management and provisioning tasks must be performed using the openstack CLI (e.g., openstack share create instead of manila create). If you are still using the "manila" command in your automation, CI/CD pipelines, or daily workflows, please migrate to the openstack CLI immediately. We appreciate your cooperation as we move toward a more maintainable OpenStack CLI experience. Regards, carloss [1] https://review.opendev.org/q/topic:%22bp/openstack-client-support%22+(statu…

1 0

[manila] Removal of the long deprecated "v1" API
by Carlos Silva 03 Feb '26

03 Feb '26

Hello everyone, After being deprecated for nearly a decade, the Manila V1 API is officially being removed from the codebase [1]. This effort will be completed in the 2026.1 Gazpacho release. Since the introduction of the Microversioned V2 API, V1 has been deprecated. However, to reduce technical debt and streamline our maintenance efforts, we are finally decommissioning it. In the Gazpacho release, the /v1 endpoint will cease to exist. While we sunset this API, please note that the /v2 API at micro-version 2.0 is identical to the /v1 API. Action Required: If you have legacy scripts or integrations still pointing to the V1 endpoint (which we do not expect at this point), please update them to use the V2 API immediately. [1] https://review.opendev.org/q/hashtag:%22remove-manila-api-v1%22+(status:ope… Regards, carloss

1 0

[neutron] Bug Deputy Report Jan 26 - Feb 01
by Yatin Karel 03 Feb '26

03 Feb '26

Hi Neutrinos, Below is the bug deputy report for last week:- Critical ====== - https://bugs.launchpad.net/neutron/+bug/2139271 - [FT] Failing test ``test_gateway_chassis_balanced_scheduling_multiple_gw_networks`` Fixed by Rodolfo High ==== - https://bugs.launchpad.net/neutron/+bug/2139143 - [OVN] ``_sync_ha_chassis_group`` fails if the current HCG has more than ``MAX_CHASSIS_IN_HA_GROUP`` HA_Chassis registers Assigned to Rodolfo Medium ====== - https://bugs.launchpad.net/neutron/+bug/2139586 - [whitebox-neutron-tempest-plugin] Metadata tests should be execute with OVN agent too Assigned to Rodolfo - https://bugs.launchpad.net/neutron/+bug/2139063 - Ensure no RPC clients are instantiated if ``rpc_workers=0`` Assigned to Rodolfo - https://bugs.launchpad.net/neutron/+bug/2139581 - Updating router state fails due to NoneType error Assigned to William Tripp Low === - https://bugs.launchpad.net/neutron/+bug/2139416 [doc] Document what changes are needed when changing supported Python version Unassigned Incomplete - https://bugs.launchpad.net/neutron/+bug/2139583 - neutron-openvswitch-agent native driver: Permanent flow loss after OVS restart due to unhandled 'unknown dpid' during rpc_loop Looks valid but requested more details -- Thanks and Regards Yatin Karel

1 0

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

02 Feb '26

Hello Stackers, We're 8 weeks away from the date of the coordinated release of OpenStack 2026.1 "Gazpacho" [1]. Next week is the feature freeze for OpenStack's Common Library projects ("oslo"), and this includes python-openstackclient and python-openstacksdk for this release. It's also the deadline for PTLs and DPL liaisons to propose additional names as contributors to OpenStack [2]. Please take this opportunity to credit folks who have been contributing to project maintenance without having any merged changes via Gerrit. Recording these individuals' contributions as "Active Contributors" acknowledges their effort and allows them to vote in the upcoming elections. Speaking of elections, the nomination period for TC and PTL elections begins this week. If you intend to contest these elections, please do submit your candidacy [3]. In the past week, the OpenStack Technical Committee began updating projects that followed the "Distributed Leadership" model during the 2026.1 "Gazpacho" release cycle. The release management team has opted to govern itself using the distributed leadership model and has retained the liaisons. The Watcher project has decided to move to the PTL model, and its PTL will be elected in the upcoming elections. We're awaiting decisions from the Ironic, Requirements, Freezer, and Oslo projects. Please review the open governance patches to help these teams make appropriate governance decisions. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee was hosted on January 27th, 2026 in OFTC's #openstack-tc IRC channel [4]. We focused our attention toward the 2026.2 Election cycle, which is fast approaching. Nominations open on February 4 and run through February 18 [5]; since our election officials are spread a bit thin this time, several TC members who aren't seeking re-election stepped up to help attest nomination patches. We’ve decided to retarget the MariaDB/MySQL Character Set community goal. While it’s a vital piece of technical debt to address, we’re looking to define and commit to this in the 2026.2 cycle to ensure the rollout is realistic and implementable across the projects. We had a robust discussion regarding updating the Technical Vision [6] and how it intersects with the Foundation’s "Next Level in 2026" initiatives [7]. The goal here isn't just to produce a static document, but to use the vision as a tool to refocus the "What is OpenStack?" question, helping us stay consistent as we also define how to evolve the vision. We also touched upon the retirement of some inactive projects in the 2026.2 "Hibiscus" cycle [8]. We hope to make practical decisions in the interest of conserving the community's energy and focusing on paying down technical debt such as eventlet removal. The next meeting of the OpenStack TC is on Tuesday, February 3rd, 2026. It'll be at 1700 UTC in OFTC's #openstack-tc channel. Please find the agenda on the meeting's wiki [9]. This week we're looking to discuss improvements to the User Survey, revival of Cyborg, and begin planning our presence at the PTG in April. I hope you're able to participate. === Governance Proposals === ==== Merged ==== - Remove rbd-iscsi-client from release management | https://review.opendev.org/c/openstack/governance/+/972316 - Remove barbican-ui from release management | https://review.opendev.org/c/openstack/governance/+/972315 - Update mission statement for kolla project | https://review.opendev.org/c/openstack/governance/+/974421 - Reset the DPL model for watcher project | https://review.opendev.org/c/openstack/governance/+/974926 ==== Open For Review ==== - Move FIPS Compliance goal back to proposed | https://review.opendev.org/c/openstack/governance/+/969145 - Reset the DPL model for Oslo project | https://review.opendev.org/c/openstack/governance/+/974929 - Reset the DPL model for Freezer project | https://review.opendev.org/c/openstack/governance/+/974931 - Reset the DPL model for requirements project | https://review.opendev.org/c/openstack/governance/+/974927 - Reset the DPL model for Ironic project | https://review.opendev.org/c/openstack/governance/+/974930 - Revert "Revive os_monasca" | https://review.opendev.org/c/openstack/governance/+/974775 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] Nominate "Extra ACs": https://releases.openstack.org/gazpacho/schedule.html#extra-ac-freeze [3] Be a candidate this election: https://governance.openstack.org/election/#how-to-submit-a-candidacy [4] TC Meeting IRC Log, Jan 27 2026: https://meetings.opendev.org/meetings/tc/2026/tc.2026-01-27-17.00.html [5] 2026.2 Elections: https://governance.openstack.org/election/ [6] Vision for OpenStack Clouds: https://governance.openstack.org/tc/reference/technical-vision.html [7] "Next Level in 2026": https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [8] Inactive Projects: https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [9] TC Meeting Agenda, Feb 03 2026: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Digital Sovereignty WG Kickoff Summary + Recording + Next Steps
by Kendall Nelson 01 Feb '26

01 Feb '26

Hello Everyone! Thank you to those that were able to attend our first meeting of the Digital Sovereignty Working Group! We had excellent representation from many different countries and organizations. Lots of good perspective and ideas were shared and I am eager to get started! As promised, here is the recording for those that were not able to attend: https://zoom.us/rec/share/QLyhngha_pgXEc2736oPEdDGWz_UI8IZLbHbJGyDWLv7nt4es… And here is the etherpad where we took notes, but will also continue to use going forward for meeting agendas and general working group coordination: https://etherpad.opendev.org/p/Digital-Sovereignty-WG If you watch the recording, please feel free to add your name to the attendees list in the etherpad, just make an additional note that you watched the recording. Everyone is encouraged to add to the notes and content in the etherpad whether they attended the meeting live or watched the recording. The goal is to capture as much participation as possible. Digital sovereignty is a very important topic with an ever developing list of accompanying legislation and we need everyone's perspective! Now, while there wasn't much in the way of immediate todo's, the one request that I have is that folks fill out this poll so that we can select a meeting time <https://beta.framadate.org/polls/5f355daf8e4329e1cd52> for the next one (during the first week of February). Responses to this poll are allowed until January 28th. -Kendall

1 2

[nova] gate fix for broken nova-alt-configurations
by Ghanshyam Maan 31 Jan '26

31 Jan '26

Hi All, WIth the recent change in tempest, nova-alt-configurations is broken for the rbac policy access. I proposed the fix, please avoid recheck until fix is merged - https://review.opendev.org/c/openstack/tempest/+/975356 - gmaan

1 0

[keystone][openstack-helm][kolla] Is it safe to run the Keystone wsgi application in multiple threads?
by Vladimir Kozhukalov 30 Jan '26

30 Jan '26

Hi Keystone team, I am writing to ask someone from the Keystone team to give their opinion regarding whether it is safe to run the Keystone wsgi app in multiple threads in the same process. I see [1] Kolla team allows users to configure the number of processes but not the number of threads. We in Openstack-Helm have a similar review request [2] and we had a small discussion about this. I would really appreciate it if someone from the Keystone team can give their opinion on [2]. Thanks. [1] https://opendev.org/openstack/kolla-ansible/src/branch/master/ansible/roles… [2] https://review.opendev.org/c/openstack/openstack-helm/+/971751 -- Best regards, Kozhukalov Vladimir

2 1

[manila] 2026.1 Gazpacho mid cycle: Feb 3rd and 5th
by Carlos Silva 30 Jan '26

30 Jan '26

Hello, everyone! The Manila team's mid cycle is right around the corner. As in the mid cycles we have hosted in the past, we will focus on understanding where we are with our plans for 2026.1 Gazpacho, as well as host collaborative review sessions for the features being introduced, helping speed up the review process. All sessions will be recorded and shared in the OpenStack Manila YouTube channel [2]. We will meet from 15:00 to 16:30 UTC on the 3rd and 5th of February in this meetpad bridge [3]. We are using an etherpad to gather topics [1], so in case you would like to add something to discuss with the manila community, please update the etherpad. The .ics file contains all meeting details [4] and can be imported to your calendar tool of preference. [1] https://etherpad.opendev.org/p/manila-gazpacho-mid-cycle [2] https://www.youtube.com/@openstackmanila [3] https://meetpad.opendev.org/p/manila-gazpacho-mid-cycle [4] https://gist.github.com/silvacarloss/0ba9a53c7b9b3d98690f1b6495baa502 Looking forward to it! Regards, carloss

1 0

[cinder] 2026.1 Midcycle reminder
by Jon Bernard 30 Jan '26

30 Jan '26

Hello all, this is a reminder that our midcycle/review meeting will take place on Wednesday February 11th from 1400 to 1600 UTC. The etherpad we'll be using is here [1], please add any topics and review information that you would like to cover. [1]: https://etherpad.opendev.org/p/cinder-gazpacho-midcycles -- Jon

1 0

[tc][cyborg] Proposal for Cyborg Project Revitalization and Maintenance
by Sean Mooney 30 Jan '26

30 Jan '26

Hi everyone, I'm not really sure how to start this conversation, so I'm just going to jump right to the point. I am writing to the Cyborg community and the Technical Committee to discuss the current state of the project and share my intent to help ramp up maintenance efforts for this cycle and beyond. I recently discussed this briefly on the #openstack-tc channel, but I wanted to bring it to the public list for broader visibility. Now that the new year has started, I am reaching out to express my intent to spend time contributing to the health and maintainability of Cyborg over the next few cycles. If I'm being entirely honest, it does not feel like it has been 18 months since I started down the same path with Watcher, but I have been asked to try and restart Cyborg development in a similar way as we did with Watcher. Recently, I have been submitting patches and performing initial code reviews, but it is clear that review latency and accumulated technical debt have become significant bottlenecks. To help unblock the project and prepare for future development, I am volunteering to lead a focused cleanup effort. My primary goals for this cycle are: 1. Addressing neglected technical debt and stale patches: I have already identified several critical areas including oslo.db and oslo.service compatibility, microversion-parse naming, and the long-overdue eventlet removal. I have also identified a backlog of bot-proposed patches for release notes and .gitreview that need manual intervention. 2. Improving CI/CD stability and alignment: While we have made progress moving failing jobs from Jammy to Noble and adding Python 3.13 support, significant debt remains. For example, the cyborg-tempest-plugin lacks stable branch jobs post-2024.2 while still carrying EOL branch definitions. We also lack grenade/SLURP upgrade testing which is vital for project health. 3. Managing release-related work and project metadata: Cyborg needs active management for release note preludes, marketing highlights, and RC/GA tagging. Furthermore, our Launchpad project requires cleanup to ensure bugs and features are tracked against the correct series, and team ownership needs to be aligned with current OpenStack standards. Note: I have checked PyPI (https://pypi.org/project/openstack-cyborg/) and it is correctly owned by openstackci from what I can tell. We are close to the end of the 2026.1 cycle, so my immediate priority is fixing the critical gaps to ensure Cyborg's inclusion in the 2026.1 release, followed by a longer-term plan for maintenance in 2026.2 and new feature development. To execute this, I am requesting that the core team consider adding me to the cyborg-core group. I am also volunteering as Release and TACT-SIG liaison for the remainder of this cycle. For 2026.2, I propose adopting the Distributed Project Leadership (DPL) model to better distribute these responsibilities. One or two others who have been helping me revive Watcher over the last year will be joining me in this effort over the coming weeks. We hope to split the release, TACT, and security roles between us to ensure consistent coverage unless we get other volunteers :) Our overall goal is to restart the Nova-Cyborg integration work to improve the accelerator management UX (attach/detach, move operations, etc.). To reach that point, we must first pay down technical debt and rebuild an active core review team. I have prepared a high-level maintenance roadmap and task list here: https://etherpad.opendev.org/p/cyborg-maintance-2026.2 which I intend to use to track this work. I look forward to hearing your thoughts. The first step should probably to discuss this at the next tc meeting and to follow up with the existing core team for comment. If there are no objections, I will coordinate with the TC and Infra team regarding the necessary permission updates. Regards, Sean

3 4

[neutron] Drivers meeting canceled Friday, January 30th
by Brian Haley 29 Jan '26

29 Jan '26

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

1 0

RabbitMQ version for OpenStack Epoxy
by Francesco Di Nucci 28 Jan '26

28 Jan '26

Hi all, I'm upgrading from OpenStack Caracal to Epoxy on EL, using RDO packages. I see that CentOS Stream Messaging SIG still packages RabbitMQ 3.8, that is EOL. Should I still use it or switch to a more recent release, like 3.13 or pass to 4.x series? Has anyone tried it? Thanks in advance -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci(a)na.infn.it

5 8

[ironic] Tuesday morning (PST) recurring review jam!
by Jay Faulkner 28 Jan '26

28 Jan '26

Hey all, The GR-OSS OpenStack team is going to be hosting a weekly Ironic review jam for our internal contributors from 10a-11a (PST) on Tuesdays for the foreseeable future. We'll be reviewing anything and everything in Ironic or Ironic-adjacent repos (not just GR changes). If you want an invitation, I'm happy to add anyone, just ask! Thanks, Jay Faulkner

1 0

[election][all][tc] Looking for volunteers to shadow election officials
by Goutham Pacha Ravi 28 Jan '26

28 Jan '26

Hello Stackers, The OpenStack election process is critical to our community. While we have historically relied on a dedicated group of volunteers to serve as election officials, we want to broaden community knowledge of this process. We are looking to recruit new election officials to help manage this important task responsibly. If you are interested in shadowing the upcoming PTL and TC elections for 2026.2, please join #openstack-election on OFTC and let us know. We would appreciate assistance with reviewing candidacies and administering the different election phases [1]. Please note that election officials should ideally be neutral parties who are not contesting these elections themselves. Thanks, Goutham Pacha Ravi (gouthamr) [1] https://governance.openstack.org/election/

1 0

[CI][Zuul] Enhancing Zuul log readability with a custom highlighter script
by Piotr Milewski 28 Jan '26

28 Jan '26

Hi everyone, I would like to share a small tool I've developed to make our daily work with Zuul logs a bit easier and more efficient. As we all know, navigating through long lists of Zuul test results in Gerrit can sometimes be tedious when trying to quickly distinguish between critical failures and non-voting ones. To address this, I created a Tampermonkey script that automatically highlights job statuses with intuitive colors: - Green: SUCCESS - Red: FAILURE (Voting) - Orange: FAILURE (Non-voting) This visual distinction allows for a much faster assessment of the "health" of a patch set at a single glance. How to use it: 1. Install the Tampermonkey extension (available for Chrome, Firefox, Edge, and others) from: https://www.tampermonkey.net/ 2. Add the script available at my Gist: https://gist.github.com/vurmil/b89f3846424bc9231f56da3ce8f8ac16 Please find a screenshot below showing the script in action: [image: image.png] I hope you find this useful! Feel free to share your feedback or suggestions for further improvements. Best regards,

2 1

[blazar] My Blazar service is having issues with MariaDB.
by Eduardo Morais 28 Jan '26

28 Jan '26

The first time the problem appeared, it wouldn’t allow listing the leases. So I went to check the logs and this log showed up. I restarted the service, and less than a week later the same thing happened again.Does anyone have any idea why this error keeps happening, and what the possible consequences would be of increasing the maximum number of connections? LOG: ERROR oslo.service.loopingcall sqlalchemy.exc.TimeoutError: QueuePool limit of size 2 overflow 50 reached, connection timed out, timeout 30.00 (Background on this error at: https://sqlalche.me/e/14/3o7r) 2026-01-26 15:11:45.671 7 ERROR oslo.service.loopingcall 2026-01-26 15:11:45.672 7 WARNING oslo.service.loopingcall [None req-3c69a13f-1bf2-4ace-9b7e-81249a6db22b - - - - - -] Function 'blazar.manager.service.ManagerService._process_events' run outlasted interval by 20.00 sec 2026-01-26 15:11:45.673 7 DEBUG blazar.manager.service [None req-3c69a13f-1bf2-4ace-9b7e-81249a6db22b - - - - - -] Trying to get events from DB. _process_events /var/lib/kolla/venv/lib/python3.10/site-packages/blazar/manager/service.py:233 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall [None req-3c69a13f-1bf2-4ace-9b7e-81249a6db22b - - - - - -] Fixed interval looping call 'blazar.manager.service.ManagerService._process_events' failed: sqlalchemy.exc.TimeoutError: QueuePool limit of size 2 overflow 50 reached, connection timed out, timeout 30.00 (Background on this error at: https://sqlalche.me/e/14/3o7r) 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall Traceback (most recent call last): 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall File "/var/lib/kolla/venv/lib/python3.10/site-packages/oslo_service/loopingcall.py", line 67, in func 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall return f(*args, **kwargs) 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall File "/var/lib/kolla/venv/lib/python3.10/site-packages/blazar/manager/service.py", line 234, in _process_events 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall events = db_api.event_get_all_sorted_by_filters( 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall File "/var/lib/kolla/venv/lib/python3.10/site-packages/blazar/db/api.py", line 102, in decorator 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall res = func(*args, **kwargs) 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall File "/var/lib/kolla/venv/lib/python3.10/site-packages/blazar/db/api.py", line 227, in event_get_all_sorted_by_filters 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall return IMPL.event_get_all_sorted_by_filters(sort_key, sort_dir, 2026-01-26 15:12:15.675 7 ERROR oslo.service.loopingcall File "/var/lib/kolla/venv/lib/python3.10/site-packages/blazar/db/sqlalchemy/api.py", line 355, in event_get_all_sorted_by_filters

2 3

[taskflow] Taskflow hangs with graph_flow with 50 tasks
by Alfredo Moralejo Alonso 28 Jan '26

28 Jan '26

Hi, In the watcher project, taskflow is used to execute actionplans which are composed of actions (taskflow tasks) with certain dependencies between them. We have found that taskflow has problems when actionplans start having problems when having parallelization >=2 around 35 actions and with 50 actions can take up to 45 minutes to find the next task after the first is done. Is anyone having this kind of scalability issues with taskflow? I've reported the issue in https://bugs.launchpad.net/taskflow/+bug/2139228 and provided a minimal reproducer with only taskflow. Any help or recommendation about a different way to implement it is appreciated. Alfredo

2 1

[cinder][nova][os-brick] Guidance on cross-project driver contribution
by Alokedip Choudhuri 28 Jan '26

28 Jan '26

Hello Everyone, We are working on contributing a new Cinder driver for Infoscale. This implementation requires coordinated changes across three projects to support the full attachment lifecycle: * Cinder: The core driver implementation. * Os-brick: The connector APIs will be implemented there * Nova: New driver implementation to support the required operations like, "attach, detach, extend" for the volumes provisioned through the InfoScale Backend. We have already registered blueprints for this work: * Cinder Blueprint: https://blueprints.launchpad.net/cinder/+spec/infoscale-cinder-driver * Nova Blueprint: https://blueprints.launchpad.net/nova/+spec/infoscale-nova-driver Since this is a cross-project effort, I would appreciate guidance on the preferred workflow for submitting patches across multiple repositories to ensure a smooth integration. Looking forward to your feedback and suggestions. Thanks & Regards Alokedip Choudhuri

1 0

[openstack][octavia]Resize a Load Balancer
by Nguyễn Hữu Khôi 27 Jan '26

27 Jan '26

Hello. I see that patch https://review.opendev.org/c/openstack/octavia/+/890215 Could I ask why we cannot merge it? Nguyen Huu Khoi

3 6

[tc][freezer][watcher][requirements][release][oslo][ironic] Please update your DPL liaisons
by Goutham Pacha Ravi 27 Jan '26

27 Jan '26

Hello project maintainers, To ensure project liaisons remain active and interested in their roles within the distributed leadership (DPL) model [1], the Technical Committee (TC) has created several reviews [2]. Project teams have until February 4, 2026, to oppose these changes and retain the DPL model for the 2026.2 "Hibiscus" release. After this deadline, we will seek Project Team Lead (PTL) nominations for these teams as part of the 2026.2 PTL elections [2]. Thanks, On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) [1] https://governance.openstack.org/tc/reference/distributed-project-leadershi… [2] https://review.opendev.org/q/hashtag:%22dpl-reset%22+status:open [3] https://governance.openstack.org/election/

1 0

[tc] [all] [security] Attestation service for confidential VMs: any existing project?
by Jean-Philippe Jung 27 Jan '26

27 Jan '26

Hi, As the work progresses for the support of confidential VMs on OpenStack (support for AMD SEV-SNP, Intel TDX, Arm CCA), is there any current effort/project to look at the key missing piece for Confidential Computing: Attestation. Attestation provides cryptographic proof that your code is actually running inside a genuine Trusted Execution Environment (TEE), not just someone claiming it is. Without attestation, confidential computing is meaningless—you'd be trusting the cloud provider's word that your data is protected, which defeats the entire purpose. Attestation generates a signed report from the hardware itself, containing measurements of the code, the TEE's identity, and proof the CPU is legitimate. This lets you verify before sending sensitive data that: the hardware is real, the enclave code hasn't been tampered with, and the environment matches your expectations. It's trust anchored in silicon, not promises. The Attestation service would have connections to at least to compute and storage, as the attestation service would be the final approver to release a VM decryption key after verifying that the hardware stack is unmodified and suitable to run an encrypted VM. Thank you, JP Jung

5 8

[ops][publiccloud-sig] Public Cloud SIG meeting d.d. 28 January
by Kees Meijs | Nefos 27 Jan '26

27 Jan '26

Hello Stackers, Tomorrow (that's 28 January) the bi-weekly Public Cloud SIG meeting will be held again. The publicly available video meeting will be conducted from 08:05 hrs UTC (09:05 hrs CET) until 08:55 hrs UTC (09:55 hrs CET) here: https://meetpad.opendev.org/publiccloud-sig Additional information to be found on https://wiki.openstack.org/wiki/PublicCloudSIG See you tomorrow! Cheers, Kees __ Kees Meijs BICT Nefos Cloud & IT <https://nefos.com/contact> Nefos IT bv Burgemeester Mollaan 34a 5582 CK Waalre - NL kvk 66494931 +31 (0)88 2088 188 <tel:+31882088188> nefos.com <https://nefos.com/contact> The information contained in this message is intended for the addressee only and may contain classified information. If you are not the addressee, please delete this message and notify the sender; you should not copy or distribute this message or disclose its contents to anyone. Any views or opinions expressed in this message are those of the individual(s) and not necessarily of the organization. No reliance may be placed on this message without written confirmation from an authorised representative of its contents. No guarantee is implied that this message or any attachment is virus free or has not been intercepted and amended. General terms and conditions ("The NLdigital Terms") apply to all our products and services.

1 0

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

26 Jan '26

Hello Stackers, We're 9 weeks away from the date of the coordinated release of OpenStack 2026.1 "Gazpacho" [1]. In the past week, election officials set the dates for the combined election for Project Team Leads and for five seats on the OpenStack Technical Committee [2]. The nomination period begins at 23:45 UTC on February 04, 2026, and runs until 23:45 UTC on February 18, 2026. This may overlap with holiday periods around the world, so please feel free to submit your nominations early [3], and if you'd like, you could have someone else shepherd the nomination through in your absence. Official election updates will follow in a separate thread. Besides this, in the past week, the OpenStack-Ansible project team revived the os_watcher and os_freezer Ansible roles. There are several other governance updates that are undergoing the community's review. === Weekly Meeting === The TC hosted a weekly IRC meeting on January 20, 2026 [4]. We spent a significant amount of time discussing the future of our recommended web server stack, specifically regarding the eventual replacement of uWSGI. While uWSGI remains functional, its "maintenance mode" status and lack of HTTP/2 support are becoming bottlenecks for deployments. We discussed alternatives like Gunicorn and the Rust-based Granian, though the TC's primary goal here isn't to mandate a specific tool, but to clarify the distinction between CI convenience (DevStack-based testing) and production recommendations. Our high-level objective is to ensure that OpenStack services remain backend-agnostic (WSGI/ASGI compatible) while providing deployers with clear, updated documentation that reflects modern performance standards rather than legacy defaults. We also discussed adding a new community goal focused on supporting MariaDB/MySQL character set changes required by newer LTS releases of MariaDB. Doing this would drive consistency across services in maintaining database compatibility and stability. The next meeting of the OpenStack Technical Committee is today, January 27, 2026, at 1700 UTC. It will be hosted on the #openstack-tc IRC channel on OFTC. Please find the agenda on the meeting's wiki page [5]. I hope you'll be able to join us there. === Governance Proposals === ==== Merged ==== - Revive os_freezer role for OSA | https://review.opendev.org/c/openstack/governance/+/973364 - Revive os_watcher role for OSA | https://review.opendev.org/c/openstack/governance/+/973385 - Replace obsolete PCRE packages | https://review.opendev.org/c/openstack/governance/+/974074 ==== Open For Review ==== - Remove rbd-iscsi-client from release management | https://review.opendev.org/c/openstack/governance/+/972316 - Move FIPS Compliance goal back to proposed | https://review.opendev.org/c/openstack/governance/+/969145 - Update mission statement for kolla project | https://review.opendev.org/c/openstack/governance/+/974421 - Remove barbican-ui from release management | https://review.opendev.org/c/openstack/governance/+/972315 === Upcoming Events === - 2026-01-27: OpenInfra Board Meeting: https://board.openinfra.org/ - 2026-01-31: FOSDEM 2026: https://www.meetup.com/brussels-openinfra-meetup-group/events/312867974 - 2026-02-26: 2026.1 "Gazpacho" Feature Freeze / Milestone 3 === 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 [5]. 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] 2026.2 OpenStack Elections: https://governance.openstack.org/election/ [3] How to submit a candidacy: https://governance.openstack.org/election/#how-to-submit-a-candidacy [4] TC Meeting IRC Log, Jan 20 2026: https://meetings.opendev.org/meetings/tc/2026/tc.2026-01-20-08.00.html [5] TC Meeting Agenda, Jan 27 2026: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Joining the Openinfra/Openstack community
by Hamed Enayatzare 26 Jan '26

26 Jan '26

Hi everyone, I’ve been working with OpenStack for several years, mostly around deployment and operations. I recently decided to get more involved with the community and start participating here. Looking forward to learning, sharing experiences, and contributing where I can. ‌Best Regads Hamed Enayatzare

3 3

[Neutron] Bug deputy report Jan 19-26
by Jakub Libosvar 26 Jan '26

26 Jan '26

Hi all, I was the bug deputy for the last week. There are two undecided bugs, one proactive from the Nova team and one that might already be solved in master, would be good to discuss at the next team meeting. Here is the full report: Medium ------ * Ensure no RPC clients are instantiated if ``rpc_workers=0`` https://bugs.launchpad.net/neutron/+bug/2139063 * [OVN] ``LogicalRouterPortEvent`` should discard routers not handled by Neutron API https://bugs.launchpad.net/neutron/+bug/2139067 Rodolfo already proposed a patch: https://review.opendev.org/c/openstack/neutron/+/974709 Low --- * Remove neutron-ovn-db-sync-util and OVNDbMonitor functional tests using various connection types https://bugs.launchpad.net/neutron/+bug/2139064 Slawek already proposed a patch: https://review.opendev.org/c/openstack/neutron/+/974691 Undecided --------- * Broken connectivity to external gateways for baremetal nodes https://bugs.launchpad.net/neutron/+bug/2138941 This one is actually fixed in master and we can discuss if it can be closed. * Live migration or any host update operation may require resetting NVRAM https://bugs.launchpad.net/neutron/+bug/2139077 This is a proactive report and it’s still not clear if there is any need from Neutron.

1 0

[nova] Ephemeral storage potential features
by Karol Klimaszewski 26 Jan '26

26 Jan '26

Hello, In my company (CloudFerro) we have developed two features related to nova ephemeral storage (with libvirt virt driver) - "SPDK-based ephemeral storage backend" and "Multiple ephemeral storage backend handling" (both described below). Would these features be appropriate to be added to upstream? If yes, then should I start with creating a blueprint and proposing a spec for each of them so it is more clear what we want to introduce? Of course not both at once, since there is some code that makes one work with the other. For us it would probably be best if we upstreamed "SPDK-based ephemeral storage backend" first and then upstreamed "Multiple ephemeral storage backend handling" Description of SPDK-based ephemeral storage backend: We add a new possible value for [libvirt]/images_type in nova.conf: spdk_lvol. If this value is set then local disks of instances are handled as logical volumes (lvols). of locally run SPDK instance (on the same compute as VM). See https://spdk.io/doc/logical_volumes.html#lvol for docs on this subject. These are essentially a part of local NVMe disk managed by SPDK. We create and manage those lvols by making calls from nova-compute to SPDK instance with RPC (https://spdk.io/doc/jsonrpc.html) using provided python library (https://github.com/spdk/spdk/blob/master/python/README.md) We attach those lvols to instances by exposing them as vhost-blk devices (see https://spdk.io/doc/vhost.html) and specifying them as disks with source_type='vhostuser'. This method of exposing NVMe local storage allows for much better I/O performance than exposing them from local filesystem. We currently have working: creating, deleting, cold-migrating, shelving, snapshots, unshelving VMs with this storage backend. We don't have live migration working yet but have it in plans. This feature includes changes only to nova. Description of Multiple ephemeral storage backend handling: We add a new configuration option [libvirt]/supported_image_types to nova.conf of nova-compute and change the meaning of [libvirt]/images_type to mean default image type. If libvirt:image_type extra_spec is specified in flavor then VM is scheduled on compute with appropriate image type in its [libvirt]/supported_image_types. We use potentially multiple DISK_GB resource providers and construct appropriate request groups to handle this scheduling. This spec is also used to fill driver_info.libvirt.image_type field of BDMs with destination_type=local of this VM. (driver_info is new JSON serialized field of BDM) Then in compute if BDM specifies this field we use its value instead of [libvirt]/images_type to decide on imagebackend to use for it. This method of handling multiple backends only works after being enabled by administrators by setting libvirt:image_type on all their flavors and running nova-manage commands that update existing VMs. Without enabling everything works as it was before. This feature includes changes to nova and some new traits in os-traits (One per possible value of [libvirt]/images_type + one extra) Best regards, Karol Klimaszewski

2 7

[horizon] Cancelling weekly meeting on Jan 28
by Tatiana Ovchinnikova 23 Jan '26

23 Jan '26

Hello team, I will not be around for our meeting on January 28, so as we discussed earlier I am cancelling it. See you all on February 4. With kind regards, Tatiana

1 0

[Kolla] ovn failed to install because of notifying handlers
by Michal Arbet 23 Jan '26

23 Jan '26

Hi, Ovn is failing currently, https://aa9bea214d792ca72a31-ab9965a682a78200f296c9df29ce08ed.ssl.cf2.rackc… Caused by https://review.opendev.org/c/openstack/kolla-ansible/+/940428 I probably have a fix ..root cause is that item of course don't have a key ... Kevko Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>

1 0

[ops][largescale-sig][scientific-sig][publiccloud-sig] Ops Radio Hour on January 23, 2026
by Ildiko Vancsa 23 Jan '26

23 Jan '26

Hi OpenStack community, I'm reaching out to you with a friendly reminder that the first OpenStack Ops Radio Hour[1] in 2026 is scheduled to happen on __January 23rd, 2026 at 1300UTC,__ which is next Friday! The call series is a casual setting for operators, engineers, and contributors to come together, share knowledge, and collaborate on the complexities of managing and deploying OpenStack environments. Topics for this call: - Plans for 2026 - Ops Radio Hour Survey draft: https://etherpad.opendev.org/p/openstack_ops_radiohour_survey If you have further topics you would like to dive into during the call, please add them to this etherpad: https://etherpad.opendev.org/p/openstack_ops_radiohour A few reminders: - The group on the call agreed to try out Matrix as a chat platform for more synchronous communication outside calls + You can access the Matrix room here: https://matrix.to/#/#openstack-ops:opendev.org<https://matrix.to/#/%23openstack-ops:opendev.org> <https://matrix.to/#/%23openstack-ops:opendev.org%3Chttps://matrix.to/%23/%2…> + Further details are here: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… - If you would like to read and catch up on notes from previous calls, you can find them in this etherpad: https://etherpad.opendev.org/p/openstack_ops_radiohour See you on the call on January 23rd! Bets Regards, Ildikó [1] https://wiki.openstack.org/wiki/Operations/Meetups

1 2

[Neutron] VPNaaS one to many subnets
by Robert N 23 Jan '26

23 Jan '26

Dear Community, I'm trying to configure VPNaaS between 2 sites, both sites have one openstack subnet with 2 networks. left side. subnet 192.168.0.0/24 gw 192.168.0.1 subnet 172.0.0.0/16 - the scope for this is just local network, it doesn't have to be routed outside. this subnet is broke into /24 subnets and assigned to differnt nodes on the network, and they are reachable with explicit routes on the router. It's basically a kubernetes pod network, and the routes are managed by openstack-cloud-controller-manager. right side subnet 192.168.1.0/24 gw 192.168.1.1 subnet 172.1.0.0/16 I need connectivity between the 2 sites on both layers 192.... and 172... so I tried to endpoint groups, a local of type subnet and a peer of type cidr with the cidrs `192.168.0.0/24,172.0.0.0/16` and respectively ` 192.168.1.0/24,172.1.0.0/16`. With this setup the vpn connection doesn't come up. If I create the peer cidr with only one cidr `192.168.0.0/24` and respectively `192.168.1.0/24` the vpn connection becomes active and works as expected for the 192... netowrks. I tried adding manually the routes for the 172.0.0.0/16 on one side and 172.1.0.0/16 o the other side with to the same gateway `169.254.0.2` but it doesn't work. I'm wondering how could I configure the VPN to have both networks routed 192... and 172... Appreciating any input on the topic. Cheers, Robert

1 0

Mark your calendars! April 2026 PTG Dates & Registration
by Kendall Nelson 22 Jan '26

22 Jan '26

Hello Everyone! The dates are set for the next PTG[1]! It will take place April 20-24, 2026! Registration is now open[2] and free for all to attend. Please stay tuned! Soon I will be sending the team sign up survey to collect those teams interested in participating this April. -Kendall Nelson (diablo_rojo) [1] PTG Website: https://openinfra.org/ptg/ [2] PTG Registration: https://ptg.openinfra.org/

1 0

[kolla] Dropping support for building and deploying InfluxDB
by Michał Nasiadka 22 Jan '26

22 Jan '26

Hello Koalas, Kolla project plans to drop support for InfluxDB, given that current version supported by the project is v1, which is in End of Life state. We haven’t seen any interest in introducing v2 support and given that the core team also has no interest in doing that - we’re dropping support. See https://review.opendev.org/q/topic:%22kolla_drop_influxdb%22 Michal

1 0

Zuul failures for openstack-tox-py313
by Nimesh Desai 22 Jan '26

22 Jan '26

Hi, I am observing following error in the zuul run the given patch. There have been no changes in this patch recently, but zuul started failing for this package error. Is this also seen in other patches? Patch: [IBM SVf Driver] Define meaningful names for error constants | https://review.opendev.org/c/openstack/cinder/+/959683 Zuul target: openstack-tox-py313 Zuul error: https://zuul.opendev.org/t/openstack/build/9491515d2dbb473c922ba1e3ba13b19b No package matching 'libpcre3-dev' is available 2026-01-19 03:30:29.510623 | TASK [bindep : Install distro packages from bindep] 2026-01-19 03:30:31.956565 | debian-trixie | ERROR 2026-01-19 03:30:31.956930 | debian-trixie | { 2026-01-19 03:30:31.957003 | debian-trixie | "msg": "No package matching 'libpcre3-dev' is available" 2026-01-19 03:30:31.957062 | debian-trixie | } Regards, Nimesh Desai

4 4

[neutron] Next week CI meeting cancelled
by Yatin Karel 21 Jan '26

21 Jan '26

Hello Neutron Team !! As discussed in the last CI meeting I will not be around upcoming Monday, so cancelling the meeting. We will now have our next CI meeting on 02nd February. -- Thanks and Regards Yatin Karel

1 0

[dev][nova] Intel TDX support
by Anton Iacobaeus 21 Jan '26

21 Jan '26

Hi, I work with confidential computing and has previously contributed to Proxmox [1] to enable support for Intel TDX. I am looking to do the same for Openstack Nova. I have proposed a blueprint [2] and am drafting a spec with target for 2026.2 release. From what I gather, support for AMD SEV and SEV-ES is already implemented in Nova, while SEV-SNP support is ongoing. TDX shares some commonalities with SEV-SNP, and I believe that the work on both can be conducted in tandem. I also have experience with SEV-SNP and am happy to contribute if needed. Early feedback or any concerns and guidance are very welcome! [1] https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_9.1 [2] https://blueprints.launchpad.net/nova/+spec/intel-tdx-libvirt-support Best Regards, Anton

3 3

[all][oslo][cinder][glance][nova][sdk][trove] Upcoming migration of whereto to PCRE2
by Takashi Kajinami 21 Jan '26

21 Jan '26

Hi ! I'm sending this email so that you'd be aware of an upcoming breaking change in the whereto library, because you might need to update your projects (especially their bindep.txt files) to adopt your projects to the change. The whereto library is a tiny library to generate redirect rules in Apache and has been used in documentation build in several projects. This library has been dependent on python-pcre, which requires the following packages. - libpcre3-dev in Debian-based operating systems (such as Debian or Ubuntu) - pcre-devel in RHEL-based operating systems (such as RHEL or CentOS Stream) However these packages are no longer provided by newer operating systems and we have to replace these by PCRE 2. - Debian removed libpcre3-dev because PCRE 3 is obsolete and it is recommended to replace it by PCRE 2 [1]. - RHEL 10 removed PCRE and PCRE 2 is a recommended replacement. I've already proposed the change[1] of whereto to replace python-pcre by pcre2 (which requires pcre2 packages from OS). I'll create a new release of whereto shortly after this change is merged. Once the new release hits the upper constraints, libpcre3-dev and pcre-devel in bindep.txt in each repository should be replaced. See [3] to learn how the change should look like. So far I'm planning to take care of this transition, but it'd be nice if I can ask for some attention about it. Please let me know if you have any question. Thank you, Takashi [1] https://lists.debian.org/debian-devel/2021/11/msg00176.html [2] https://review.opendev.org/c/openstack/whereto/+/970061 [3] https://review.opendev.org/c/openstack/whereto/+/970061/4/bindep.txt -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 1