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

[vitrage][tc] Project status
by Takashi Kajinami 20 Aug '25

20 Aug '25

Hi, Some of you might be aware of this, but tempest jobs in vitrage repo have been broken for some time (I remember I saw consistent failures early in this cycle and I'm afraid that the situation hasn't been improved.) I spent some time to dig into these failures and found out a few problems. However I'm afraid I can't fix these all with my limited knowledge about vitrage. # I've helped its project maintenance for some time but I've never looked into # its implementations quite in detail. So I'm sharing my observations here hoping someone who know better about it can look into these. 1. Usage of removed oslo_context.context.RequestContext interfaces This is the most trivial and can be fixed easily. https://review.opendev.org/c/openstack/vitrage/+/957004/2/vitrage/api/hooks… 2. Usage of asyncore modules from pysnmp-lextudio Recent release of pysnmp-lextudio no longer provides these modules, likely due to removal of asyncore in Python 3.12 . I was drafting the migration to asyncio version in https://review.opendev.org/c/openstack/vitrage/+/957004 but learned simple replacement does not work and we need more careful assessment. This might be the most tricky problem atm. 3. Some tempest test failures I can no longer see old CI results, but as far as I'm aware, CI jobs were blocked by a few tests consistently failing early in this cycle so we may have to dig into these, too. You may find some tempest tests failures in https://review.opendev.org/c/openstack/vitrage/+/957004 though I'm unsure if these are related to broken snmp service, which is caused by incomplete migration to asyncio (which I described in 2). I'm adding the tc tag, to notify them of the current status. Thank you, Takashi Kajinami -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

2 2

[swift] Unmaintained branch cleanup
by Tim Burke 20 Aug '25

20 Aug '25

Swift currently has six unmaintained branches: - unmaintained/2023.1 - unmaintained/zed - unmaintained/yoga - unmaintained/xena - unmaintained/wallaby - unmaintained/victoria Half of them have not been updated this year. For all of them, the only patches since the transition to unmaintained status were to try to maintain CI. While two of them have open patches, they all seem to revolve around maintaining CI and none of them currently pass. I propose transitioning all of these to end-of-life. If you have any objections, please respond here on the mailing list or at https://review.opendev.org/c/openstack/releases/+/958101 which makes the change. Tim

1 0

[horizon] Today's weekly meeting is cancelled
by Tatiana Ovchinnikova 20 Aug '25

20 Aug '25

Hello team, A reminder that today's meeting is cancelled since more than a half of the team is busy with downstream activities. With kind regards, Tatiana

1 0

[masakari] Add a rpc api for ping check
by do-gyun kim 20 Aug '25

20 Aug '25

Similar to Nova, I think it would be good to add ping api to masakari engine for rpc health check. This can be used for reading business and lifestyle check in Masakari distributed to Kubernetes through OpenStack Helm. Currently, there is no health check for masakari-engine in openstack-helm project, but it would be good to add it. Blueprint: https://blueprints.launchpad.net/masakari/+spec/add-a-rpc-api-for-ping

1 1

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

19 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 : 1 day, 9:36:15 Nominations progress : 90.00% --------------------------------------------------- Projects[1] : 38 Projects with candidates : 18 ( 47.37%) Projects with election : 1 ( 2.63%) --------------------------------------------------- Need election : 1 (Horizon) Need appointment : 20 (Adjutant Barbican Blazar Cloudkitty Cyborg Glance Magnum Manila Masakari Mistral Monasca OpenStackAnsible OpenStack_Ch arms Quality_Assurance Rally Swift Tacker Trove Venus Vitrage) --------------------------------------------------- TC Candidates : 2 (4 Required) =================================================== Stats gathered @ 2025-08-19 14:08:45 UTC This means that with approximately 2 days left, 20 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

2 1

[election][cloudkitty] PTL candidacy for the 2026.1 release cycle
by Rafael Weingärtner 19 Aug '25

19 Aug '25

Hi all, I would like to self-nominate for the role of PTL of CloudKitty for the 2026.1 release cycle. I have been PTL since the Victoria cycle and I am willing to continue in this role. I will keep working with existing contributors to maintain CloudKitty for their use cases and encourage the addition of new functionalities. I have opened the patch with my candidacy: https://review.opendev.org/c/openstack/election/+/957871 -- Rafael Weingärtner

1 0

[openstack-client|keystone] API calling behavior for fetching by id or name
by Niklas Schwarz 19 Aug '25

19 Aug '25

Hey there I have observed that the keystone logs are flooded with error messages and a stack trace that resources are not found. When investigating on the issue I noticed that the resources do exist but the behavior of the openstack-client is a bit confusing. I will describe the behavior for the openstack-client in the interaction with the kestone api. As know the openstack-cli which uses the openstack-client has the functionality to show a user either by passing an id or the name of the user. The requests when executing the command with the name of the user will be 1. v3/user/<name_or_id> - v3/user?name=<name_or_id> The first request is issued to the endpoint which expects the rout parameter to be an id of the user and in the case of the keystone api a db query is executed with the name as an id and no user will be found which results in the log message and the stack trace in the keyston logs. Because no user was found the openstack-client issues a second request to the api with the name as a query-parameter instead of a rout-parameter which will issue the db-query at the keystone api to search by the username. On some deployments this can and will be additional load on the database and on the api which can be reduced just by sending the correct request to the api instead of "guessing" and trying for the correct request and hoping there will be an answer. The issue with keystone is that the openstack-client will issue also requests to the keystone api when listing, e.g. networks but only for a specific project (openstack network list --project <name_or_id>). The client will first search for the project and in the worst case these are two requests. In my opinion this behavior can be prevented to send multiple requests to the keystone api (or any other api), either by checking on the client if a the passed parameter is an id or by handling the passed route-parameter accordingly in the keystone api and executing the correct db-query to prevent multiple requests. I have decided on implementing a change [1] on the client side and have adjusted the openstack-client. As artem pointed out in the review that in some services there are places where the id cannot be really identified as such I wanted to ask/I was asked to discuss the issue on the mailing list since there might be multiple projects involved in such a change to reduce the calls to the api (when handling on the client side) or db (when handling on the server side) when a search by an id or name is issued. Are there an plans on tackling this issue or any other options and opinions? The post by marc [2] might also be a result of the openstack-client issuing multiple requests to the api and polluting the logs. So in some cases this is a realy issue. Best regards Niklas [1] https://review.opendev.org/c/openstack/python-openstackclient/+/933644 [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…

3 4

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

19 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