August 2025 - openstack-discuss - lists.openstack.org

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R-6)
by Goutham Pacha Ravi 18 Aug '25

18 Aug '25

Hello Stackers, We're six weeks away from the release date for the 2025.2 "Flamingo" release [1]. We will observe a feature freeze for this release on August 28th. Nominations for TC and PTL elections are due by August 20th at 23:45 UTC [2]. Please remember that you must be a member of the OpenInfra Foundation to contest these elections. The OIF's recent move under the Linux Foundation meant that any prior member is not automatically considered a member unless they accept this change by renewing their membership [3]. To run as a Project Team Lead, one must also have contributed to the project in the one-year period prior to the nomination deadline. We check this by matching the data between the candidate's OIF profile and their contributions on Gerrit. I understand that several well-meaning candidacies could hit roadblocks because of these requirements. We'd be happy to respond to concerns in the #openstack-election channel on OFTC. Ghanshyam Maan (gmaan), a long-serving member of the TC, would like to take a break and will not be contesting the upcoming elections. I'd like to thank him for his many years of service on the TC, including as its chair. I'm excited to see other community members step up to join the TC in his stead. In the past week, the OpenStack Technical Committee worked with several project teams (Oslo, Requirements, Release Management, Freezer, and Ironic) to reaffirm their distributed leadership model and confirm their liaisons for the upcoming release. We also made some progress on retiring repositories owned by the Monasca project team. The governance proposal [4] to that effect is under the community's review. The community is requested to review the proposed runtime (Python versions and Linux distributions) update for the Gazpacho/2026.1 release cycle [5]. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee was hosted in OFTC's #openstack-tc channel on August 12th, 2025 [6]. We checked on the progress of retiring the Monasca project team. We also discussed the retirement of the refstack-server in the opendev namespace, noting that while the server has been deleted, a desire remains within the community for a lightweight "certification" process to promote interoperability among providers. However, no one has yet committed to leading this effort. If you're reading this and are interested in working on this, please chime in on this list, or within the #openstack-tc IRC channel on OFTC. The conversation then shifted to the health of the gate and the future supported runtimes [5]. Infra administrators noted that the OpenMetal provider is back online in Zuul and that they are working on adding Debian Trixie and dropping older content like Xenial. As for the runtime for Gazpacho, there was a detailed discussion about dropping Python 3.10 and Ubuntu 22.04, with a consensus to drop the latter but a more cautious approach to Python 3.10, which will remain a minimum supported version for now. The group also agreed to include Python 3.13 as a maximum supported version, as recent bug fixes in eventlet make it viable for testing. The next meeting of the TC is today, August 19th, 2025, at 1700 UTC. This meeting will be hosted over IRC, in OFTC's #openstack-tc channel. Please find the meeting's agenda in the wiki [7]. I hope you'll be able to join us. === Governance Proposals === ==== Open For Review ==== - Reset watcher project leadership from DPL back to PTL | https://review.opendev.org/c/openstack/governance/+/956913 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Define testing runtime for 2026.1 release | https://review.opendev.org/c/openstack/governance/+/957199 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 === Upcoming Events === - 2025-08-20: Nominations close for OpenStack elections: - 2025-08-26: OpenInfra Days, Korea: https://2025.openinfradays.kr/ - 2025-08-28: Feature Freeze deadline, Milestone-3 of the Flamingo release [1] - 2025-08-29: Colombia OpenInfra User Group Meetup: https://www.meetup.com/colombia-openinfra-user-group/events/307096751/ - 2025-09-09: OIF Board Monthly meeting: https://board.openinfra.org/ - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] Contesting elections: https://governance.openstack.org/election/#how-to-submit-a-candidacy [3] Renew OIF membership: https://openinfra.org/a/renew-membership [4] Retiring Monasca: https://review.opendev.org/c/openstack/governance/+/953671 [5] Runtime update for 2026.1: https://review.opendev.org/c/openstack/governance/+/957199 [6] TC Meeting IRC Log, Aug 12th 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-08-12-17.00.html [7] TC Meeting Agenda, Aug 19th 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[openstack]backup as a service
by Nguyễn Hữu Khôi 18 Aug '25

18 Aug '25

