February 2025 - openstack-discuss

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

25 Apr '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 8

Fwd: DPDK+OVS with OpenStack
by Mark Wittling 23 Apr '25

23 Apr '25

Looking for someone who knows OpenStack with OpenVSwitch, and in addition to that, DPDK with OpenStack and OVS.I am using OpenStack Queens, with OpenVSwitch. The architecture I am using is documented here: https://docs.openstack.org/neutron/queens/admin/deploy-ovs-provider.htmlThe OVS I am using on the Compute Node, is compiled with DPDK, and I have enabled the datapath to netdev (DPDK) on br-prv (provider network bridge), and br-tun (tunneling bridge). But these two bridges, br-tun and br-prv, are patched into another OpenStack bridge, called br-int. I wasn’t actually sure about whether to tinker with this bridge, and wondered what datapath it was using.Then, I realized there is a parameter in the openvswitch_agent.ini file, which I will list here: # OVS datapath to use. 'system' is the default value and corresponds to the # kernel datapath. To enable the userspace datapath set this value to 'netdev'. # (string value) # Possible values: # system - <No description provided> # netdev - <No description provided> #datapath_type = system datapath_type = netdev So in tinkering with this, what I realized, is that when you set this datapath_type to system or netdev, it will adjust the br-int bridge to that datapath type.So here is my question. How can I launch a non-DPDK VM, if all of the bridges are using the netdev datapath type?Here is another question. What if one of the flavors don’t have the largepages property set on them? I assumed OpenStack would revert to a system datapath and not use DPDK for those VM interfaces. Well, I found out in testing, that is not the case. If you set all your bridges up for netdev, and you don’t set the property on the Flavor of the VM (largepages), the VM will launch, but it simply won’t work.Is there no way, on a specific Compute Host, to support both DPDK (netdev datapaths) and non-DPDK (system datapaths)?Either on a VM interface level (VM has one interface that is netdev DPDK and another that is system datapath non-DPDK)?Or on a VM by VM basis (VM 1 has 1 or more netdev datapath interfaces and VM 2 has 1 or more system datapath interfaces)?Am I right here? Once you set up a Compute Host for DPDK, it’s DPDK or nothing on that Compute Host? (edited)

3 2

How to config DPDK compute in OVN
by dangerzone ar 22 Apr '25

22 Apr '25

Hi....as far I understand ovs does support dpdk compute to be deployed. I'm referring to the guideline ' *https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html <https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html>* ' ... It's too brief.. May I know how to config dpdk compute in OVN networking openstack? Hope someone could help what is the config to be done.... Currently compute is run without dpdk over openstack train ovn based. Please need some info on how I can proceed. Thank you

2 1

[oslo] python-consul2 is unmaintained
by Takashi Kajinami 21 Apr '25

21 Apr '25

Hello, I recently noticed that python-consul2 library[1], which is used by the consul coordination driver in tooz, hasn't been updated for 3+ years. Looking at issues in the project, there is an indication that the library is not compatible with ACL API in consul >= 1.11[2]. There is another fork created[3] and this includes fixes to support new API endpoints. Although the driver in tooz does not directly use the feature, I think it's better to discuss our plan to mitigate risks caused by the unmaintained library. As far as I can think of, there are three options now 1. Deprecate consul driver and remove it 2. Keep using python-consul2 now. At least basic functionality is proven to work by our functional tests (Note that the tests do not cover all configuration patterns) 3. Replace python-consul2 by py-consul Before we start the overall discussions I'd like to ask a few questions to the wider audience, as our inputs. - Is anyone using the consul coordination driver now ? - Does anyone have experience with python-consul2 and/or py-consul ? Note that this discussion affects the http messaging driver[4] currently proposed, because it also requires client library to communicate with Consul. Actually I noticed the situation when I noticed that the requirement check job is failing because the library is not part of global requirements list... Thank you, Takashi Kajinami [1] https://github.com/poppyred/python-consul2 [2] https://github.com/poppyred/python-consul2/issues/42 [3] https://github.com/criteo-forks/py-consul [4] https://review.opendev.org/c/openstack/oslo.messaging/+/912499 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

2 3

[octavia] Purging ERROR'ed amphora and load balancers stuck in transitional states
by Paul Browne 11 Apr '25

11 Apr '25

Hello Octavia users, For a while I've been trying to find a systematic way to remove Octavia LBs+Amphora that have become stuck in ERROR or transitional PENDING_* states ; $ openstack loadbalancer amphora list -f value | grep ERROR a2323f14-3aaa-418a-8249-111aaa9c21fe 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe ERROR MASTER 10.8.0.242 192.168.3.247 e5b236ba-e7ee-4ed7-9f58-57ce7a408489 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe ERROR BACKUP 10.8.0.190 192.168.3.247 6b556f28-93c9-49dd-b6ee-4379288e7957 d5e402fe-2c4b-49af-a700-532cb408cee5 ERROR MASTER 10.8.0.39 192.168.3.126 c669db5d-8686-4d5c-9e95-e02030b34301 d5e402fe-2c4b-49af-a700-532cb408cee5 ERROR BACKUP 10.8.0.174 192.168.3.126 $ openstack loadbalancer list -f value | grep -vi active 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe k8s-clusterapi-cluster-default-ci-6386871107-kube-upgrade-kubeapi 3a06571936a0424bb40bc5c672c4ccb1 192.168.3.247 PENDING_UPDATE amphora d5e402fe-2c4b-49af-a700-532cb408cee5 k8s-clusterapi-cluster-default-ci-6386871107-latest-kubeapi 3a06571936a0424bb40bc5c672c4ccb1 192.168.3.126 PENDING_DELETE amphora These resources are marked immutable and so cannot be failed over or deleted; $ openstack loadbalancer amphora failover a2323f14-3aaa-418a-8249-111aaa9c21fe Load Balancer 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe is immutable and cannot be updated. (HTTP 409) (Request-ID: req-6e66c4e8-c3d3-4549-a03c-367017c8c8b3) $ openstack loadbalancer failover 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe Invalid state PENDING_UPDATE of loadbalancer resource 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe (HTTP 409) (Request-ID: req-84b44212-e7a8-4101-a16f-18c774c0577e) The backing Nova instances for these Amphora do seem to exist and be in good working order. Is there any API way to purge these out of Octavia's service state, or would (very careful) DB hackery be required here? Many thanks, Paul Browne ******************* Paul Browne Research Computing Platforms University Information Services Roger Needham Building JJ Thompson Avenue University of Cambridge Cambridge United Kingdom E-Mail: pfb29(a)cam.ac.uk<mailto:pfb29@cam.ac.uk> Tel: 0044-1223-746548 *******************

4 6

GPU PCI passthrough woes.
by Andy Speagle 10 Apr '25

10 Apr '25

