- openstack-discuss - lists.openstack.org

[nova]Hypervisor Data and Overcommit Ratio via API
by Thamanna Farhath 11 Sep '25

11 Sep '25

Hi All, I noticed a mismatch between hypervisor data shown in Horizon and via the OpenStack API. The API returns original values without calculating the overcommit ratio. Could you advise how to retrieve the effective resources including overcommit ratio via the API? Thanks, Thamanna Farhath N Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

2 1

[cinder]Issue Deleting Volume Snapshots in OpenStack
by Thamanna Farhath 11 Sep '25

11 Sep '25

Hi All, I’m facing an issue when deleting volume snapshots in our OpenStack environment (Kolla-Ansible + Ceph). The snapshots get stuck in error deleting status. Logs show: rbd.PermissionError: [errno 1] RBD permission error (error unprotecting snapshot b'volume-<id>'@b'snapshot-<id>') Could you suggest ways to resolve this or reduce such permission errors during snapshot deletion? Thanks Thamanna Farhath N https://www.facebook.com/Zybisys/ Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

1 0

[publiccloud-sig] Public Cloud SIG meeting d.d. 10 September
by Kees Meijs | Nefos 10 Sep '25

10 Sep '25

Hello Stackers, Tomorrow (that's 10 September) the bi-weekly Public Cloud SIG meeting will be held again. The publicly available video meeting will be conducted from 07:00 hrs UTC (09:00 hrs CEST) and on 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.

2 2

[sdk][requirements] RFE requested for openstacksdk
by Stephen Finucane 10 Sep '25

10 Sep '25

o/ Per request from elodilles, I'd like to request a Requirements Freeze Exception (RFE) for openstacksdk in order to release [1]. That resolves a minor bug that is currently preventing us bumping the minimum version of openstacksdk before we release Flamingo [2]. fwiw, 4.7.0 itself consists mainly of wholly new features, bug fixes, and test cleanup. I've includes the git log below Cheers, Stephen [1] https://review.opendev.org/c/openstack/releases/+/960355 [2] https://review.opendev.org/c/openstack/requirements/+/960027 --- ❯ git log --oneline --no-merges 4.6.0..4.7.0 -- . ':!openstack/tests' ':!doc' 53e19fe0a Add id to query_mapping for Networking 2d8ff6603 Add SDK support for ``glance image-tasks`` 61323654e tests: Use binary mode to open files 1649ed0cd Replace CLA with DCO b14c73d35 Remove commented out sections b2ada579c create_image: support other import methods d649aada8 resource: add max_items parameter to resource cb04f4a70 Fix hostname attribute withing request body c2465fee2 Increase swap allocation for devstack-networking 4b0b78e19 Allow filtering of volumes by properties 3a774c1c5 Fix Volume.set_image_metadata 82bc00507 Remove loop variable 65a97e1a7 Fix create_volume_snapshot() description. 83fc95d25 Remove duplicate Python version declarations 2eb367c6e Migrate setup configuration to pyproject.toml da4961cab zuul: Make openstacksdk-functional-devstack-masakari voting 198cb9e02 zuul: Make openstacksdk-functional-devstack-ironic voting 07f52229b Clean small nit comment ad9896c12 Add support for inspection rules 4b74d73ae Add backup export command 5a909ee17 typing: Annotate openstack.config.openstackcloud 7c1e42b41 config: Handle interface list in CloudRegion.get_all_version_data 36a7ccb6f typing: Annotate openstack.config.cloud_config 550c15c83 typing: Annotate openstack.config.loader 5a2b3bd81 typing: Annotate openstack.config.vendors 9afc09407 typing: Annotate openstack.config.cloud_region de9129e76 Update .git-blame-ignore-revs b82a434d3 Follow-up: Add support for runbooks

2 1

[cinder] IBM SVf driver callhome
by Vivek Pandey 10 Sep '25

10 Sep '25

Hi Joe/ Brian, Since we didn’t get a chance to discuss the patch [IBM SVf driver] Adding support for callhome plugin, we can continue the conversation here. Patch : https://review.opendev.org/c/openstack/cinder/+/951829. We need callhome enabled as default for which we have introduced a parameter “callhome” in cinder.conf. This feature is to fecth the os_version, cinder-manage version and ispbhaenabled. Note: We are not fetching any customer’s sensitive data. Please let me know if you’ve had a chance to review NetApp’s ActiveIQ implementation. Netapp’s ActiveIQ code ref : https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/netap… As we have discussed during the 9th July cinder call, Anoop from NetApp confirmed that they are enabling it by default and EMS details are being captured from the logs. Based on that, do you think we can align or extend our current IBM callhome implementation (from the patch above) to follow a similar approach? Thanks, Vivek

5 9

OpenStack wide MariaDB 11.8 problem
by Seunghun Lee 10 Sep '25

10 Sep '25

Dear OpenStack developers I'm a Kolla contributor and was trying to bump MariaDB from 10.11 to 11.8 for Kolla and Kolla-Ansible projects. During this, I found problems that can happen across the whole OpenStack services with MariaDB's default charset and collation set changes. Here's the note I made for each problem I found. Problems with default collation set change - MariaDB changed default collation set of charset utf8mb3 from utf8mb3_general_ci to utf8mb3_uca1400_ai_ci from 11.5 https://jira.mariadb.org/browse/MDEV-25829 - K-A currently sets database level charset to utf8 (Which is aliased to utf8mb3) and collation set to utf8_general_ci (aliased to utf8mb3_general_ci) - Problem detected when deploying fresh magnum on MariaDB 11.8: https://bugs.launchpad.net/magnum/+bug/2121797 - This is because how MariaDB works. If charset is not specified when creating a table, MariaDB uses database level charset and collation set (if set) or server level charset and collation set - If only charset is specified when creating a table, MariaDB uses MariaDB default (defined as a list of mapping in variable ``collation_connection``) - Magnum specified charset when creating *some* of tables not all -> Collation set inconsistency in magnum database. - Server-wide collation set inconsistency (when DB and services are freshly deployed) - Some services such as Nova, Keystone, Cinder, designate provides charset when creating tables (Also alters database level charset to utf8 in first alembic op) Let's call them group A - Some services such as Glance, Neutron, Octavia, Placement don't. Let's call them group B - Then we have Magnum which mixed up. Let's call it... Magnum - These differences cause database level collation set inconsistency between group A and group B services because of MariaDB's behaviour on creating a table and database - Potential problem for MariaDB 10.11 to 11.8 upgrade - Existing databases in MariaDB server have collation set of utf8mb3_general_ci - Because of MariaDB's new default collation set for utf8mb3 and how the table creation works, if any services decide to create a new table, they can be created with utf8mb3_uca1400_ai_ci and causes collation set inconsistency - This issue can be invisible at first but if any project decides to create new tables then do string comparison between the old tables and new tables, it will be visible - Potential solution A: Override MariaDB default for utf8mb3 to utf8mb3_general_ci for each service clients https://mariadb.com/docs/server/reference/data-types/string-data-types/char… - Pros: Easy - Cons: - In fact, it doesn't work. Because there are slight differences on how each projects create tables, only some of them (Keystone, designate) are affected - Even if it worked, It's just delaying the problem. Looks like community pushed forward in the past: https://review.opendev.org/c/openstack/kolla-ansible/+/455154 - Potential solution B: Change K-A's server level collation set config to utf8mb3_uca1400_ai_ci then migrate (ALTER TABLE) all tables to use new collation on upgrade - Pros: We'll probably don't need to worry about this matter for a long time - Cons: - Service disruption, inter-table relationships such as foreign keys make altering table hard. - Percona-toolkit claims it can be done with near-zero downtime with FK handling strategies. Can be useful. https://docs.percona.com/percona-toolkit/pt-online-schema-change.html (GPLv2 license) - Potential solution C: Use MariaDB 11.4 instead - Pros: 11.4 is also an LTS but without this drama - Cons: Not the latest LTS Problems with default character set change - MariaDB's new default charset utf8mb4 https://jira.mariadb.org/browse/MDEV-19123 - This is not urgent but MariaDB is planning to remove alias between utf8 and utf8mb3 https://jira.mariadb.org/browse/MDEV-30041 - Currently most of openstack projects use 'utf8' when specifying a character set not 'utf8mb3'. This will all need to be updated to 'utf8mb3'. - Or we can try moving on to utf8mb4 but ironic need to use utf8mb3 due to its internal design https://docs.openstack.org/ironic/latest/install/install.html#set-up-the-da… - Transition to utf8mb4 would also need a migration plan - Using MariaDB 11.4 also helps here because this change is from 11.6 I suggest to raise this topic on next OpenStack TC meeting. I think it's worth having a inter-project conversation as these will affect any projects that uses DB. What do people think about this? Any inputs are appreciated. Kind regards, Seunghun Lee Cloud Engineer, StackHPC

4 4

[freezer] Activity on this project?
by Jimmy McArthur 08 Sep '25

08 Sep '25

Are there orgs or individuals that are working on Freezer and/or have interest in working on Freezer? Cheers, Jimmy

4 3

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

08 Sep '25

Hello Stackers, We're three weeks away from the coordinated 2025.2 "Flamingo" release [1]. This week, project teams are testing code changes and merging bug fixes to deliver release candidates for deliverables that follow a "cycle-with-rc" release model [2]. Polls for electing a PTL for the OpenStack Dashboard ("Horizon") project team, as well as for four members to the OpenStack Technical Committee, are still open. They will close on September 17th, 2025, at 23:45 UTC [3]. In the past week, election officials reached out to a section of the electorate that hadn't opted in to emails on the election system: CIVS. Please do contact the election officials [3] if you are having trouble finding your ballot. Besides this, governance updates included marking the conclusion of the goal to migrate WSGI scripts across all OpenStack services [4] and adding new metadata to project tracking to highlight inactive OpenStack projects. This will help us make release and documentation updates to clearly flag deliverables that need help from new (or existing) contributors, as well as serve as a health indicator to operators and users. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee occurred on September 2nd, 2025, simultaneously over Meetpad [5] and IRC [6]. The "Migrate from WSGI scripts to module paths" goal was completed [4]. A significant portion of the meeting was spent discussing the proposed retirement of the Monasca project team. The TC considered whether to recommend forking the project into a new namespace on opendev.org under the aegis of the volunteer who wants to maintain it. We also discussed the need to update documentation and README files to reflect the project's maintenance status and to implement automated updates for this process. We discussed the ongoing elections, where an early retrospective item was to urge existing members to renew their OpenInfra Foundation memberships and to opt in to CIVS emails. The team reviewed "leaderless teams" and the status of projects like Vitrage, Venus and OpenStack Charms, noting that a PTL candidate is still needed. We took an action item to tag retired packages on PyPi as part of the repository retirement process. Finally, the group briefly touched on gate health issues related to Debian Trixie nodes and a new discussion point about default MySQL/MariaDB charset/collations that will be addressed in the next meeting. The next meeting of the OpenStack TC is on September 9th, 2025, at 1700 UTC. This meeting will be hosted in the #openstack-tc channel on OFTC. Please find the meeting's agenda on its wiki page [7]. I hope you'll be able to join us there. === Governance Proposals === ==== Merged ==== - Show inactive project status in project.yaml | https://review.opendev.org/c/openstack/governance/+/958229 - Mark "Migrate from WSGI scripts" goal as completed | https://review.opendev.org/c/openstack/governance/+/958817 ==== Open For Review ==== - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Extend Monasca's inactive state | https://review.opendev.org/c/openstack/governance/+/959392 === Upcoming Events === - 2025-09-09: OIF Board Monthly meeting: https://board.openinfra.org/ - 2025-09-17: OpenStack TC and Horizon project elections conclude: https://governance.openstack.org/election/ - 2025-10-01: OpenStack 2026.1 "Flamingo" release day - 2025-10-03: OpenStack's Birthday Meetup, Austin: https://www.meetup.com/openinfra-austin/events/310508680 - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ === How to Contact the TC === You can reach the TC in several ways: - Email: send an email with the tag [tc] on this mailing list. - Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC. - Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 1700 UTC [7]. 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] "cycle-with-rc" release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] OpenStack Elections: https://governance.openstack.org/election/ [4] Community Goal to update WSGI configuration: https://governance.openstack.org/tc/goals/proposed/migrate-from-wsgi-script… [5] TC Meeting Video Recording, Sep 2nd, 2025: https://youtu.be/K_tdk4mkxT0 [6] TC Meeting IRC Log, Sep 2nd, 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-02-17.01.html [7] TC Meeting Agenda, Sep 9th, 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[watcher] Core team updates - removals, reminders, and new addition
by Sean Mooney 08 Sep '25

08 Sep '25

Hi everyone, I'm writing to propose some updates to the Watcher core team membership to ensure we maintain an active and engaged core review team. ## Proposed Removals (Immediate) The following core reviewers have been inactive for an extended period and I propose to remove them from all Watcher core groups: * Alexander Chadin (joker946(a)gmail.com) - last contribution: 26 Feb 2019 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=joker… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=joker…> * Vincent Françoise (Vincent.FRANCOISE(a)b-com.com) - last contribution: 15 Mar 2019 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=vince… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=vince…> * YumengBao (yumeng_bao(a)yahoo.com) - last contribution: 09 Apr 2020 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=yumen… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=yumen…> * aditi sharma (adi.sky17(a)gmail.com) - last contribution: 22 Nov 2018 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=adi-s… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=adi-s…> * licanwei (li.canwei2(a)zte.com.cn) - last contribution: 21 Jan 2021 https://www.stackalytics.io/?release=all&user_id=li-canwei2&module=watcher-… <https://www.stackalytics.io/?release=all&user_id=li-canwei2&module=watcher-…> * suzhengwei (sugar-2008(a)163.com) - last contribution: 13 Sep 2022 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=sue.s… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=sue.s…> We want to thank all these contributors for their valuable work and contributions to the Watcher project over the years for there time and effort. ## Core Activity Notice (Removal planned for 2026.2) The following core reviewers are currently showing low activity levels. We're providing advance notice that they will be removed from the core group at the start of the 2026.2 cycle unless they become active again during the 2026.1 cycle: * chenker (chen.ke14(a)zte.com.cn) * Dan Smith (dms(a)danplanet.com) * Marios Andreou (marios.andreou(a)gmail.com) * Slawek Kaplonski (skaplons(a)redhat.com) We recognize that over time priorities change, if you wish to maintain their core status and can re-engage or wish to be be removed before we review the core composition again at the start of 2026.2 just let us know. ## New Core Proposal I would also like to propose adding jgilaber (jgilaber(a)redhat.com) as a new member of the watcher-core group, based on their recent contributions and engagement with the project. ## Timeline These changes will take effect if there are no objections by our next Watcher IRC meeting on Thursday, September 11th, 2025. Please share any feedback or concerns about these proposed changes. Regards sean

4 3

October 2025 PTG Team Signup Final Call
by Kendall Nelson 08 Sep '25

08 Sep '25

Hello Everyone, Make sure to sign your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, October 27th to Friday, October 31st 2025! If you haven't already done so and your team is interested in participating, you need to complete the survey[1] by September 14th, 2025 at 7:00 UTC. Please also make sure to register[2] for the event - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2025_ptg_survey [2] PTG Registration: http://ptg.openinfra.dev/

1 0