May 2025 - openstack-discuss - lists.openstack.org

"quantum" package name on pypi
by JDK Phoenix 22 May '25

22 May '25

Dear Openstack-Team, I am the creator and maintainer of the programming language "qb" (qb · PyPI <https://pypi.org/project/qb/>, qb <https://lschreiber.eu/qb/>) and I wanted to implement a package manager similar to how Maven, Cargo or Poetry works. I picked the name "quantum" for this program and noticed that this name was already in use on pypi for a package developed by you. This program has only a singular contribution in 2012 and seems to be inactive since then. I wanted to ask if it would be possible for you to transfer the quantum-package name on pypi to my user (Leander420). I would be very grateful if this could be possible. I thank you for your time and consideration Kind regards Leander S. Schreiber

6 6

[tc][all] Moving from CLA to DCO for OpenInfra Contributions
by Jonathan Bryce 22 May '25

22 May '25

Hi everyone, I wanted to flag a recent message on the Foundation mailing list about the possibility to move OpenInfra projects from using the Contributor License Agreement (CLA) to the Developer Certificate of Origin (DCO) [1]. This change would be part of the broader transition into the Linux Foundation and could take effect starting June 1, 2025. It’s something the Board has supported for newer projects, and now existing projects like OpenStack have the opportunity to make the switch as well. I’m happy to join the TC meeting this week to discuss. Thanks, Jonathan 1. https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/th…

5 7

Issue on IP Assignment on newly created VM after deleting old one
by sudeb ghosh 21 May '25

21 May '25

Hi Team, We are operating an OpenStack environment managed by Ansible. Openstack Version: Ussuri(21.2.1) OS: CentOS8 We had a volume backed VM named VM01 with IP of 10.10.10.10 for example. We required to delete the VM01 & recreate a VM named VM02 using the same volume. We used the same project & same network what we used for VM01 earlier. VM02 is getting any one available IPs from the given network. Manually i am able to detach the existing IP & attached the specific IP but its not pinging. Query: i) What is the option if i need the same IP(10.10.10.10) will be assigned to VM02 as well autometically? ii) What is fix to get the said old IP(10.10.10.10) working if i do attach manually in GUI through newtwork-interface? BR// Sudeb Ghosh 7044064878 9332034788

3 3

[openstack][nova]qemu system wont release memory
by Nguyễn Hữu Khôi 21 May '25

21 May '25

Hello. I have an OpenStack instance that was using 14GB out of 16GB of memory. Later, when it was using only 4GB, I checked the QEMU process on the compute node, and it was still consuming 14GB, this means memory isn't released when usage decreases. Do we have solutions for this? I use Ubuntu 24.04 instances. Nguyen Huu Khoi

2 2

#eventlet-removal - Progress & Updates - Flamingo milestone 1
by Herve Beraud 21 May '25

21 May '25

TL;DR: We just passed the milestone 1 of Flamingo and at this point big fishes like Neutron, Nova, Glance, and Mistral demonstrated awesome progress in their migration. Oslo.service's new backend is now usable in real life use cases. Eventlet still suffers from a new version of Python. If you have not yet started your migration yet, then, please consider starting ASAP before the aircraft crash. ## OpenStack Updates Neutron's L3 agent is well on its way to running its WSGI features without using Eventlet and activating the new oslo.service threading backend at runtime. Allowing to decouple a bit more the needs of Eventlet at runtime. Nova scheduler is now able to start in threading mode without requiring any usage of Eventlet at runtime. This was possible by also shifting nova-scheduler to the threading backend of oslo.service. More details are available here https://gibizer.github.io/categories/eventlet/ Activating the new threading backend of oslo.service required devstack adaptation to allow having jobs running this execution mode. https://review.opendev.org/c/openstack/devstack/+/948436. Everybody will be able to benefit from these adaptations. Glance continues its adaptation journey by migrating its functional jobs to reduce its needs of Eventlet and to allow it to run jobs in threading mode. oslo.service's new backend is on the way to be landed soon, and is waiting for additional reviews. https://review.opendev.org/c/openstack/oslo.service/+/945720 ## Eventlet Updates Our CI was failing for almost 2 months, we were able to unlock this failing CI and hence we were able to merge several blocked reviews. Last week Eventlet 0.40.0 was released. This new version provides fixes around OpenSSL 3.5+. The support of Python 3.8 and of PyPy were removed. The Python 3.13 issues are still not solved and require further work. ## Call to Action Flamingo is a crucial series in the realization of global migration of OpenStack. We need your involvement to accelerate the progress of this initiative! If your project is affected by Eventlet, now is the time to start your migration. Teams are invited to read the migration guide available at https://removal.eventlet.org/ and are encouraged to join the #openstack-eventlet-removal IRC channel to get help. You'll benefit quickly from the advantages of running your deliverables without using Eventlet. ## Final Thoughts Postponing the beginning of the migration will put additional pressure related to growing runtime failures of Eventlet. We want to prevent this from happening to you. We are now going straight to milestone 2 meaning that we will soon be in the middle of Flamingo. The migration path is now well cleared by all the previous actions and changes applied into OpenStack. Do not be afraid by the migration and take advantage of the collected experience. Your journey start here https://removal.eventlet.org/ Thanks for reading. -- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/