Hey Folks, I could use a little assistance getting GPU passthrough working. I had this working already for one flavor of nvidia gpu... and I've added some hosts with a much newer gpu... I've updated the pci_alias and pci_passthrough variables and those seem to be getting set properly in nova.conf passthrough_whitelist = [{"vendor_id":"10de", "product_id":"1b06"},{"vendor_id":"10de", "product_id":"26b9"}] alias = {"name": "gpu", "product_id": "1b06", "vendor_id": "10de"} alias = {"name": "gpu-l40s", "product_id": "26b9", "vendor_id": "10de"} I believe I have all of the iommu stuff configured and have the pci- stub module entries... dmesg output shows that the GPUs are being claimed by the stub module. $ openstack flavor show t1.small_gpu_l40s +----------------------------+--------------------------------------+ | Field | Value | +----------------------------+--------------------------------------+ | OS-FLV-DISABLED:disabled | False | | OS-FLV-EXT-DATA:ephemeral | 0 | | access_project_ids | None | | description | None | | disk | 0 | | id | af70c94e-0026-4a39-bc1e-dfb93b286a54 | | name | t1.small_gpu_l40s | | os-flavor-access:is_public | True | | properties | pci_passthrough:alias='gpu-l40s:1' | | ram | 2048 | | rxtx_factor | 1.0 | | swap | 0 | | vcpus | 1 | +----------------------------+--------------------------------------+ Yet... I can't seem to get an instance to run using that new flavor... keeps complaining about there not being enough hosts available. Fault: code: 500 created: 2024-10-30T02:04:33Z message: "No valid host was found. There are not enough hosts available." details: | Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nova/conductor/manager.py", line 1580, in schedule_and_build_instances host_lists = self._schedule_instances(context, request_specs[0], File "/usr/lib/python3/dist-packages/nova/conductor/manager.py", line 940, in _schedule_instances host_lists = self.query_client.select_destinations( File "/usr/lib/python3/dist- packages/nova/scheduler/client/query.py", line 41, in select_destinations return self.scheduler_rpcapi.select_destinations(context, spec_obj, File "/usr/lib/python3/dist-packages/nova/scheduler/rpcapi.py", line 160, in select_destinations return cctxt.call(ctxt, 'select_destinations', **msg_args) File "/usr/lib/python3/dist- packages/oslo_messaging/rpc/client.py", line 189, in call result = self.transport._send( File "/usr/lib/python3/dist- packages/oslo_messaging/transport.py", line 123, in _send return self._driver.send(target, ctxt, message, File "/usr/lib/python3/dist- packages/oslo_messaging/_drivers/amqpdriver.py", line 689, in send return self._send(target, ctxt, message, wait_for_reply, timeout, File "/usr/lib/python3/dist- packages/oslo_messaging/_drivers/amqpdriver.py", line 681, in _send raise result nova.exception_Remote.NoValidHost_Remote: No valid host was found. There are not enough hosts available. Traceback (most recent call last): File "/usr/lib/python3/dist- packages/oslo_messaging/rpc/server.py", line 241, in inner return func(*args, **kwargs) File "/usr/lib/python3/dist-packages/nova/scheduler/manager.py", line 223, in select_destinations selections = self._select_destinations( File "/usr/lib/python3/dist-packages/nova/scheduler/manager.py", line 250, in _select_destinations selections = self._schedule( File "/usr/lib/python3/dist-packages/nova/scheduler/manager.py", line 416, in _schedule self._ensure_sufficient_hosts( File "/usr/lib/python3/dist-packages/nova/scheduler/manager.py", line 455, in _ensure_sufficient_hosts raise exception.NoValidHost(reason=reason) nova.exception.NoValidHost: No valid host was found. There are not enough hosts available. Any clues on how/where to dig into this more to see what might be missing? Thanks. -- Andy Speagle

3 2

bug report
by Xavier Benjamin 05 Apr '25

05 Apr '25

whenever i try to connect to trove pts servers it would usually say fails to authenticate or something. Can you fix that please?

2 2

[openstack-helm] Merge openstack-helm and openstack-helm-infra git repos
by Vladimir Kozhukalov 31 Mar '25

31 Mar '25

Hi dear Openstack-Helmers, I would like to suggest merging the two project git repos: https://opendev.org/openstack/openstack-helm-infra.git https://opendev.org/openstack/openstack-helm.git At some point it seemed reasonable to have separate git repos for openstack and infrastructure charts. But now it looks like we are experiencing more cons than pros. When working on some features we are forced to prepare sets of interdependent patches. Some code can be deduplicated. Also when we publish charts we append two commit hashes as package metadata. Also we can reduce the number of test jobs if we have all chats in one repo. Other people also proposed this earlier. So if there are no objections let's make it done. I understand this is going to affect many of our users. Please express your opinions so we don't break any downstream. If we all agree about this, then I would say we can do this in the mid of March/2025 before 2025.2 PTG. The procedure is going to be smth. like 1. Freeze the infra repo and prepare retirement PSs for it 2. Merge openstack-helm-infra repo into openstack-helm ``` git clone https://opendev.org/openstack/openstack-helm.git cd openstack-helm git remote add infra https://opendev.org/openstack/openstack-helm-infra.git git fetch infra git checkout -b infra infra/master git checkout master git merge --allow-unrelated-histories infra # resolve not so many conflicts git review ``` 3. Accept merger PS 4. Update documentation 5. Accept infra retirement PSs (openstack-helm-infra and project-config) -- Best regards, Kozhukalov Vladimir

4 10

[mistral][heat][watcher][aodh] croniter being abandoned
by Thierry Carrez 22 Mar '25

22 Mar '25

Hi everyone, It was brought to my attention that the croniter maintainer has decided to abandon his project, due to not wanting to deal with his perceived exposure to the EU Cyber-Resilience act (CRA). https://pypi.org/project/croniter/#disclaimer The maintainer indicates that you should no longer use it and it may be "unpublished" any time after March 15, 2025. Croniter is being used in at least Mistral, Heat, Watcher, and Aodh as a dependency. While this is clearly an overreaction (the CRA only applies to "economic operators" putting "products with digital elements" on the market "in the course of a commercial activity"), we should probably prepare to migrate away from this dependency, or maintain a fork of it. -- Thierry Carrez (ttx)

5 8

[Devstack] Trying to setup development environment on VM
by Ishan Shanware (ishanwar) 17 Mar '25

17 Mar '25

Hello Everyone, I am currently trying to setup in all-in-one development environment for OpenStack on a Debian VM. The VM has 16 GB RAM and 4 CPUs. However, I face an error while trying to run FORCE=yes ./stack.sh. I get an error that keystone does not start. This causes the entire process to fail. Requesting assistance in solving this issue. I am following the this guide: https://docs.openstack.org/devstack/latest/guides/single-machine.html PFA the error log and error message on the terminal. [Call Trace] ./stack.sh:1126:start_keystone /opt/stack/devstack/lib/keystone:549:die [ERROR] /opt/stack/devstack/lib/keystone:549 keystone did not start Error on exit World dumping... see /opt/stack/logs/worlddump-2024-11-18-150808.txt for details ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Thanks in advance, Ishan

3 5

[all][tc][ptl][qa] Migrating upstream CI/CD jobs to Ubuntu Noble (24.04)
by Ghanshyam Mann 15 Mar '25

15 Mar '25

Hello Everyone, As per the 2025.2 cycle testing runtime, we need to run upstream CI/CD jobs on Ubuntu Noble (24.04) [1]. For better tracking and speeding up this work, it is the community-wide goal for this cycle[2]. This is the etherpad which has the migration plan and will be used for the tracking: - https://etherpad.opendev.org/p/migrate-to-noble I have prepared the change(WIP) for base jobs migration on Noble (openstack tox jobs, devstack, and tempest) which will migrate most of the projects jobs. Tempest change[3] include dependency on openstack tox, devstack base jobs changes so testing project gate using the the tempest change will test the complete set. Refer to the etherpad for the complete migration plan/steps. * Deadline: Nov 29th 2024 (R18) is the deadline to test/fix the projects jobs and to merge the base jobs running on Noble (openstck tox, devstack, and tempest). [1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html [2] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubunt… [3] https://review.opendev.org/c/openstack/tempest/+/932156 -gmann

2 9

[kolla] [nova] API flags ignored in Wallaby
by Albert Braden 13 Mar '25

13 Mar '25

After rebuilding our Train clusters on Wallaby we are seeing some API issues. It appears that flags that work in Train are still documented in Wallaby, but are ignored. Do we have something setup wrong, or are we encountering bugs? The first thing is the “locked” list: Train: openstack server list --all-projects --locked --os-compute-api-version 2.73 <empty list because nothing is locked> openstack server list --all-projects --unlocked --os-compute-api-version 2.73 <list of every VM in the cluster> Wallaby (locked flag is ignored): openstack server list --all-projects --locked --os-compute-api-version 2.73 <list of every VM in the cluster> openstack server list --all-projects --unlocked --os-compute-api-version 2.73 <list of every VM in the cluster> The second problem is the hypervisor list. We can’t get “long” output in Wallaby: Train: openstack hypervisor list --long | ID | Hypervisor Hostname | Hypervisor Type | Host IP | State | vCPUs Used | vCPUs | Memory MB Used | Memory MB | Wallaby (long flag is ignored): openstack hypervisor list --long | ID | Hypervisor Hostname | Hypervisor Type | Host IP | State |

6 14

[all] Important discussion about the OpenInfra Foundation's future
by Jeremy Stanley 12 Mar '25

12 Mar '25