Hello. I am curious that why dont have a complete backup solution for Openstack. I used Cinder backup but It cannot schedule time to backup and wont display how long to complete backup. I found Freezer and Raksha but it was abadonned. Currently, we use Ceph and do snapshot and rbd export to backup Ceph volumes. Nguyen Huu Khoi

2 11

[dev][infra][qa][tact-sig] Updating Zuul to Ansible 11
by Jeremy Stanley 18 Aug '25

18 Aug '25

Just a heads up for those not following OpenDev's service-announce mailing list, today OpenDev is switching Zuul's default Ansible version in the openstack tenant from 9 to 11. See this announcement for further details: https://lists.opendev.org/archives/list/service-announce@lists.opendev.org/… If you notice any new behavior changes in your jobs, double-check that it's not related to the Ansible version update. -- Jeremy Stanley

1 0

[all][elections][ptl][tc] Combined PTL/TC 2026.1 cycle Election Nominations Last Days
by Sławek Kapłoński 18 Aug '25

18 Aug '25

Hi, A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Aug 20, 2025 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 @ 2025-08-06 23:45:00 UTC Nominations end @ 2025-08-20 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 2 days, 14:27:12 Nominations progress : 81.41% --------------------------------------------------- Projects[1] : 38 Projects with candidates : 8 ( 21.05%) Projects with election : 1 ( 2.63%) --------------------------------------------------- Need election : 1 (Horizon) Need appointment : 30 (Adjutant Barbican Blazar Cloudkitty Cyborg Glance Heat Keystone Magnum Manila Masakari Mistral Monasca Neutron Nova Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms Puppet_OpenStack Quality_Assurance Rall y Storlets Sunbeam Swift Tacker Telemetry Trove Venus Vitrage) --------------------------------------------------- TC Candidates : 2 (4 Required) =================================================== Stats gathered @ 2025-08-18 09:17:48 UTC This means that with approximately 2 days left, 30 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… -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Bug deputy report (week starting on August 11)
by Bernard Cafarelli 18 Aug '25

18 Aug '25

Hey neutrinos, we switched the deputy order with Miro, so here is the list of bugs reported last week It was quiet most of the week, though activity picked up a bit in the end (thanks Brian for checking the recent ones). Overall, medium priority bugs are in progress, with a patch proposed or even merged. The metadata agent one is worth digging into, and we have one on vpnaas that need relevant eyes High * [OVN] Metadata agent errors when returning gzip-encoded data - https://bugs.launchpad.net/bugs/2120723 Reported on 2025.1, Brian asked for more info (up-to-date deployment, possible to test on master) Medium * Neutron FWaaS logapi fails to notify for already deleted ports - https://bugs.launchpad.net/bugs/2120429 Patch proposed and merged: https://review.opendev.org/c/openstack/neutron-fwaas/+/956013 * Limit threads for metadata haproxy - https://bugs.launchpad.net/bugs/2120668 Patch proposed: https://review.opendev.org/c/openstack/neutron/+/955951 * Dual-stack networks are not handled correct by OVS DHCP plugin - https://bugs.launchpad.net/bugs/2120758 Patch proposed: https://review.opendev.org/c/openstack/neutron/+/957594 New * Dalmatian: Second IPsec site connection on same VPN service/router stays PENDING_CREATE; no agent-side rendering (works on Zed L3 agent) - https://bugs.launchpad.net/bugs/2120316 VPNaaS issue with ML2/OVS, we have similar open issues but on ML2/OVN - Needs vpnaas eyes Proposed RFE * Add metadata caching for immutable values - https://bugs.launchpad.net/bugs/2120732 * Set additional search domains via DHCP - https://bugs.launchpad.net/bugs/2120740 Regards, -- Bernard Cafarelli

1 0

[manila] Share network subnets unclean
by Rico Lin 17 Aug '25

17 Aug '25

Hi Manila core team We have an issue with share network teardown that leaves subnet unclean when no router information is provided. This led to a huge list of subnets stay unclean with manila CSI plugin in Kubernetes. The fix is here: https://review.opendev.org/c/openstack/manila/+/955996 It would be appreciated if you could kindly provide your review on this. Thank you *Rico Lin*

1 0