3 4

[watcher] Call for maintainers - MAAS integration
by Douglas Viroel 21 May '25

21 May '25

Hi everyone, At the last watcher's weekly meeting[1], the team discussed the impacts of the eventlet removal in Watcher's code, and it was brought up that the integration with MAAS (Metal As a Service) support is affected. At the moment, we do not have any active members in Watcher that have any experience with MAAS. CI also doesn't have any job running and testing this integration, and we don't have documentation of how it works. This is a call for maintainers interested in supporting MAAS in Watcher to help fill these gaps. It is worth mentioning that, as discussed in the PTG[2], we also plan to mark this integration as *experimental* once it does not provide minimal testing and documentation (this is also the case of other integrations). But we will cover this topic in a different thread. [1] https://meetings.opendev.org/meetings/watcher/2025/watcher.2025-05-15-12.01… [2] https://etherpad.opendev.org/p/apr2025-ptg-watcher#L71 Thanks and regards, -- Douglas Viroel - dviroel

1 0

[ops][neutron] Neutron-db-manage upgrade from Antelope to Bobcat fails with "foreign key constraint 'porthints_ibfk_1' are incompatible" error
by federica fanzago 21 May '25

21 May '25

Dear all, we are running an OpenStack deployment Yoga on AlmaLinux 9.5 and we are attempting the upgrade Openstack up to Caracal release, one release at time (Zed--Antelope--Bobcat--Caracal) The procedure we are following is to shut down all openstack services, to remove the "old" openstack release and to install the new one, upgrading all service databases. This procedure works well for Zed and Antelope, but during the installation of the Bobcat release, the Neutron database upgrade fails when creating the new "porthints" table. The command we are using is su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head" neutron and the error message we receive is ... File "/usr/lib/python3.9/site-packages/pymysql/err.py", line 107, in raise_mysql_exception raise errorclass(errno, errval) sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (3780, "Referencing column 'port_id' and referenced column 'id' in foreign key constraint 'porthints_ibfk_1' are incompatible.") [SQL: CREATE TABLE porthints ( port_id VARCHAR(36) NOT NULL, hints VARCHAR(4095) NOT NULL, PRIMARY KEY (port_id), FOREIGN KEY(port_id) REFERENCES ports (id) ON DELETE CASCADE )ENGINE=InnoDB ... Our "ports" table uses the collation utf8mb3_general_ci mysql> SHOW FULL COLUMNS FROM ports; +------------------+--------------+--------------------+------+-----+---------+-------+---------------------------------+---------+ | Field | Type | Collation | Null | Key | Default | Extra | Privileges | Comment | +------------------+--------------+--------------------+------+-----+---------+-------+---------------------------------+---------+ | project_id | varchar(255) | utf8mb3_general_ci | YES | MUL | NULL | | select,insert,update,references | | | id | varchar(36) | utf8mb3_general_ci | NO | PRI | NULL | | select,insert,update,references | | | name | varchar(255) | utf8mb3_general_ci | YES | | NULL | | select,insert,update,references | | | network_id | varchar(36) | utf8mb3_general_ci | NO | MUL | NULL | | select,insert,update,references | | | mac_address | varchar(32) | utf8mb3_general_ci | NO | | NULL | | select,insert,update,references | | | admin_state_up | tinyint(1) | NULL | NO | | NULL | | select,insert,update,references | | | status | varchar(16) | utf8mb3_general_ci | NO | | NULL | | select,insert,update,references | | | device_id | varchar(255) | utf8mb3_general_ci | NO | MUL | NULL | | select,insert,update,references | | | device_owner | varchar(255) | utf8mb3_general_ci | NO | | NULL | | select,insert,update,references | | | standard_attr_id | bigint | NULL | NO | UNI | NULL | | select,insert,update,references | | | ip_allocation | varchar(16) | utf8mb3_general_ci | YES | | NULL | | select,insert,update,references | | +------------------+--------------+--------------------+------+-----+---------+-------+---------------------------------+---------+ in Bobcat the collation required for the new "porthints" table is latin1_swedish_ci MariaDB [neutron]> show create table porthints; +-----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Table | Create Table | +-----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | porthints | CREATE TABLE `porthints` ( `port_id` varchar(36) NOT NULL, `hints` varchar(4095) NOT NULL, PRIMARY KEY (`port_id`), CONSTRAINT `porthints_ibfk_1` FOREIGN KEY (`port_id`) REFERENCES `ports` (`id`) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci | So, we have tried to create the porthints table in mysql, forcing the collation to utf8mb3_general_ci mysql> CREATE TABLE porthints ( port_id VARCHAR(36) NOT NULL, hints VARCHAR(4095) NOT NULL, PRIMARY KEY (port_id), FOREIGN KEY(port_id) REFERENCES ports (id) ON DELETE CASCADE )ENGINE=InnoDB DEFAULT CHARSET=utf8 DEFAULT COLLATE utf8mb3_general_ci; and commenting out the creation of the new table in the neutron code /usr/lib/python3.9/site-packages/neutron/db/migration/alembic_migrations/versions/2023.2/expand/6f1145bff34c_port_hints.py. In this way, the upgrade works, but we encounter the same kind of problem during the upgrade to Caracal, specifically with the creation of the new table porthardwareoffloadtype. Have you already encountered this issue during the Neutron upgrade? Do you have any suggestions on how to upgrade the neutron DB, without manually creating new tables? Thanks a lot, cheers, Federica -- Federica Fanzago INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy Tel: +39 049.967.7367 --