The OpenInfra Foundation's board of directors is considering a significant organizational change, and your feedback is critical to assist them in their decision. Please read this announcement on the foundation mailing list: https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/th… You can follow up publicly on that list with any questions or input you have for the board and staff, or in one of the public feedback conference calls mentioned there, as well as privately to Jonathan Bryce or myself if you prefer to give feedback in confidence. Thanks as always for your interest in the future of our community! -- Jeremy Stanley -- Jeremy Stanley

4 11

Confidential VM and TDX support in upstream Openstack
by Ildiko Vancsa 12 Mar '25

12 Mar '25

Hi, I'm reaching out about a topic that came up in the Kata Containers / Confidential Containers communities related to a feature in Kata that is called remote hypervisor and also referred to as peer pods. Kata provides an API that allows users to implement a function to run Kata Containers pods in a remote location, which can include a different host machine or cloud environment. The Cloud API Adaptor in the Confidential Containers project is an implementation of the Kata remote hypervisor interface: https://github.com/confidential-containers/cloud-api-adaptor It recently came up to add support for OpenStack to be a cloud option to run Kata remote VMs in. In order to implement that, OpenStack would need to support the creation of Confidential VMs (CVM) along with things like TDX. I looked around and found 3rd-party implementation to add TDX support to Nova, but the repo has been archived: https://github.com/intel/secured-cloud-management-stack/blob/main/scm3.0/no… Does anyone know if the CVM support along with supporting Intel TDX or related technologies have been added to OpenStack already? Or if there's anyone in the community planning for adding these in the future? Thanks and Best Regards, Ildikó

4 4

Assistance Required: OpenStack Helm Deployment (Version 2023.1) Compatibility Issues
by Thamanna Farhath 06 Mar '25

06 Mar '25

Hello OpenStack Community, I hope you are doing well. I am currently deploying OpenStack on top of a Kubernetes cluster using OpenStack Helm and aiming to install the 2023.1 (Antelope) version. However, I am facing difficulties in installing this specific version via Helm charts. Despite my attempts, I have not been able to successfully deploy the required OpenStack services for this release. Additionally, I am ensuring that the dependent services, such as RabbitMQ, align with the compatibility requirements of OpenStack 2023.1. As per the OpenStack documentation, RabbitMQ 3.11 is the recommended version, but I encountered issues while deploying it. Instead, I found that RabbitMQ 3.12 works without any issues. I would like to know: Is there a way to install OpenStack 2023.1 properly using Helm charts, or should I consider using a newer OpenStack version? Will using RabbitMQ 3.12 instead of 3.11 cause any potential issues with OpenStack services, or is it safe to proceed with this version? Are there any known workarounds or recommendations for deploying OpenStack 2023.1 using Helm? I would appreciate any guidance, best practices, or documentation references that could help resolve these challenges. Looking forward to your valuable insights. 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."

4 6

Remove config drive of instances
by Pardhiv Karri 03 Mar '25

03 Mar '25

Hi, We are on the Openstack Queens version. We added the config drive option during its build but never used it. How can we remove it? The "OpenStack server delete --no-config-drive" option isn't available due to the older version we are using. What is the best way to eliminate it, hopefully without rebooting the instances? Thanks, IM

4 7

[release] Release countdown for week R-4, Mar 03 - 07
by Elõd Illés 28 Feb '25

28 Feb '25

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the 2025.1 Epoxy deliverables can be proposed, well ahead of the final 2025.1 Epoxy release date. General Information ------------------- We are still finishing up processing a few release requests, but the 2025.1 Epoxy release requirements are now frozen. If new library releases are needed to fix release-critical bugs in 2025.1 Epoxy, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in 2025.1 Epoxy that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By March 27th, 2025 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/2025.1 branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for 2025.1 Epoxy changes should be added there to make sure the consumers of your release notes see them. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 14th, 2025 (R-3 week) Final RC deadline: March 28th, 2025 (R-1 week) Final 2025.1 Epoxy release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 Előd Illés irc: elodilles @ #openstack-release

3 2

[Neutron][operators] LinuxBridge to OVN Outreach
by Daniel Failing 28 Feb '25

28 Feb '25

Hi all, Following on the good session we had last time discussing migrating out of LinuxBridge between operators, I would propose to meet again the first or second week of March. To find a good time slot, please respond to the following survey: https://newdle.cern.ch/newdle/7XbH4fCd For reference, the notes from last meeting: https://etherpad.opendev.org/p/neutron-lb-ovn-migration Best, Daniel Failing CERN Cloud Infrastructure

1 1

[kolla] IRC meeting cancelled - 5-th of March 2025
by Bartosz Bezak 28 Feb '25

28 Feb '25

Hi. Due to OpenInfra US conference related travel, Kolla IRC meeting on 5-th of March is cancelled. Best regards, Bartosz Bezak

1 0

Issues with installing Zun on Compute node
by Vaibhav 28 Feb '25

28 Feb '25

I was trying to install openstack 2024.2 zun on compute node. and following the page https://docs.openstack.org/zun/2024.2/install/compute-install.html for installation. I am facing the issue of docker "--cluster-store" support. I am using Docker 27.5 version. Reading the documentation online, i am confused. Some places it is, mentioned that it is fixed. and some places it suggest to uses docker 22. At few places in your mail you have mentioned to stop using kuryr and use CNI. And official documentation still says to use --cluster store. What is the current state and the correct solution. Please guide me. Vaibhav

3 3

[Openstack-ansible][cinder-volume] deletion of snapshot after creating a volume from it..
by Danish Khan 28 Feb '25

28 Feb '25

Dear All, Is there a way we can delete a volume who has a snapshot available? I have created a volume from snapshot and now we have a full chain of snapshots and volumes that we can't delete. But I need only the last volume to be available. If not then what is the best use case for snapshot? or Should I assume that if I create a snapshot and then create a volume from that snapshot then I need to keep the old volume and snapshot always. Regards, Danish

2 1

[neutron] Drivers meeting canceled Friday, February 28th
by Brian Haley 28 Feb '25

28 Feb '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as discussed at this week's meeting, plan is to have one next week. Just a reminder there are still open specs that need review, list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

Problem to delete volume backup
by franck 28 Feb '25

28 Feb '25

2 1

[oslo][release][requirements] RFE for taskflow
by Herve Beraud 27 Feb '25

27 Feb '25

Hello, During this cycle we started to deprecat eventlet support in oslo deliverables However one patch missed the epoxy train [1]. We'd like to request approval about the release and also bumping taksflow version in stable/2025.1 requirements to properly align all our deliverables about eventlet support. Thank you in advance for your feedback. [1] https://review.opendev.org/c/openstack/taskflow/+/940884 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

4 3

Assistance Required: OpenStack Helm Deployment (Version 2023.1) Compatibility Issues
by Thamanna Farhath 27 Feb '25

27 Feb '25

Hello OpenStack Community, I hope you are doing well. I am currently deploying OpenStack on top of a Kubernetes cluster using OpenStack Helm and aiming to install the 2023.1 (Antelope) version. However, I am facing difficulties in installing this specific version via Helm charts. Despite my attempts, I have not been able to successfully deploy the required OpenStack services for this release. Additionally, I am ensuring that the dependent services, such as RabbitMQ, align with the compatibility requirements of OpenStack 2023.1. As per the OpenStack documentation, RabbitMQ 3.11 is the recommended version, but I encountered issues while deploying it. Instead, I found that RabbitMQ 3.12 works without any issues. I would like to know: Is there a way to install OpenStack 2023.1 properly using Helm charts, or should I consider using a newer OpenStack version? Will using RabbitMQ 3.12 instead of 3.11 cause any potential issues with OpenStack services, or is it safe to proceed with this version? Are there any known workarounds or recommendations for deploying OpenStack 2023.1 using Helm? I would appreciate any guidance, best practices, or documentation references that could help resolve these challenges. Looking forward to your valuable insights. Associate Engineer-R&D Thamanna Farhath N Cn: (+91) 9344093591 , thamanna.f(a)zybisys.com Zybisys Consulting LLP | Srinivasa Tower' No.29, 39th E Cross, 4th T Block, Jayanagar , Bangalore India – 560041 http://zybisys.com/ 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

