January 2026 - openstack-discuss - lists.openstack.org

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

13 Jan '26

Hello Stackers, Tomorrow (that's 14 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 Meeting Agenda (2026.1/R-11)
by Goutham Pacha Ravi 12 Jan '26

12 Jan '26

Hello Stackers, Happy New Year! After a 4-week break, the weekly TC meeting returns on January 13th 2026, Tuesday. It will be held in the #openstack-tc channel on OFTC between 1700 UTC and 1800 UTC. Please find the agenda in the meeting's wiki page [1]. I hope you'll be able to join us! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee

1 0

A focus on digital sovereignty in 2026
by Kendall Nelson 12 Jan '26

12 Jan '26

Hello! A growing trend around the globe that is especially relevant for OpenInfra is digital sovereignty. Now, while OpenStack has been engineered with fine grained control over the data being processed and saved in OpenStack VMs since its inception, it is not necessarily immediately obvious to the global tech industry just how secure and intentional OpenStack can be. As a community, we hope to grow awareness by collaborating on a targeted effort to promote understanding of the ways in which OpenStack and other OpenInfra technologies enable digital sovereignty. To kick off this effort we plan to host a meeting on January 20th at 7:00 UTC. This first meeting will focus on setting the stage and defining goals for the year (examples could include crafting concrete deliverables, a gathering of case studies, enumeration of new features that could grow the digital sovereignty use case, etc). If you are interested in joining this meeting, please reply to this email and I can get you added to the calendar block. Please join us! -Kendall

1 0

[ptls][tc] 2026 OpenStack Marketing & Messaging Priorities
by Allison Price 12 Jan '26

12 Jan '26

Hi everyone, I wanted to share the big focuses for OpenInfra Foundation marketing around OpenStack messaging as I think this could be helpful as we think about overall milestones for OpenStack as well as positioning for Gazpacho and Hibiscus. I would love your help in identifying upstream and community work throughout the year that can help amplify these messaging priorities. OpenStack as the OSS Infrastructure Standard to Support AI Workloads This is a massive, quickly growing space, and it’s critical to keep OpenStack relevant as these systems get built out. It will be our primary focus for 2026. Specifically here, I want to learn more about efforts around hardware diversification efforts as this is a common concern I have heard when scaling to support AI workloads as more new hardware is introduced. Digital Sovereignty: Building a Global Network of Localized Clouds In Europe we have seen digital sovereignty provide a unique opportunity for OpenStack and we are seeing this extend to new geographies rapidly. This isn’t limited to code, but also to the OpenStack community culture in areas like open governance. Kendall Nelson will be following up on a larger effort around this soon. VMware Migration While VMware Migration will not be the primary focus this year, it continues to provide significant momentum for OpenStack adoption. As new features are built or strengthened to support this transition, we need to be prepared to share that more broadly. This is not an exhaustive list of messaging around OpenStack, but are priorities that the OpenInfra Foundation has identified to maximize OpenStack exposure in the broader open source and cloud market. If it would be helpful, I am happy to join an OpenStack TC meeting or schedule an ad hoc meeting to discuss these priorities and any feedback or concerns you may have as well as opportunities to maximize impact. Thanks, Allison Allison Price VP of Marketing & Community, OpenInfra Linux Foundation p: +1-214-686-6821 e: allison(a)openinfra.dev e: aprice(a)linuxfoundation.org

1 0

[cinder] volume migration and multipathing
by Karl-Heinz Preuß 12 Jan '26

12 Jan '26

Hi Everyone, I'm trying to migrate cinder volumes from one backend to another. Namely I'm migrating from an HPE Nimble Storage backend to a Ceph backend. My Problem: the volume migration speed is kinda sluggish - around 100 MB/s. I can read from a Nimble backed volume way faster. And of course the Ceph can also write more than 1GB/s. After quite some debugging, the problem seems to be: cinder uses multipathing to access the Nimble backed volumes. But for some reason cinder's volume migration explicitly doesn't use multipathing. (I found "multipath=false" in the cinder logs when looking for my slow migrations.) Question: is there a way to configure cinder to use multipathing for volume migrations when available. -- Karl-Heinz Preuß Linux Consultant Tel.: +49 1515 5806243 E-Mail: preuss(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / https://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt, HRB 3537

2 1

[aco][ansible] PRs for the ansible collection
by James Hewitt-Thomas 12 Jan '26

12 Jan '26

Hi all, I've made a few proposed changes for the ansible collection, not sure on the process so thought I'd reach out and check. I've got them passing the zuul checks - is there anything I need to do to request reviewers, or is it just an it'll happen over time thing? There's no urgency, just making sure I'm not leaving things in limbo. Thanks, James.

1 0

[ceilometer] ceilometer metrics for list fields in event payloads
by NITIN GUPTA 12 Jan '26

12 Jan '26

Hello Ceilometer Team! Good Day! Could you please suggest, how to create ceilometer metrics for list fields in event payloads when creating Gnocchi resources? Looks like Ceilometer doesn't iterate over list fields in event payloads when creating Gnocchi resources. Is this a known issue? From the below Sample payload, I'm looking to create a separate metric for "vcpus" field (for example) from each item in "reservations", which is a list of dictionary type of data in the payload. 'payload': { 'lease_id': 'f94182be-70e2-4f3f-bc8d-a1d1c2eea0aa', 'user_id': '2cf63f4ecf7740f5ac9ef4adfa4cdf5e', 'project_id': '07f1a09ab11543bb9080d260a98d812c', 'trust_id': '0037eb9121f04cdc94c39628a8354dde', 'start_date': '2025-12-15T16:18:00.000000', 'end_date': '2025-12-15T16:22:00.000000', 'status': 'PENDING', '*reservations*': [ { 'id': '1fffeb17-599d-441a-80e0-ca6d9044fd36', 'lease_id': 'f94182be-70e2-4f3f-bc8d-a1d1c2eea0aa', 'resource_id': 'c9daade3-4a85-4122-bec2-f34b7a849a01', 'resource_type': 'virtual:instance', 'status': 'pending', 'missing_resources': False, 'resources_changed': False, 'created_at': '2025-12-15 16:18:07', 'updated_at': '2025-12-15 16:18:10', '*vcpus*': 1, 'memory_mb': 1024, 'disk_gb': 20, 'amount': 1, 'affinity': None, 'resource_properties': '', 'flavor_id': '1fffeb17-599d-441a-80e0-ca6d9044fd36', 'aggregate_id': 292, 'server_group_id': None }, { 'id': '97df8162-d756-44c0-a27f-c832101577e8', 'lease_id': 'f94182be-70e2-4f3f-bc8d-a1d1c2eea0aa', 'resource_id': '4a3e20b1-5f63-46b1-a61b-13a267fd829a', 'resource_type': 'virtual:instance', 'status': 'pending', 'missing_resources': False, 'resources_changed': False, 'created_at': '2025-12-15 16:18:05', 'updated_at': '2025-12-15 16:18:07', '*vcpus*': 1, 'memory_mb': 1024, 'disk_gb': 20, 'amount': 1, 'affinity': None, 'resource_properties': '', 'flavor_id': '97df8162-d756-44c0-a27f-c832101577e8', 'aggregate_id': 291, 'server_group_id': None } ], 'events': [{'id': '4cea5a4f-53f4-4a69-969b-74a5869c7ab1', 'lease_id': 'f94182be-70e2-4f3f-bc8d-a1d1c2eea0aa', 'event_type': 'end_lease', 'time': '2025-12-15T16:22:00.000000', 'status': 'UNDONE', 'created_at': '2025-12-15 16:18:10', 'updated_at': None}, {'id': '63b51fc9-5eca-4729-8f5e-a3659e7db24b', 'lease_id': 'f94182be-70e2-4f3f-bc8d-a1d1c2eea0aa', 'event_type': 'start_lease', 'time': '2025-12-15T16:18:00.000000', 'status': 'UNDONE', 'created_at': '2025-12-15 16:18:10', 'updated_at': None}, {'id': 'bba382f6-47d8-4bb0-b3aa-0a65c6959ed9', 'lease_id': 'f94182be-70e2-4f3f-bc8d-a1d1c2eea0aa', 'event_type': 'before_end_lease', 'time': '2025-12-15T16:18:00.000000', 'status': 'UNDONE', 'created_at': '2025-12-15 16:18:10', 'updated_at': None}], 'name': 'lease-short-ins', 'created_at': '2025-12-15 16:18:05', 'updated_at': '2025-12-15 16:18:10', 'degraded': False } Best regards. -- NITIN GUPTA

3 12

[neutron] Bug deputy Jan 5 - Jan 11
by Rodolfo Alonso Hernandez 12 Jan '26

12 Jan '26

Hello Neutrinos: This is the list of bugs created during the last week: * Critical ** networking-bgpvpn and neutron-vpnaas unit tests arefailing due to tenant_id to project_id migration ( https://bugs.launchpad.net/neutron/+bug/2137489) Fixes merged and bug closed. * High: ** devstack deployment failing on stable/2025.1 branch without wsgi ( https://bugs.launchpad.net/neutron/+bug/2137540) Fix proposed: https://review.opendev.org/c/openstack/neutron/+/972669 (tested in https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/972266) * Medium ** neutron.tests.functional.services.bgp.test_ovn.TestBgpOvnLocking.test_locking_mechanism randomly fails with AssertionError: Second API did not lose the lock ( https://bugs.launchpad.net/neutron/+bug/2137467) In progress: https://review.opendev.org/c/openstack/neutron/+/972547 ** ``get_api_worker_id`` should not fail if ``uwsgi`` module is not installed (https://bugs.launchpad.net/neutron/+bug/2137715) Fix proposed: https://review.opendev.org/c/openstack/neutron/+/972687 (needed up to 2025.2) Regards.

1 0

[tacker] Cancelling weekly IRC meeting
by Yasufumi Ogawa 11 Jan '26

11 Jan '26

Hi tacker team, Due to a holiday in Japan and most of team members aren't join, I'm cancelling meeting this week. Regards, Yasufumi

1 0

[release] Release countdown for week R-11, Jan 12 - 16
by Elõd Illés 09 Jan '26

09 Jan '26

Development Focus ----------------- We are now past the Gazpacho-2 milestone, and entering the last development phase of the cycle. Please review the late milestone-2 release patches at https://review.opendev.org/q/topic:gazpacho-milestone-2 if you have not done so already! Teams should otherwise be focused on implementing planned work for the cycle. Now is a good time to review those plans and reprioritize anything if needed based on the what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to the end of the release cycle, please be aware of the feature freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 19th, 2026). 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, 2026) * Deliverables following a cycle-with-rc model (that would be most services) 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. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 12th, 2026) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 26th, 2026) 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) Előd Illés irc: elodilles @ #openstack-release

1 0