4 8

Osprofiler and nova
by engineer2024 20 May '25

20 May '25

Team, I am facing an issue with osprofiler in nova, where the 'trace show' is failing. I have filed a bug at https://bugs.launchpad.net/osprofiler/+bug/2111345 But I don't see any recent activity there. Is the osprofiler project active ? Please guide me as per the issue mentioned there... Thanks elinux

1 0

[publiccloud-sig] Next meeting of Public Cloud SIG - May 21st at 0700 UTC
by Felix Kronlage-Dammers 20 May '25

20 May '25

Hi everyone, This upcoming Wednesday (May 21st - this is tomorrow :) the next meeting of the publiccloud-sig is going to happen. We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG See you tomorrow! cheers felix -- Felix Kronlage-Dammers Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

CEPH deployment method: cephadm vs puppet
by Francesco Di Nucci 20 May '25

20 May '25

Hi all, we're planning (finally) to setup a CEPH cluster to be used as OpenStack backend. The cloud is actually set up with Foreman+Puppet, to setup CEPH what would you advice? cephadm as it's the preferred method in the CEPH docs or Puppet with the puppet-ceph module, as it's part of openstack? Thanks in advance -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci(a)na.infn.it

6 14

[Patch Management] [Openstack-2024.1 (caracal)]
by Shalini Srivastava 20 May '25

20 May '25

Hello Sir/Ma'am, I need to implement Security update that is Patch management, Vulnerability Management to my Openstack environment that is 2024.1 (Caracal release). The services needs to upgrade as well as update according to the upper constraints available for the given release. Please guide me the steps/procedure for the same. Hope to hear from you soon. Thanks & Regards, Shalini Srivastava Project Associate /प्रोजेक्ट एसोसिएट Centre for Development of Advanced Computing(C-DAC) / प्रगत संगणन विकास केन्द्र(सी-डैक) Tidel Park”, 8th Floor, “D” Block, (North &South) / “टाइडल पार्क”,8वीं मंजिल, “डी” ब्लॉक, (उत्तर और दक्षिण) No.4, Rajiv Gandhi Salai / नं.4, राजीव गांधी सलाई Taramani / तारामणि Chennai / चेन्नई – 600113 Ph.No.:044-22542226/27 Fax No.: 044-22542294 ------------------------------------------------------------------------------------------------------------ [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------