[openstack][kolla ansible]ask about Enhance Ceph Integration for Multiple Clusters backport
by Nguyễn Hữu Khôi 27 Feb '25

27 Feb '25

Hello folks. I would like to know if we have a plan for Enhance Ceph Integration for Multiple Clusters port? https://review.opendev.org/c/openstack/kolla-ansible/+/907166 Thank you. Regards Nguyen Huu Khoi

2 6

[all] CI resources usage optimization
by Sławek Kapłoński 27 Feb '25

27 Feb '25

Hi, In of of the recent weekly TC meetings we have discussed usage of our CI resources by projects. After that discussion I did small script [1] to get some more data about it. I checked separately how much nodes and "nodehours" are projects using in the check and gate queue to validate patches. Full results for the time rage 01.01.2025 to 13.02.2025 are in [2] for the check queue and in [3] for the gate queue. 1 "nodehour" means that 1 CI node was busy for 1 hour running job. This email is of course not sent just to tell team to cut their testing coverage but if you can take a closer look at your project's CI jobs configuration, maybe there is some way to improve it easily. For example if you have jobs running as non-voting for long time, maybe you can think of moving them to the experimental or periodic queue instead of running it in the check queue for every patch (or make it voting). This may be one of those small steps to optimize things a bit and make our own live easier as less load on infra means more stable jobs in general. Below there are results of the top 50 projects based on the "nodehours" per patch # Check queue +--------------------------------------------------+-------------------+------------------+----------------------------+-----------------------+---------------------------------+ | Project | Number of patches | Total Nodes used | Total time used [nodehour] | Nodes per patch (avg) | Time per patch (avg) [nodehour] | +--------------------------------------------------+-------------------+------------------+----------------------------+-----------------------+---------------------------------+ | openstack/openstack-ansible-rabbitmq_server | 2 | 72 | 90:06:07 | 36.00 | 45:03:03 | | openstack/octavia-tempest-plugin | 4 | 128 | 164:35:45 | 32.00 | 41:08:56 | | openstack/openstack-ansible-haproxy_server | 3 | 90 | 119:12:36 | 30.00 | 39:44:12 | | openstack/tacker | 14 | 1667 | 506:49:12 | 119.07 | 36:12:05 | | openstack/openstack-ansible-os_neutron | 8 | 204 | 289:32:21 | 25.50 | 36:11:32 | | openstack/openstack-ansible-os_keystone | 3 | 81 | 106:46:15 | 27.00 | 35:35:25 | | openstack/kolla-ansible | 130 | 8461 | 4491:25:21 | 65.08 | 34:32:57 | | openstack/openstack-ansible-os_octavia | 4 | 80 | 135:50:31 | 20.00 | 33:57:37 | | openstack/openstack-ansible | 31 | 872 | 1012:42:34 | 28.13 | 32:40:04 | | openstack/openstack-ansible-os_horizon | 5 | 115 | 162:39:57 | 23.00 | 32:31:59 | | openstack/openstack-ansible-os_aodh | 3 | 66 | 94:01:09 | 22.00 | 31:20:23 | | openstack/openstack-ansible-os_glance | 3 | 69 | 92:57:56 | 23.00 | 30:59:18 | | openstack/openstack-ansible-os_cinder | 3 | 63 | 86:19:38 | 21.00 | 28:46:32 | | openstack/openstack-ansible-os_magnum | 3 | 63 | 84:34:05 | 21.00 | 28:11:21 | | openstack/openstack-ansible-os_cloudkitty | 3 | 48 | 78:30:50 | 16.00 | 26:10:16 | | openstack/openstack-ansible-os_ironic | 6 | 93 | 153:06:27 | 15.50 | 25:31:04 | | openstack/openstack-ansible-os_barbican | 3 | 54 | 76:32:05 | 18.00 | 25:30:41 | | openstack/openstack-ansible-os_gnocchi | 2 | 32 | 51:00:15 | 16.00 | 25:30:07 | | openstack/openstack-ansible-os_ceilometer | 3 | 48 | 75:49:07 | 16.00 | 25:16:22 | | openstack/openstack-ansible-os_swift | 3 | 54 | 75:37:56 | 18.00 | 25:12:38 | | openstack/openstack-ansible-os_skyline | 5 | 89 | 124:53:18 | 17.80 | 24:58:39 | | openstack/openstack-ansible-os_placement | 2 | 36 | 49:46:31 | 18.00 | 24:53:15 | | openstack/tempest | 26 | 854 | 633:21:36 | 32.85 | 24:21:36 | | openstack/openstack-ansible-os_designate | 3 | 51 | 72:30:14 | 17.00 | 24:10:04 | | openstack/openstack-ansible-os_tempest | 2 | 36 | 47:27:46 | 18.00 | 23:43:53 | | openstack/openstack-ansible-os_mistral | 3 | 51 | 71:06:02 | 17.00 | 23:42:00 | | openstack/openstack-ansible-os_heat | 3 | 51 | 70:23:53 | 17.00 | 23:27:57 | | openstack/openstack-ansible-os_blazar | 2 | 32 | 46:30:44 | 16.00 | 23:15:22 | | openstack/openstack-ansible-os_masakari | 3 | 48 | 68:52:54 | 16.00 | 22:57:38 | | openstack/ansible-role-systemd_networkd | 13 | 277 | 297:37:09 | 21.31 | 22:53:37 | | openstack/ironic-tempest-plugin | 12 | 398 | 271:54:14 | 33.17 | 22:39:31 | | openstack/openstack-ansible-galera_server | 5 | 111 | 112:28:29 | 22.20 | 22:29:41 | | openstack/openstack-ansible-os_nova | 3 | 51 | 66:54:40 | 17.00 | 22:18:13 | | openstack/openstack-ansible-os_rally | 2 | 32 | 44:20:06 | 16.00 | 22:10:03 | | openstack/cinder | 127 | 3518 | 2746:32:43 | 27.70 | 21:37:34 | | openstack/openstack-ansible-os_tacker | 3 | 45 | 63:03:01 | 15.00 | 21:01:00 | | openstack/octavia | 38 | 917 | 764:50:26 | 24.13 | 20:07:38 | | openstack/cinder-tempest-plugin | 13 | 176 | 241:51:59 | 13.54 | 18:36:18 | | openstack/neutron-tempest-plugin | 8 | 129 | 147:41:46 | 16.12 | 18:27:43 | | openstack/devstack | 24 | 536 | 442:16:49 | 22.33 | 18:25:42 | | openstack/neutron | 186 | 3580 | 3283:39:42 | 19.25 | 17:39:14 | | openstack/nova | 251 | 6527 | 4383:59:41 | 26.00 | 17:27:58 | | openstack/openstack-ansible-plugins | 7 | 127 | 116:04:29 | 18.14 | 16:34:55 | | openstack/openstack-ansible-repo_server | 5 | 72 | 82:42:24 | 14.40 | 16:32:28 | | openstack/ironic | 79 | 2159 | 1284:28:46 | 27.33 | 16:15:33 | | openstack/ansible-role-systemd_service | 3 | 52 | 46:55:01 | 17.33 | 15:38:20 | | openstack/manila | 36 | 856 | 561:16:54 | 23.78 | 15:35:28 | | openstack/bifrost | 6 | 164 | 93:30:55 | 27.33 | 15:35:09 | | openstack/kolla | 35 | 997 | 530:29:59 | 28.49 | 15:09:25 | | openstack/glance | 43 | 718 | 616:18:37 | 16.70 | 14:19:58 | | openstack/manila-tempest-plugin | 13 | 177 | 178:58:11 | 13.62 | 13:46:00 | # Gate queue +--------------------------------------------------+-------------------+------------------+----------------------------+-----------------------+-------------------------16:35:44 [270/9949] | Project | Number of patches | Total Nodes used | Total time used [nodehour] | Nodes per patch (avg) | Time per patch (avg) [nodehour] | +--------------------------------------------------+-------------------+------------------+----------------------------+-----------------------+---------------------------------+ | openstack/openstack-ansible-rabbitmq_server | 1 | 31 | 32:04:31 | 31.00 | 32:04:31 | | openstack/octavia-tempest-plugin | 2 | 38 | 43:36:32 | 19.00 | 21:48:16 | | openstack/openstack-ansible-galera_server | 3 | 60 | 64:21:11 | 20.00 | 21:27:03 | | openstack/openstack-ansible-os_keystone | 1 | 18 | 20:01:48 | 18.00 | 20:01:48 | | openstack/openstack-ansible | 24 | 460 | 462:28:00 | 19.17 | 19:16:10 | | openstack/openstack-ansible-repo_server | 5 | 76 | 91:39:29 | 15.20 | 18:19:53 | | openstack/openstack-ansible-os_horizon | 3 | 39 | 52:58:46 | 13.00 | 17:39:35 | | openstack/openstack-ansible-plugins | 3 | 48 | 51:28:19 | 16.00 | 17:09:26 | | openstack/openstack-ansible-os_aodh | 1 | 13 | 16:30:26 | 13.00 | 16:30:26 | | openstack/openstack-ansible-os_octavia | 2 | 24 | 32:52:12 | 12.00 | 16:26:06 | | openstack/openstack-ansible-os_neutron | 4 | 61 | 65:06:05 | 15.25 | 16:16:31 | | openstack/openstack-ansible-os_cinder | 1 | 12 | 15:51:46 | 12.00 | 15:51:46 | | openstack/nova | 91 | 1788 | 1326:41:46 | 19.65 | 14:34:44 | | openstack/tempest | 8 | 181 | 116:36:02 | 22.62 | 14:34:30 | | openstack/openstack-ansible-os_glance | 1 | 13 | 14:28:12 | 13.00 | 14:28:12 | | openstack/openstack-ansible-os_skyline | 3 | 34 | 41:15:36 | 11.33 | 13:45:12 | | openstack/neutron | 87 | 1149 | 1033:31:12 | 13.21 | 11:52:46 | | openstack/openstack-ansible-lxc_container_create | 1 | 19 | 11:49:22 | 19.00 | 11:49:22 | | openstack/openstack-ansible-os_ironic | 4 | 36 | 46:49:08 | 9.00 | 11:42:17 | | openstack/devstack | 11 | 183 | 121:32:26 | 16.64 | 11:02:56 | | openstack/openstack-ansible-lxc_hosts | 2 | 27 | 22:00:46 | 13.50 | 11:00:23 | | openstack/ansible-role-httpd | 1 | 17 | 10:55:36 | 17.00 | 10:55:36 | | openstack/openstack-ansible-os_swift | 1 | 9 | 10:54:59 | 9.00 | 10:54:59 | | openstack/kolla-ansible | 44 | 847 | 468:00:27 | 19.25 | 10:38:11 | | openstack/ironic-tempest-plugin | 7 | 121 | 73:14:18 | 17.29 | 10:27:45 | | openstack/openstack-ansible-os_barbican | 1 | 9 | 10:22:22 | 9.00 | 10:22:22 | | openstack/openstack-ansible-os_heat | 1 | 9 | 10:20:01 | 9.00 | 10:20:01 | | openstack/openstack-ansible-os_ceilometer | 1 | 9 | 10:18:23 | 9.00 | 10:18:23 | | openstack/bifrost | 6 | 108 | 60:34:38 | 18.00 | 10:05:46 | | openstack/openstack-ansible-os_masakari | 1 | 9 | 10:00:38 | 9.00 | 10:00:38 | | openstack/ansible-role-systemd_networkd | 11 | 136 | 109:26:42 | 12.36 | 09:56:58 | | openstack/openstack-ansible-os_cloudkitty | 1 | 9 | 09:56:58 | 9.00 | 09:56:58 | | openstack/openstack-ansible-os_designate | 1 | 9 | 09:54:08 | 9.00 | 09:54:08 | | openstack/openstack-ansible-os_mistral | 1 | 9 | 09:50:16 | 9.00 | 09:50:16 | | openstack/openstack-ansible-os_tacker | 1 | 9 | 09:38:43 | 9.00 | 09:38:43 | | openstack/kolla | 14 | 223 | 134:48:14 | 15.93 | 09:37:43 | | openstack/openstack-ansible-os_magnum | 1 | 9 | 09:11:37 | 9.00 | 09:11:37 | | openstack/openstack-ansible-openstack_hosts | 1 | 12 | 08:58:07 | 12.00 | 08:58:07 | | openstack/openstack-ansible-os_nova | 1 | 9 | 08:49:26 | 9.00 | 08:49:26 | | openstack/swift | 21 | 484 | 180:31:42 | 23.05 | 08:35:47 | | openstack/neutron-lib | 10 | 94 | 82:54:52 | 9.40 | 08:17:29 | | openstack/ansible-role-pki | 3 | 40 | 24:50:35 | 13.33 | 08:16:51 | | openstack/kayobe | 21 | 372 | 173:09:54 | 17.71 | 08:14:45 | | openstack/glance | 12 | 140 | 94:42:31 | 11.67 | 07:53:32 | | openstack/openstack-ansible-os_trove | 1 | 6 | 07:50:27 | 6.00 | 07:50:27 | | openstack/ansible-role-python_venv_build | 1 | 6 | 07:34:53 | 6.00 | 07:34:53 | | openstack/ironic | 46 | 671 | 337:51:59 | 14.59 | 07:20:41 | | x/devstack-plugin-tobiko | 6 | 57 | 42:46:30 | 9.50 | 07:07:45 | | openstack/cinder | 20 | 204 | 136:59:33 | 10.20 | 06:50:58 | | openstack/requirements | 47 | 1404 | 320:35:23 | 29.87 | 06:49:15 | | openstack/placement | 4 | 49 | 27:11:05 | 12.25 | 06:47:46 | [1] https://github.com/slawqo/tools/blob/master/jobs_time/infra_usage_stats.py [2]https://paste.opendev.org/show/bzS4jJgGxMq9UUBfwKNn/ [3] https://paste.opendev.org/show/bbrKIKUAGiHsntU1cQ7L/ -- Slawek Kaplonski Principal Software Engineer Red Hat