[release] Release countdown for week R-6, Aug 18 - 22
by Elõd Illés 15 Aug '25

15 Aug '25

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 August 21st, 2025. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2025.2 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" (August 28th, 2025) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, August 28th, 2025. 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/2025.2 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2025.2 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2025.2 "Flamingo" 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: August 21st, 2025 (R-6 week) Client library freeze: August 28th, 2025 (R-5 week) Flamingo-3 milestone: August 28th, 2025 (R-5 week) Cycle Highlights Due: September 4th, 2025 (R-4 week) 2025.2 "Flamingo" final release: October 1st, 2025 OpenInfra Summit Europe: October 17th-19th, 2025 Előd Illés irc: elodilles @ #openstack-release

1 0

[nova] Nova API call duration increases after upgrading to Caracal
by Chang Xue 15 Aug '25

15 Aug '25

Hello, we recently upgraded from Bobcat to Caracal. After upgrading, an interesting increment of duration of nova api call is observed. It's involved to multiple API calls, e.g. os-query-sets, /v2.1/servers/detail, etc. And it seems to be accumulated, meaning whenever nova-api is restarted, the duration seems to be fairly fast, giving response within like 80, 90 ms. As it keeps running for like up to 10 days, the duration increases to over 500 ms. I noticed that Caracal is using UnifiedLimitsDriver instead of DbQuotaDriver. I tried to change nova.conf to use DbQuotaDriver but it seems not working well with reducing the duration. I understand that calling to Keystone and Placement (and likely other external APIs) could result to longer duration, but pretty confused why it shows up as accumulated. Wondering if anyone else in Openstack community noticed the similar issue, thanks!

5 10

[magnum] Deploying Openshift with Magnum
by Winicius Allan 15 Aug '25

15 Aug '25

Hi community, Currently, is it possible to deploy an Openshift cluster using Magnum? I do not find anything on docs, nor on drivers. If it is not possible, is there any effort to add this feature in the future? Thanks in advance

1 0

[PTL][Nova][Swift][Cyborg][Keystone][Neutron][Horizon][Skyline] OpenStack for AI Whitepaper: August 14 Meeting Recording & Recap
by Kendall Nelson 15 Aug '25

15 Aug '25

Hello Everyone! Thank you again to those that were in attendance today and also those that have already been contributing to the whitepaper! We are making some solid progress. For those that weren't able to make it, in today's meeting we did another walkthrough of the working document and outline with the new subsection additions <https://docs.google.com/document/d/1NjxIyWF6aUFg0jb0HewX1JmOyploYV5Dxe3j1Lt…>. I talked a little bit about inclusion of specific images that have been added and that I am trying to keep up with comments and questions in the doc. I also reiterated our timeline (trying to have all the content largely drafted by September 1) and a reminder that providing a reference architecture is open to all OpenInfra Platinum, Gold and Silver members and that case studies can be provided by OpenInfra Platinum and Gold members for inclusion in the whitepaper. The deadline for both reference archs and case studies is September 19th. If you know you will not make the deadline please reach out to us ahead of time and we can try to make accommodations, but largely after that date we will not be able to include additions due to website building and other planning that will be the final phase before publication at the OpenInfra Summit Europe. You can watch the recording of today's meeting here <https://zoom.us/rec/share/JSacqoVVH9hmBriq9XRM69IyxCoRWnNykQj5T0GScln85SDP4…> . WRT OpenStack teams, I want to call out some of the comments and sections in the doc: We are in need of your perspective! I had added some of the PTLs directly in comments, but anyone from any project team is welcome to get involved in the whitepaper. Generally the projects I tagged in the subject line of this email are ones we would love content from, but if there are others that should be or want to be included, we can figure that out as well. As always if you have any questions, please feel free to drop them here or in the working doc <https://docs.google.com/document/d/1NjxIyWF6aUFg0jb0HewX1JmOyploYV5Dxe3j1Lt…>, or generally on the ML. As another reminder, next week will be an asych check in. I look forward to seeing more of your content in the doc by then! Thank you everyone for your effort and collaboration! -- Kendall Nelson *Senior Upstream Developer Advocate* The OpenInfra Foundation <https://openinfra.dev/>

3 2