1 0

Guidance related to [Patch Management] [Openstack-2024.1 (caracal)]
by Shalini Srivastava 20 May '25

20 May '25

Hello Sir/Ma'am, I need to implement a Security update that is Patch management, Vulnerability Management to my Openstack environment that is 2024.1 (Caracal release). The services need to upgrade as well as update according to the upper constraints available for the given release. Please guide me the steps/procedure for the same. Hope to hear from you soon. Thanks & Regards, *Shalini Srivastava* Project Associate /प्रोजेक्ट एसोसिएट Centre for Development of Advanced Computing(C-DAC) / प्रगत संगणन विकास केन्द्र(सी-डैक) Tidel Park”, 8th Floor, “D” Block, (North &South) / “टाइडल पार्क”,8वीं मंजिल, “डी” ब्लॉक, (उत्तर और दक्षिण) No.4, Rajiv Gandhi Salai / नं.4, राजीव गांधी सलाई Taramani / तारामणि Chennai / चेन्नई – 600113 Ph.No.:044-22542226/27 Fax No.: 044-22542294

1 0

[magnum] April vPTG summary and Magnum meeting time change
by Dale Smith 20 May '25

20 May '25

Hello all, I wanted to post a short summary to this list of the vPTG[1] the Magnum team held on April 8th and 9th 2025. These are the topics and a summary of my notes from the discussions. If I missed key details please add these to the etherpad and/or reply here. Thank you all for attending. Please get in touch if the timing of the vPTG did not work for you, as we could propose multiple timezone slots in future. * Heat driver deprecation. o This driver is marked deprecated in Dalmation 2025.1, being replaced by either of the Cluster API drivers, and we discussed when and how we will remove it from Magnum codebase. o We are now looking at removing the Heat driver in this (Flamingo 2025.2) cycle, as waiting longer may imply waiting until 2026.2 due to SLURP release expectations. We would like to hear any feedback on this plan from users of Magnum - either in the mailing list or join one of our IRC meetings[2]. o One option is to move the driver out of tree into its own codebase (perhaps in `x/`), to allow deployers to keep their existing clusters functional and addressable by Magnum while transitioning to a Cluster API driver. This initiative needs effort and a champion to drive it. * Helm charts (magnum-capi-helm driver) o While the driver code is now in opendev the Helm charts live in azimuth-cloud's github. These are a major component of the driver and we discussed the reasoning behind keeping them in github and stability of the Magnum-capi-helm driver. o The current proposal is to snapshot the upstream repo at regular intervals into the opendev repo. This avoids maintenance of a complete fork, but keeps the Magnum-capi-helm driver with a stable internal reference of the helm charts. * CI for the Magnum project was discussed o One big implication of the Heat driver being removed is what we test against. o Including the CAPI drivers (initially non-voting) would give stability, provided external changes wouldn't break the CI. * Normalised labels proposal o Dale has a proposal for Normalised labels[3], aiming for Mutable labels. The video format discussion of the vPTG was very helpful to give context and move the idea forward to cover API backwards compatibility requirements and a better way to implement support labels for different drivers. o The proposal as it stands should be re-worked to look at covering a similar extension pattern that Nova has with drivers, and possibly look to replace labels. * TC initiatives o We discussed the upcoming Eventlet removal and as we are a small team we will wait for guidance and examples to follow before implementing, but we remain aware of this initiative. Finally, I wanted to announce to the list that at last weeks Magnum IRC meeting we proposed and agreed on a new time slot. This is on alternate (every second) Tuesday at 8am UTC starting on the 27th May[2]. See the meeting notes for a full transcript and discussion[4]. Links and references: [1] Magnum vPTG topics and notes can be found on https://etherpad.opendev.org/p/apr2025-ptg-magnum [2] Magnum weekly meeting times and agenda, https://etherpad.openstack.org/p/magnum-weekly-meeting [3] Normalisation of labels proposal, https://review.opendev.org/c/openstack/magnum-specs/+/943358 [4] Magnum meeting 2025-05-14, https://meetings.opendev.org/meetings/magnum/2025/magnum.2025-05-14-09.00.l… Thank you for reading! (or skim reading!) Dale Smith Magnum PTL for Epoxy cycle.

1 0

[adjutant] Adding Callum Dickinson to core group
by Dale Smith 20 May '25