3 2

[manila] 2025.1 Epoxy Bugsuqash - Mar 3 - 4th
by Carlos Silva 27 Feb '25

27 Feb '25

Hello, Zorillas and interested stackers, Next week, the Zorillas will be meeting for the second bugsquash of the 2025.1 Epoxy cycle. Next week's bugsquash will be focused on stale bugs. We will have a kickoff meeting on Monday (March 3rd) at 15 UTC using meetpad [1], and work on the list of bugs. [1] https://meetpad.opendev.org/manila-epoxy-bugsquash Looking forward to it! carloss

1 0

[oslo][release][requirements] RFE for oslo.db and oslo.service
by Takashi Kajinami 27 Feb '25

27 Feb '25

Hi ! We've identified a few regressions in the latest Epoxy release of oslo libraries, and these are currently blocking a few projects such as octavia or watcher. We already published a new releases with the required fixes. Although we already passed the requirement freeze, I'd like to request a freeze exception to unblock the affected projects. I'm specifically talking about the following two requirement bumps. oslo.db https://review.opendev.org/c/openstack/requirements/+/942829 fixes https://launchpad.net/bugs/2099908 oslo.service https://review.opendev.org/c/openstack/requirements/+/942830 fixes https://launchpad.net/bugs/2099955 Please let me know if you have any question, and I appreciate your help ! -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

2 1

[all][elections][tc] 2025.2/F Technical Committee Election Results
by Sławek Kapłoński 26 Feb '25

26 Feb '25

Hi, Please join me in congratulating the 5 newly elected members of the Technical Committe (TC). * Amy Marrich (spotz) * Artem Goncharov (gtema) * Goutham Pacha Ravi (gouthamr) * Dmitriy Rabotyagov (noonedeadpunk) * Michal Nasiadka (mnasiadka) Election: no election required. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. Slawek Kaplonski on behalf of the OpenStack Technical Election Officials

1 0

[all][elections][ptl] 2025.2/F: PTL Election Conclusion & Results
by Sławek Kapłoński 26 Feb '25

26 Feb '25

Hi, Thank you to the electorate, and to all candidates who put their name forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. Now for the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Adjutant - Dale Smith (dalees) * Blazar - Matt Crees (mattcrees) * Cinder - Jon Bernard () * Cloudkitty - Rafael Weingartner () * Cyborg - alex song (songwenping) * Designate - Omer Schwartz (oschwart) * Glance - Cyril Roelandt (croelandt) * Heat - Takashi Kajinami (tkajinam) * Horizon - Tatiana Ovchinnikova (tmazur) * Keystone - Artem Goncharov (gtema) * Kolla - Michal Nasiadka (mnasiadka) * Magnum - Dale Smith (dalees) * Manila - Carlos Silva (carloss) * Mistral - Axel Vanzaghi (avanzaghi) * Monasca - Hasan Acar () * Neutron - Brian Haley (haleyb) * Nova - René Ribaud (rribaud) * Octavia - Michael Johnson (johnsom) * OpenStack Helm - Vladimir Kozhukalov (kozhukalov) * OpenStackAnsible - Dmitriy Rabotyagov (noonedeadpunk) * OpenStackSDK - Artem Goncharov (gtema) * Puppet OpenStack - Takashi Kajinami (tkajinam) * Quality Assurance - Ghanshyam Mann (gmann) * Rally - Andrey Kurilin (andreykurilin) * Skyline - Wenxiang Wu (wu_wenxiang) * Storlets - Takashi Kajinami (tkajinam) * Sunbeam - Hemanth Nakkina (hemanth-n) * Swift - Tim Burke (timburke) * Tacker - Yasufumi Ogawa (yasufum) * Telemetry - Juan Larriba (jlarriba) * Trove - Wu Chunyang (wuchunyang) * Venus - Sirui Jia () * Vitrage - Dmitriy Rabotyagov (noonedeadpunk) * Zun - Hongbin Lu () Elections: no election required. For remaining projects (without PTL candidates), TC will work on the appointment. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all involved in the PTL election process, Slawek Kaplonski, on behalf of the OpenStack Technical Election Officials

1 0

[release][swift][horizon][ironic] Deliverables missing Epoxy releases
by Thierry Carrez 26 Feb '25

26 Feb '25

Hi everyone, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the 2025.1 Epoxy cycle: swift horizon bifrost ironic-inspector ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch Those should be released ASAP, and in all cases before March 14th, so that we have a release to include in the final 2025.1 Epoxy release. -- Thierry Carrez (ttx)

2 1

[openstack-helm] Retire Senlin chart
by Vladimir Kozhukalov 26 Feb '25

26 Feb '25

Hi team, This is to suggest retiring the senlin chart. The project is retired now and there has been little interest in this chart recently. So I believe we can remove the chart painlessly. Opinions are welcome. -- Best regards, Kozhukalov Vladimir

3 2

[publiccloud-sig] Next meeting of Public Cloud SIG upcoming - February 26th at 0800 UTC
by Felix Kronlage-Dammers 25 Feb '25

25 Feb '25

Hi everyone, This upcoming Wednesday (February 26th) the next meeting of the publiccloud-sig is going to happen. We’ll be meeting at 0800 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG See ya Wednesday (depending on the timezone, this is tomorrow ;) ! 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

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-5)
by Goutham Pacha Ravi 25 Feb '25

25 Feb '25

Hello Stackers, We're a couple of days away from milestone-3 of the 2025.2 ("Epoxy") release cycle [1]. For OpenStack project teams with deliverables following the "cycle-with-rc" release model [2], 2025-02-27 marks a Feature Freeze [2]. Client software releases are also due on this date, and from next week, we'll be actively squashing bugs to tag and ship release candidates. Last week, we concluded the nomination period for project leaders for 40+ OpenStack project teams and for 5 seats on the Technical Committee. We have just enough or fewer nominees than there are positions. Since no polls are needed, Ian Y Choi (ianychoi) and Slawek Kaplonski (slaweq), our election officials, are working with the TC to conclude the process. The TC will also work with project teams to appoint leaders for projects where there were no PTL nominees during the nomination window. More details about this will be shared on this mailing list as soon as they are available. Also, in the past week, the TC made some governance changes regarding the Ironic project. Several project contributors stepped up to be liaisons and adopt the Distributed Project Leadership model for the upcoming release [3]. The team also deprecated ironic-lib [4], as its relevant code has moved into the Ironic service and Ironic Python Agent. === Weekly Meeting === The TC met on OFTC's #openstack-tc channel on 2025-02-18 [5]. Ghanshyam Mann (gmann) and Artem Goncharov (gtema) noted their collaboration with the OSLO project team to expand the core team of the openstackdocstheme and os-api-ref repositories. This expansion is expected to support work to create OpenAPI specifications for OpenStack API services. We discussed the kinds of contributions that qualify individuals as Active Contributors, making them eligible to vote or contest in OpenStack elections. This follows our recent inclusion of governance repositories in the list of repositories counted for contributions. We encouraged project teams to actively nominate additional contributors—those who support their teams through invaluable work such as code review, bug grooming, documentation, mentoring, managing trackers, events, and communication. This can be done by adding "extra-acs" to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-AC freeze. The freeze has passed for the 2025.1 release cycle; however, you can propose Extra-ACs for the upcoming cycle now. Besides being eligible as candidates and voters, Extra-ACs will also appear on the release contributor list. We also brought up patches proposing to tag "end-of-life" for "unmaintained" branches: Wallaby [6], Xena [7], and Yoga [8]. These patches will remain open for 30 days, allowing contributors who wish to maintain these branches to step up. If no objections arise, these patches will be merged, and the branches will be deleted. Finally, we analyzed recent CI usage statistics and found that some projects, such as openstack/tacker, had significantly high node usage (averaging 119 nodes per patch in the check queue), consuming approximately 25% of the total aggregate quota. We will summarize our findings in a separate post to this list. The next IRC meeting of the OpenStack TC will be held today, 2025-02-25, at 1800 UTC in the #openstack-tc channel on OFTC. Please find the agenda in the meeting wiki [9]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== - Switch Ironic to Distributed Leadership | https://review.opendev.org/c/openstack/governance/+/941935 - Cleanup policy popup leads list | https://review.opendev.org/c/openstack/governance/+/941148 - Deprecate ironic-lib | https://review.opendev.org/c/openstack/governance/+/939278 ==== Open for Review ==== - Add TC/PTL results from 2025.2 election | https://review.opendev.org/c/openstack/governance/+/942507 - Add Extra-ACs to the tech committee repos | https://review.opendev.org/c/openstack/governance/+/942296 - Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === Upcoming Events === - 2025-02-28: 2025.1 ("Epoxy") Feature Freeze and release milestone 3 [1] - 2025-03-06: SCALE 2025 + OpenInfra Days NA (https://www.socallinuxexpo.org/scale/22x) - 2025-03-11: OpenInfra Board Meeting: https://board.openinfra.org/ - 2025-04-07: OpenInfra PTG Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] "cycle-with-rc" release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [2] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [3] Switch Ironic to Distributed Leadership: https://review.opendev.org/c/openstack/governance/+/941935 [4] Deprecate ironic-lib: https://review.opendev.org/c/openstack/governance/+/939278 [5] TC Meeting IRC Log 2025-02-18: https://meetings.opendev.org/meetings/tc/2025/tc.2025-02-04-18.00.log.html [6] Transition unmaintained/wallaby to EOL: https://review.opendev.org/c/openstack/releases/+/941458 [7] Transition unmaintained/xena to EOL: https://review.opendev.org/c/openstack/releases/+/942201 [8] Transition unmaintained/yoga to EOL: https://review.opendev.org/c/openstack/releases/+/942218 [9] TC Meeting Agenda, 2025-02-25: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[nova]Intel RDT CAT Support Missing from OpenStack
by Junya Noguchi (Fujitsu) 25 Feb '25

25 Feb '25

To whom it may concern I have a question regarding the lack of Intel RDT CAT implementation in OpenStack We are planning to commit Resource Monitoring functionality to Openstack for ARM, and are exploring the implementation of Intel RDT on Openstack. We found the following blueprint for the Intel RDT CAT implementation in nova. https://blueprints.launchpad.net/nova/+spec/cat-support However, the Intel RDT CAT feature is not currently implemented in OpenStack. Has the implementation of Intel RDT CAT functionality in Openstack been rejected? Or is it just a development delay? Best regards, Junya Noguchi.