20 May '25

Hello all, The project Adjutant is adding Callum Dickinson to the core group. Callum has contributed features, bugfixes and reviews code in the Adjutant project. I want to note that both of us are from the same company, Catalyst Cloud, and keeping the project alive by using it internally. We will always welcome other contributors, and don't want to keep this project exclusive. regards, Dale, Adjutant PTL -- DALE SMITH Cloud Engineer Catalyst Cloud <https://catalystcloud.nz> Aotearoa New Zealand's cloud provider e dale(a)catalystcloud.nz w catalystcloud.nz <https://catalystcloud.nz> Follow us on LinkedIn <https://www.linkedin.com/company/catalyst-cloud-limited/> Level 6, Catalyst House, 150 Willis St, Wellington 6011 Confidentiality Notice: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267 <tel:+6444992267>.

1 0

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

20 May '25

Hello Stackers, We are 19 weeks away from the release date for OpenStack 2025.2 "Flamingo" [1]. Last week, election officials published the combined TC and PTL election schedule targeting the next release cycle [2]. We are setting up our election configuration early to ensure that community members have adequate time to propose and deliberate nominations. The elections themselves will occur in August 2025, and the official nominations window opens on 2025-08-06 (week R-8). However, you are welcome to submit your candidacy early in case you anticipate being away. Please note that your nomination will not be merged until the nomination window opens. This election is also an opportunity for OpenStack project teams to modify their leadership model if they choose. All project teams with "distributed" project leadership will be required to update their liaisons or assert that no change is necessary by week R-8. Please await changes from the TC on Gerrit to do so. No further governance changes were made last week; however, a few proposals are open for review. === Weekly Meeting === The weekly IRC meeting of the OpenStack Technical Committee occurred on 2025-05-13 [3]. A lot of progress was made in the past few weeks with regard to action items that we were tracking from our Project Team Gathering in April. We discussed a proposal [4] to require a declaration of affiliation when contesting TC elections and how that would apply to current TC members. The proposal seeks to enhance transparency and allow voters to make more informed choices since the TC has an affiliation diversity requirement [5] that is enforced when adopting the results of an election. Concerns were raised about potential misinterpretations regarding company influence and the perception of OpenStack's governance. It was recommended that we add specific disclaimers as to why the affiliation is declared on our governance pages after this proposal has been adopted. We also socialized the kick-off for the 2026.1 elections. I will be serving as the TC's election liaison and helping our election officials Slawek Kaplonski (slaweq) and Ian Y Choi (ianychoi). We discussed the state of the CI, bringing the TC up to speed on several cross-community CI efforts. The next meeting of the OpenStack TC is on 2025-05-20 at 1700 UTC. This meeting will be held over IRC on the #openstack-tc channel on OFTC. Please find the agenda and other details in the meeting's wiki page [6]. I hope you will be able to join us there! === Governance Proposals === === Open for review === - [resolution] Relinquish "quantum" project on PyPI | https://review.opendev.org/c/openstack/governance/+/949783 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Clarify actions when no elections are required | https://review.opendev.org/c/openstack/governance/+/949431 === Upcoming Events === - 2025-05-22: OpenInfra UG Meetup, Sweden: https://www.meetup.com/openinfra-user-group-sweden/events/306139678/ - 2025-06-03: 15 ans d'OpenStack - OpenInfra UG, Paris: https://www.meetup.com/openstack-france/events/307492285 - 2025-06-05: OpenStack 15 ans! - OpenInfra UG, Rennes: https://www.meetup.com/openstack-rennes/events/306903998 - 2025-06-28: OpenInfra+Cloud Native Day, Vietnam: https://www.vietopeninfra.org/void2025 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] 2026.1 TC+PTL Elections: https://governance.openstack.org/election/ [3] TC Meeting IRC Log 2025-05-13: https://meetings.opendev.org/meetings/tc/2025/tc.2025-05-13-17.00.html [4] Require declaration of affiliation from TC Candidates: https://review.opendev.org/c/openstack/governance/+/949432 [5] OpenStack TC's affiliation diversity requirement: https://governance.openstack.org/tc/reference/charter.html#tc-diversity-req… [6] TC Meeting Agenda, 2025-05-20: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[all][dev][ops][tc] Bridging the gap between community and contributing orgs
by Jeremy Stanley 20 May '25

20 May '25