5 9

Keystone Tokenless
by Ryan Belgrave 25 Feb '25

25 Feb '25

Hey All! I've been reading the documentation here https://docs.openstack.org/keystone/latest/admin/configure_tokenless_x509.h… and poking through the Keystone code to figure out how tokenless authentication works. However, It doesn't seem like tokenless auth can be used as a full replacement for usernames and passwords when using ephemeral users? I can manage to get a role assignment created that allows tokenless to work for domain and project scopes but it doesn't seem possible to set up tokenless for the system scope. Without system scope I can't list catalog services or get their endpoints. Re-reading through the documentation it says: This feature is designed to reduce the complexity of user token validation in Keystone auth_token middleware by eliminating the need for service user token for authentication and authorization. Which seems like tokenless should only be used for user token validation and nothing else. It doesn't look like this auth mechanism can be used in the same manner as others for service-to-service communication? I can't really tell if I am doing something wrong or my understanding of the documentation is correct and it should only be used for user token validation. If tokenless should only be used for user token validation are there any plans to support it normally as a full replacement of usernames and passwords? Thanks! - Ryan

1 0

some more Mistral questions.
by Alvin Starr 24 Feb '25

24 Feb '25

I am trying to create a VM with an attached volume. Does someone have a pointer to or an example of a workflow that creates a volume. -- Alvin Starr || land: (647)478-6285 Netvel Inc. || home: (905)513-7688 alvin(a)netvel.net ||

2 2

#eventle-removal - Progress & Updates Epoxy Milestones 2-3
by Herve Beraud 24 Feb '25

24 Feb '25

Today we wanted to share with you the latest updates on our ongoing efforts to phase out Eventlet across our various OpenStack projects. Below you’ll find a summary of our progress, key milestones, and important dates to keep in mind as we continue to move forward with this critical initiative. ## Current Status The lib freeze is next week and we are close from milestone 3. At the time I wrote these lines 105 eventlet removal patches have been submitted on our gerrit and 61 patches are now merged. That shows really good progress. https://review.opendev.org/q/prefixtopic:%22eventlet-removal%22 Eventlet is now in version 0.39.0 and is compatible and ready to be used with Python 3.13, meaning that we are ready for an upgrade of our runtimes within the coming series. ## Achievements Among all the contributions, we can highlight these achievements: - 2 deliverables are now completely migrated: python-manilaclient and mistral-lib; - Neutron implemented their new socket server in replacement of the eventlet WSGI features and they started to migrate their OVN agent other that new server; - Mistral has made excellent progress and significantly reduced their usages of Eventelt. From moving from coroutines to threading, or migrating their messaging executor. We will been soon able to consider mistral as fully migrated; - Glance started a wide clean up of Eventlet into their functional tests; - oslo.service's backend mechanism is now implemented and the Eventlet isolation as been merged, opening the door of its refactoring based on threading; - Almost all Oslo deliverables (apart oslo.vmware) deprecated Eventlet from their usages; - Eventlet's support of Python 3.13 has been implemented and released; - Eventlet stabilization works have been done during the past months and we now observe less negative feedback and less new bugs. No news, good news; - The community goal is now selected, officializing the starting of this initiative. ## Latest Updates There are side conversations concerning the deprecation/removal of oslo.rootwrap and oslo.vmware. Those both deliverables rely on Eventlet and are in some way considered as deprecated or experimental. In parallel to that, we think we should also have a discussion about heat and heat-templates. The activity of these projects seems quite slow and (do not hesitate to correct me if I'm wrong) they are more or less in a way to be replaced with more modern ways to orchestrate OpenStack. Should we not prioritize their deprecation or at least start a wider discussion about their fate? ## Call to Action Epoxy is a SLURP series, and as we are close from lib freeze and from milestone 3, that's the right time to prioritize your deprecations in your deliverables in view of removing these pieces with non-SLURP series. The sooner they are deprecated the better. ## Important Dates Please do not hesitate to join us during our bi-weekly meeting on #openstack-eventlet-removal. Bring your own topics and do not hesitate to ask questions. All the details are available in the links below: - https://wiki.openstack.org/wiki/Eventlet-removal#Recurring_Events - https://etherpad.opendev.org/p/epoxy-eventlet-tracking ## Final Thoughts This series strongly demonstrated the feasibility to remove our dependency to Eventlet. There is still a long way to go but the path is now well cleared. Do not hesitate to take example on the ongoing efforts, and If there are any questions or if you need assistance with your project’s transition away from Eventlet, please join the discussion on the #openstack- eventlet-removal OFTC channels . We will be happy to help you! Thank you for your dedication and hard work! -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

5 6

[NOVA] - Instances got stuck at boot with PCI passthrough mechanism enabled
by jeanpierre.roquesalane＠dell.com 24 Feb '25

24 Feb '25

Hello all! Our new env uses Zuul and nodepool for managing vms on which will be executed devstack and tempest. Those VMS are hosted on an openstack cloud with nodepool spinning them up every time a CI job is triggered. This is something very common in OpenStack end users but can be challenging for our powermax product line as it requires HBA which are seen by the host not the guest. We have followed documentation to set it up and I confirm the HBAs are visible to the instances but unfortunately once those cards are seen the instance get stuck at the boot process just like they were waiting for something. Any advice would be highly appreciated. Thank you.

1 0

Separate the read/write SQL requests
by Mia 24 Feb '25

24 Feb '25

Hi OpenStack community, I'm currently working on read/write database splitting in my OpenStack environment using this document: https://docs.openstack.org/large-scale/journey/configure/database.html#reve… Here is what I've done up to this point: - Configured HAProxy as recommended - Added the slave_connection parameter to all service configurations(nova.conf, cinder.conf, etc.) To test this, I enabled MariaDB's general_log on all nodes. However, upon checking the logs, most SELECT queries still reach the first database node instead of the other replicas. Did I miss a configuration step somewhere? Any guidance would be super helpful.

3 3

Re: CLI clients and neutron QoS packet_rate_limit rules
by Nell Jerram 24 Feb '25

24 Feb '25