The tl;dr on this is that I'm opening a broad community discussion on how we can, collectively through improved communication, better bring together our established contributors with casual and prospective contributors who struggle to find successful patterns of contribution, so that we might all support each other in order to benefit OpenStack as a whole. Read on for details... OpenStack's TC has requested that foundation staff, when in conversation with representatives of member organizations, encourage participation in the project and collect feedback on any related challenges those organizations encounter in their attempts to do so. In order to better understand the feedback and brainstorm achievable recommendations for the broader community[*], Community Managers on the foundation staff started to work with a small focus group of established contributors with a solid understanding of what successful patterns of contribution look like. It also came to light that established contributors experience many of the same sorts of challenges, even more so if they don't have the luxury of focusing full-time upstream, and so success often comes down to knowing how to effectively navigate those challenges. The community's goal with this exercise is to improve everyone's experience, and your help is needed to do that! The most common themes reported by those struggling to contribute are not related to tooling or workflow confusion, but instead seem to come down to basic communication challenges. Ideas so far to address these gaps include: * Review bandwidth - Ensure contributors and companies understand the importance and benefits of code review - Incentivize and credit meaningful "+1" reviews more - Understand that the volume of changes and limited reviewer bandwidth often means proposals aren't reviewed quickly (or at all), and their proponents may need some additional tenacity and engagement with the team to get their work noticed - Utilize "review dashboards" as a way to find stale changes which have fallen through the cracks * Review strategy and etiquette - Be clear about the meaning of votes on changes, especially negative ones, and set explicit timelines for things like "procedural -2" or WIP blocks when their approval needs to be delayed - Focus on comments and requests that affect whether or not the change can be merged after the fixes are submitted, rather than requesting trivial adjustments to an unsuitable change which has more fundamental problems - Reciprocate with reviews of changes from new reviewers you see leaving insubstantial reviews, demonstrating to them what deeper and more meaningful reviewing looks like * Mentoring newcomers - Established contributors with sufficient bandwidth can help mentoring newcomers, potential core reviewers and new leaders - Mentoring can happen as part of internship programs as well as by helping newcomers determined to become active contributors; both ways should be embraced and utilized What challenges are you facing? And, how would you improve them? Two weeks from now, we'll have a forum session at the OpenInfra Summit Asia in Suwon[**] where our community can refine these possible approaches and integrate others, as well as bring attention to them and promote their application. I've also proposed a similar forum session for OpenInfra Days North America in Indianapolis a month after that, where we can hopefully continue this conversation. The goal for this multi-stage effort is to improve the contribution experience for established participants, casual contributors and newcomers alike. While it's easy to jump to blaming in these situations, it will be far more productive if we can focus on the challenges and experiences that we would each like to remove or improve for ourselves and others in our community. As we find ways together to improve our efficiency, we can reduce the load on all contributors and lower the barriers for people to join and participate. [*] https://etherpad.opendev.org/p/r.2205024e55689bccb82c20c960853cb5 [**] https://2024.openinfraasia.org/a/schedule#view=calendar&title=Bridging%20th… -- Jeremy Stanley

2 9

[ironic] No meeting May 26, 2025
by Jay Faulkner 20 May '25

20 May '25

Hi all, We're cancelling the meeting for next Monday, May 26, due to it overlapping with the US Memorial Day holiday. Thanks, Jay Faulkner Ironic Security Liason

1 0

Guidance related to Patch Management in Openstack-2024.1 (caracal)
by Shalini Srivastava 19 May '25

19 May '25