FYI the attached patches, against openstacksdk 0.62.0 and python-openstackclient 5.8.1, allow me to successfully execute `openstack network qos rule create --type packet-rate-limit --max-kpps 111 --ingress bw-limiter`. (I'm using those old base versions because of testing against a Yoga system.) If I may whinge for a brief moment: it's quite tedious that boilerplate changes are needed in multiple different places for this change. I'm only really saying this in case there are others who agree and my opinion might help to build their case... Best wishes - Nell On Mon, Feb 24, 2025 at 9:46 AM Nell Jerram <nell(a)tigera.io> wrote: > Many thanks Rodolfo. I'll experiment locally with possible fixes here, > and follow up later. > > Best wishes - Nell > > > On Sat, Feb 22, 2025 at 4:22 PM Rodolfo Alonso Hernandez < > ralonsoh(a)redhat.com> wrote: > >> Hi Nell: >> >> The neutronclient project is now deprecated, at least the CLI part. As >> you mentioned, the OSC cannot create these packet rate rules. I'll create a >> bug. >> >> Regards. >> >> On Fri, Feb 21, 2025 at 7:04 PM Nell Jerram <nell(a)tigera.io> wrote: >> >>> Is it just an oversight that the openstack client doesn't support >>> packet_rate_limit rules? [1] >>> >>> Looking at the file names under [2], it looks like that might be true >>> for the neutron client as well. >>> >>> [1] >>> https://github.com/openstack/python-openstackclient/blob/master/openstackcl… >>> >>> [2] >>> https://github.com/openstack/python-neutronclient/tree/master/neutronclient… >>> >>> Best wishes - Nell >>> >>>

2 2

[neutron] Bug deputy report from week of 17th February
by Sławek Kapłoński 24 Feb '25

24 Feb '25

Hi, I was bug deputy last week. Here's summary of what new bugs do we have and their current state: ### Critical - none ### High - none ### Medium - https://bugs.launchpad.net/neutron/+bug/2098996 - empty_string_filtering extension is not enabled for ML2/OVN - fix already proposed: https://review.opendev.org/c/openstack/neutron/+/942387 - https://bugs.launchpad.net/neutron/+bug/2099450 - Incorrect ovsdb_connection validation - fix already proposed https://review.opendev.org/c/openstack/neutron/+/942412 - https://bugs.launchpad.net/neutron/+bug/2099706 - [OVN][QoS] QoS rule addition to an exiting net work policy only updates the first port - assigned to Rodolfo, patch proposed https://review.opendev.org/c/openstack/neutron/+/942516 - https://bugs.launchpad.net/neutron/+bug/2099755 - # [whitebox-neutron-tempest-plugin] ``QosTestExternalNetwork.test_dscp_bwlimit_external_network`` must check BW with VMs on different compute nodes - assigned to Rodolfo ### Low - https://bugs.launchpad.net/neutron/+bug/2098815 - # attempting to write bad value to column external_ids (ovsdb error: expected string, got <class 'NoneType'>) - assigned to Terry and already have fix proposed, - https://bugs.launchpad.net/neutron/+bug/2099798 - error when running `osken` in os_ken CLI in python 3.13 - this is osken bug impacting osken CLI tool (I didn't even know there is something like that there :)) - needs volunteer if we want to fix it, - https://bugs.launchpad.net/neutron/+bug/2099799 - `os_ken.topology.switches` cannot be stopped when observing links - yet another os-ken bug, needs volunteer ### RFE - https://bugs.launchpad.net/neutron/+bug/2098736 - [RFE] Use quota engine to replace config option "max_allowed_address_pair" - needs owner, - https://bugs.launchpad.net/neutron/+bug/2098737 - # Create a restricted default policy for undefined API calls - this needs owner but I may most likely take ownership of it, it may also require some oslo_policy changes but I am not sure about it yet, - https://bugs.launchpad.net/neutron/+bug/2099818 - ovn-sync add -reported by and already assigned to Kevin Carter, ### To triage - https://bugs.launchpad.net/neutron/+bug/2099675 - trunk subport vnic_type not inherited from parent, DHCP for baremetal ports does not work - this one deeds to be checked by someone who knows more about trunk and baremetal ports in OVN, ### Invalid (for Neutron) - https://bugs.launchpad.net/python-openstackclient/+bug/2098980 - "openstack port list -c" showing non existing columns - I moved it to be OSC bug, not the neutron one, needs assignment, should be low-hanging-fruit bug to fix -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[designate] Kubernetes External-DNS webhook provider for OpenStack Designate
by Christian Rohmann 23 Feb '25

23 Feb '25

Hello openstack-discuss, the external-dns [1] controller is the de-facto standard to integrate Kubernetes with DNS services, one of them being OpenStack Designate. 1) For quite a while there is a push to move the provider specific code out of tree, see [2], [3]. With (larger) changes not being reviewed / merged for the in-tree Designate code, [4] we bit the bullet and wrote a webhook provider implementation for OpenStack Designate, [5], which I also proposed to be added to the list of new providers via [6]. If you are running Kubernetes on top of OpenStack, I kindly ask you to give this webhook a try and see if it works or if there are still some kinks to iron out. If so: Open helpful issues, send PRs! 2) I am also reaching out to see if potentially you would even want to adopt this project as OpenStack Designate. While one could argue that it's out of OpenStack Designates element to care about Kubernetes. I believe a good integration and well working interfaces are key to keep OpenStack attractive as a platform (to run Kubernetes on). And with the webhook provider being an independent piece of software, just implementing the webhook provider interface [7], the contact surface with Kubernetes is very limited to non-existing. It's mostly Gophercloud ([8]) calling the Designate-API for the DNS record management actions external-dns requires. Looking a bit more closely to this widely used controller hitting the Designate-API might give also provide good insights or ideas for improvements or in the very least facilitates adoption. Regards Christian [1] https://github.com/kubernetes-sigs/external-dns [2] https://github.com/kubernetes-sigs/external-dns/issues/4347 [3] https://github.com/kubernetes-sigs/external-dns?tab=readme-ov-file#status-o… [4] https://github.com/kubernetes-sigs/external-dns/pull/3024 [5] https://github.com/inovex/external-dns-designate-webhook [6] https://github.com/kubernetes-sigs/external-dns/pull/5115 [7] https://kubernetes-sigs.github.io/external-dns/v0.15.1/docs/tutorials/webho… [8] https://github.com/gophercloud/gophercloud

1 0

CLI clients and neutron QoS packet_rate_limit rules
by Nell Jerram 22 Feb '25

22 Feb '25

Is it just an oversight that the openstack client doesn't support packet_rate_limit rules? [1] Looking at the file names under [2], it looks like that might be true for the neutron client as well. [1] https://github.com/openstack/python-openstackclient/blob/master/openstackcl… [2] https://github.com/openstack/python-neutronclient/tree/master/neutronclient… Best wishes - Nell

2 1

[release] Release countdown for week R-5
by Thierry Carrez 21 Feb '25

21 Feb '25

Development Focus ----------------- We are getting close to the end of the 2025.1 Epoxy cycle! Next week on February 27th, 2025 is the Epoxy-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2025.2 Flamingo cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on February 27th, 2025. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2025.1 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… February 27th, 2025 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also a good time for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Epoxy-3 milestone (feature freeze): February 27th, 2025 (R-5 week) RC1 deadline: March 14th (R-3 week) Final RC deadline: March 28th (R-1 week) Final 2025.1 Epoxy release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 -- Thierry Carrez (ttx)

1 0

[neutron] Drivers meeting canceled Friday, February 21st
by Brian Haley 21 Feb '25

21 Feb '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as I have a conflict. We can cover an RFEs added this week next Friday. Just a reminder there are still open specs that need review, list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

OVN in latest OpenStack
by Jani Heikkinen 20 Feb '25

20 Feb '25

We have been installing openstack Dalmatian based on Debian packages on our institution. I am currently trying to configure OVN neutron metadata service, but it seems very hard to find how OVN actually currently does it. See [1.]. The documentation states first, that ovn-metadata-agent will run with a netns and haproxy instance on hypervisor. But there is also a reference to having metadata support in ovn-controller. In addition, I have seen hints suggesting that neutron-ovn-agent and neutron-ovn-metadata-agent would be exclusive to each other. What is the currently up-to-date way to configure OVN metadata agent? Especially, is there any up-to-date instructions how to properly configure neutron's related config files? We have following versions of ovn and ovs: openvswitch-common 3.1.0-2 (+deb12u1) ovn-common 23.03.1-1 (~deb12u2) ovn-host 23.03.1-1 (~deb12u2) neutron-ovn-metadata-agent 2:25.0.0 (-5~bpo12+1) neutron-ovn-agent 2:25.0.0 (-5~bpo12+1) Best Regards, Jani Heikkinen [1.] https://docs.openstack.org/networking-ovn/latest/contributor/design/metadat… -- Berner Fachhochschule / Bern University of Applied Sciences IT-Services / Team Linux & Infrastructure Services Jani Heikkinen IT Linux Engineer ___________________________________________________________ Dammweg 3, CH-3013 Bern Telefon direkt +41 31 848 68 14 Telefon Servicedesk +41 31 848 48 48 jani.heikkinen(a)bfh.ch

5 10

how to clear instance actions
by Jiatong Shen 20 Feb '25

20 Feb '25

Hello Experts, During operating an old deployment, we found that instance_action as well as instance_action_event stores many records. The instance with actions are still in use. I would like to ask if there is any tool to clear instance action & events? Thank you very much for your help. -- Best Regards, Jiatong Shen

2 1

[all][elections][tc] 2025.2 cycle TC Election Campaigning Kickoff
by Ian Y. Choi 20 Feb '25

20 Feb '25

Developers, The TC Election Campaigning Period has now started [1]. Although there are no polls that need to be held [2], during the next couple days, you are all encouraged to ask the candidates questions about their platforms [3], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. TC Candidates, Each of you has posted a platform [3], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. Ian Y. Choi, on behalf of the election officials. [1] https://governance.openstack.org/election/ [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] https://opendev.org/openstack/election/src/branch/master/candidates/2025.2/…

1 0