Hello Sir, I need to implement Security update that is Patch management, Vulnerability Management to my Openstack environment that is 2024.1 (Caracal release). The services needs to upgrade as well as update according to the upper constraints available for the given release. Please guide me the steps/procedure for the same. Hope to hear from you soon. Thanks & Regards, Shalini Srivastava Project Associate /प्रोजेक्ट एसोसिएट Centre for Development of Advanced Computing(C-DAC) / प्रगत संगणन विकास केन्द्र(सी-डैक) Tidel Park”, 8th Floor, “D” Block, (North &South) / “टाइडल पार्क”,8वीं मंजिल, “डी” ब्लॉक, (उत्तर और दक्षिण) No.4, Rajiv Gandhi Salai / नं.4, राजीव गांधी सलाई Taramani / तारामणि Chennai / चेन्नई – 600113 Ph.No.:044-22542226/27 Fax No.: 044-22542294 ------------------------------------------------------------------------------------------------------------ [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------

1 0

[neutron] Bug deputy report (week starting on May 12)
by Bernard Cafarelli 19 May '25

19 May '25

Hey neutrinos, here is the list of bugs reported last week Overall a quiet week, bugs are assigned with proposed (or merged already) patch, except a CI failure report (no immediate action needed, mostly for tracking if the failure reappears) High * Neutron endpoint options are not applied - https://bugs.launchpad.net/neutron/+bug/2110488 ovn-octavia-provider similar to a fixed Octavia issue, proposed updated patch by priteau: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/925893 * "neutron-tempest-plugin-designate-scenario-zed" job failing - https://bugs.launchpad.net/neutron/+bug/2110550 Needed to pin the tempest plugin to zed-last, fix by ralonsoh merged: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/949643 Medium * occasional functional test failure: neutron.tests.functional.privileged.agent.linux.test_utils.FindListenPidsNamespaceTestCase.test_find_listen_pids_namespace - https://bugs.launchpad.net/neutron/+bug/2110878 CI failure but seen once in gate for now * ovs-agent: Leftover tpi/spi interfaces after VM boot/delete with trunk port(s) - https://bugs.launchpad.net/neutron/+bug/2095152 Trunk ports leftover for ML2/OVS following a change for ML2/OVN, see bug for details (reproducer) Patch proposed by rubasov: https://review.opendev.org/c/openstack/neutron/+/949217 -- Bernard Cafarelli

1 0

[openstack-helm] Are there any real users of the umbrella chart?
by Vladimir Kozhukalov 17 May '25

17 May '25

Hi team, This is to start the discussion about the future of the Openstack super (umbrella) chart [1]. My personal impression (maybe I am wrong) is that this chart is of extremely little interest. We continue to maintain this code (and spend testing resources) but maybe there are no real users of it. The chart deploys a compute-kit scheme but the same result can be achieved if one deploys multiple separate charts one-by-one. It seems convenient to have this single super chart that deploys Openstack with a single command, but IMO even small operators prefer using separate charts. Having said that, I would suggest removing this chart if it is not needed. [1] https://opendev.org/openstack/openstack-helm/src/branch/master/openstack -- Best regards, Kozhukalov Vladimir

3 4

[nova] Auto-convergence but for I/O
by Winicius Allan 17 May '25

17 May '25

Is there any option for disk I/O auto-convergence like conf.libvirt.live_migration_permit_auto_converg for memory-intensive instances? The use case is for an I/O intensive VM, so the disk cannot be migrated. Instead, it is necessary to change the max IO with `$ virsh blkdeviotune` then, migrate the instance and replace the current value with the old using the same command. regards.

2 1

[release] Release countdown for week R-19
by Thierry Carrez 16 May '25

16 May '25

Development Focus ----------------- We are now past the Flamingo-1 milestone. Teams should now be focused on feature development and completion of goals [0]. [0] https://governance.openstack.org/tc/goals/selected/index.html General Information ------------------- Our next milestone in this development cycle will be Flamingo-2, on July 3rd, 2025. This milestone is when we freeze the list of deliverables that will be included in the 2025.2 Flamingo final release, so if you plan to introduce new deliverables in this release, please propose a change to add an empty deliverable file in the deliverables/flamingo directory of the openstack/releases repository. Now is also generally a good time to look at bugfixes that were introduced in the master branch that might make sense to be backported and released in a stable release. If you have any question around the OpenStack release process, feel free to ask on this mailing-list or on the #openstack-release channel on IRC. Upcoming Deadlines & Dates -------------------------- Flamingo-2 Milestone: July 3rd, 2025 -- Thierry Carrez (ttx)

1 0

[Kolla-Ansible][DockerImages] - Failing at start
by Victor Sartori 16 May '25

16 May '25

Hello All, Some containers are failing to start. All of them exhibit the same behavior: ``` + echo 'Running command: '\''uwsgi /etc/nova/nova-api-uwsgi.ini'\''' Running command: 'uwsgi /etc/nova/nova-api-uwsgi.ini' + exec uwsgi /etc/nova/nova-api-uwsgi.ini /usr/local/bin/kolla_start: line 27: exec: uwsgi: not found ``` Could this issue be related to a message posted in the OpenStack IRC? ``` -opendevstatus/#openstack- NOTICE: Setuptools 80.7.0 broke python package installs for many, affecting CI jobs. That release has been yanked, and it should be safe to recheck failed changes. ``` I see errors in the following containers: - quay.io/openstack.kolla/nova-scheduler:2024.2-ubuntu-noble - quay.io/openstack.kolla/placement-api:2024.2-ubuntu-noble - quay.io/openstack.kolla/cinder-volume:2024.2-ubuntu-noble It's likely that any container relying on uwsgi will fail. Environment: Ubuntu 24.04.2 Kernel 6.8.0-59-generic Docker CE 28.1.1 Kolla version: kolla-ansible 20.1.0.dev10 Any help?

1 0

[Kolla-Ansible][Magnum] Vexxhost CAPI no longer working
by Oliver Weinmann 16 May '25

16 May '25

Hi all, a couple of weeks ago I updated the containers in my 2023.2 release. kolla-ansible pull kolla-ansible deploy since then the Vexxhost driver in Magnum is no longer working. I have clusters stuck in provisioning and deleting: $ kubectl get cluster -A NAMESPACE NAME CLUSTERCLASS PHASE AGE VERSION magnum-system kube-6r0du magnum-v0.26.0 Provisioning 20d v1.26.7 magnum-system kube-7ljg3 magnum-v0.26.0 Provisioning 18d v1.26.7 magnum-system kube-csf6s magnum-v0.13.4 Deleting 71d v1.26.7 I believe this is due to a versionn mismatch. Many different tools are involved here. All pods in the KIND Management cluster are running: $ kubectl -n kube-system get pods NAME READY STATUS RESTARTS AGE coredns-76f75df574-lfckv 1/1 Running 5 (2d23h ago) 71d coredns-76f75df574-n85fv 1/1 Running 5 (2d23h ago) 71d etcd-magnumcapi-control-plane 1/1 Running 5 (2d23h ago) 71d kindnet-jtdtm 1/1 Running 5 (2d23h ago) 71d kube-apiserver-magnumcapi-control-plane 1/1 Running 5 (2d23h ago) 71d kube-controller-manager-magnumcapi-control-plane 1/1 Running 10 (2d23h ago) 71d kube-proxy-qwjc8 1/1 Running 5 (2d23h ago) 71d kube-scheduler-magnumcapi-control-plane 1/1 Running 9 (2d23h ago) 71d There is nothing obvious in the capi or capo logs. Is there someone that is currently running 2023.2 or newer with the Vexxhost CAPI driver? Would be great if you could share the versions of: Management Cluster $ kind --version kind version 0.22.0 $ export KUBECONFIG=~/config $ kubectl get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME magnumcapi-control-plane Ready control-plane 71d v1.29.2 172.18.0.2 <none> Debian GNU/Linux 12 (bookworm) 5.14.0-503.38.1.el9_5.x86_64 containerd://1.7.13 $ kubectl get provider -A NAMESPACE NAME AGE TYPE PROVIDER VERSION capi-kubeadm-bootstrap-system bootstrap-kubeadm 71d BootstrapProvider kubeadm v1.9.5 capi-kubeadm-control-plane-system control-plane-kubeadm 71d ControlPlaneProvider kubeadm v1.9.5 capi-system cluster-api 71d CoreProvider cluster-api v1.9.5 capo-system infrastructure-openstack 71d InfrastructureProvider openstack v0.10.8 The magnum pods: ~]# podman exec -it magnum_conductor bash ()[ /]$ pip list | grep api magnum-cluster-api 0.26.0 ()[ /]$ helm version version.BuildInfo{Version:"v3.13.2", GitCommit:"2a2fb3b98829f1e0be6fb18af2f6599e0f4e8243", GitTreeState:"clean", GoVersion:"go1.20.10"} ~]# podman exec -it magnum_api bash ()[ /]$ pip list | grep api magnum-cluster-api 0.26.0 ()[ /]$ helm version version.BuildInfo{Version:"v3.13.2", GitCommit:"2a2fb3b98829f1e0be6fb18af2f6599e0f4e8243", GitTreeState:"clean", GoVersion:"go1.20.10"} ()[ /]$ Cheers, Oliver

1 0

[neutron] Neutron drivers meeting cancelled today
by Rodolfo Alonso Hernandez 16 May '25

16 May '25

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend! [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda

1 0