September 2025 - openstack-discuss

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

08 Dec '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 14

[Octavia][Load Balancer][2023.1] Amphora Fails Health Check – “No Route to Host” & Timeout Errors
by Thamanna Farhath 02 Dec '25

02 Dec '25

Hi OpenStack Community, I am currently facing an issue with the Load Balancer (Octavia) service in my OpenStack deployment and would appreciate your guidance or suggestions on how to troubleshoot and resolve it. Environment Details: OpenStack Version: 2023.1 (Antelope) Operating System: Ubuntu 22.04 Octavia Backend: Amphora Network Type: VXLAN Deployment Tool: Kolla Ansible Issue Summary: After creating a Load Balancer, the Amphora instance is successfully launched. However, approximately 18 minutes later, the Load Balancer transitions to an ERROR state. Error Observed: octavia.common.exceptions.ComputeWaitTimeoutException: Waiting for compute id a222527f-8336-4fb1-8e9e-0e3ac6e8d580 to go active timeout. octavia.amphorae.driver_exceptions.exceptions.AmpConnectionRetry: Could not connect to amphora, exception caught: HTTPSConnectionPool(host='192.168.200.247', port=9443): Max retries exceeded with url: // (Caused by NewConnectionError: Failed to establish a new connection: [Errno 113] No route to host) What I’ve Tried: Created a VXLAN-based internal network: openstack subnet create --network octavia-mgmt-net --subnet-range 192.168.200.0/24 octavia-mgmt-subnet openstack router create octavia-router openstack router add subnet octavia-router octavia-mgmt-subnet openstack router set octavia-router --external-gateway <public-network-id> Manually configured OVS interface: ovs-vsctl add-port br-int octavia-mgmt -- set interface octavia-mgmt type=internal ip addr add 192.168.200.1/24 dev octavia-mgmt ip link set octavia-mgmt up Security groups are open (allowing all ingress and egress). Verified OVS bridge setup – interface appears correctly on br-int. Behavior Noticed: Amphora instance gets created but fails to communicate with the controller after a while,so health checks fails. The controller cannot reach the Amphora management IP (192.168.200.x). Logs show heartbeat/connection issues (No route to host, timeouts). Request for Help: I would appreciate any of the following: Suggestions to verify if the management network is properly routed from controller to Amphora. Best practices for setting up the Octavia management network using VXLAN. Troubleshooting steps for verifying health manager connectivity to Amphora. 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 3

LXB Removal and OVN migration
by Ricardo Cano 10 Nov '25

10 Nov '25

Hello openstack-discuss, With the removal of the linuxbridge mechanism driver, has anyone successfully completed an in-place migrationfrom LinuxBridge to OVN? I did come across this https://www.jimmdenton.com/migrating-lxb-to-ovn/ and that looks good as a one-shoit while biting the bullet and taking a full outage. However, I was wondering if it was possible to run lxb and ovn side-by-side and cut them over, say one network at a time. This particular deployment was stood up using openstack-ansible back in the rocky days (now running antelope) and it appears that openstack ansible's default was lxb up until Zed. Any suggestions or recommendations on the best path forward? Also, will the dynamic routing agent work with ovn?

4 3

[openstack helm] [Glance] Glance showing OSError: unable to receive chunked part when uploading image
by daniel890723＠gmail.com 08 Nov '25

08 Nov '25

Hello i'm testing using Openstack-helm to install all component but after the installation complete i can't upload the OS image through both openstack CLI or Horizon it stuck at Queueing and when i checking Glance Api log it shows 2024-11-07 07:31:19.362 7 INFO glance.api.v2.image_data [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token. 2024-11-07 07:31:19.400 7 ERROR glance.api.v2.image_data [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Failed to upload image data due to internal error: OSError: unable to receive chunked part 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Caught error: unable to receive chunked part: OSError: unable to receive chunked part 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi Traceback (most recent call last): 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1302, in __call__ 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi action_result = self.dispatch(self.controller, action, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1345, in dispatch 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return method(*args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 415, in wrapped 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return func(self, req, *args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/api/v2/image_data.py", line 299, in upload 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi with excutils.save_and_reraise_exception(): 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.force_reraise() 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise self.value 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/api/v2/image_data.py", line 162, in upload 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi image.set_data(data, size, backend=backend) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/notifier.py", line 492, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi with excutils.save_and_reraise_exception(): 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.force_reraise() 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise self.value 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/notifier.py", line 443, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.repo.set_data(data, size, backend=backend, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/quota/__init__.py", line 322, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.image.set_data(data, size=size, backend=backend, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/location.py", line 596, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self._upload_to_store(data, verifier, backend, size) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/location.py", line 487, in _upload_to_store 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi multihash, loc_meta) = self.store_api.add_with_multihash( 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/multi_backend.py", line 397, in add_with_multihash 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return store_add_to_backend_with_multihash( 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/multi_backend.py", line 479, in store_add_to_backend_with_multihash 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi (location, size, checksum, multihash, metadata) = store.add( 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/driver.py", line 294, in add_adapter 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi metadata_dict) = store_add_fun(*args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/capabilities.py", line 176, in op_checker 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return store_op_fun(store, *args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/_drivers/filesystem.py", line 764, in add 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise errors.get(e.errno, e) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/_drivers/filesystem.py", line 746, in add 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi for buf in utils.chunkreadable(image_file, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/common/utils.py", line 73, in chunkiter 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi chunk = fp.read(chunk_size) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 294, in read 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi result = self.data.read(i) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 121, in readfn 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi result = fd.read(*args) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/format_inspector.py", line 956, in read 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi chunk = self._source.read(size) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1045, in read 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi data = uwsgi.chunked_read() 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi OSError: unable to receive chunked part 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi Ceph Cluster Status: NAME DATADIRHOSTPATH MONCOUNT AGE PHASE MESSAGE HEALTH EXTERNAL FSID ceph /var/lib/rook 3 82m Ready Cluster created successfully HEALTH_OK 5cf8b9bb-13e1-4c31-b47d-9e7d92c3c05d Ceph osd status: ID CLASS WEIGHT REWEIGHT SIZE RAW USE DATA OMAP META AVAIL %USE VAR PGS STATUS TYPE NAME -1 0.35156 - 360 GiB 3.3 GiB 493 MiB 0 B 2.8 GiB 357 GiB 0.91 1.00 - root default -5 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 964 MiB 119 GiB 0.92 1.01 - host instance-lu-1 2 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 964 MiB 119 GiB 0.92 1.01 195 up osd.2 -3 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 - host instance-lu-2 0 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 195 up osd.0 -7 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 - host instance-lu-3 1 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 197 up osd.1 TOTAL 360 GiB 3.3 GiB 493 MiB 0 B 2.8 GiB 357 GiB 0.91 MIN/MAX VAR: 1.00/1.01 STDDEV: 0.01 now i'm able to create Empty Volume using horizon(can't create volume using default cirros image ) and i can start an Instance without volume and mount the empty volume in(Ceph also can detect when i use that volume) is there something i need to set when starting glance? because i'm following the Openstack-helm installation document to install openstack with helm

5 8

[openstack][kolla-ansible]about group node config overwrite
by Nguyễn Hữu Khôi 30 Oct '25

30 Oct '25

Hello Koller. I want to ask if we can overwrite config for a group of nodes. For example, compute01 >> compute10 will have the same nova configuration compute11 >> compute20 will have the same nova configuration. It will be very nice if we support this way. Thank you. Regards Nguyen Huu Khoi

4 7

[ptg][nova][ironic][cinder]cross-project sessions
by Iury Gregory 24 Oct '25

24 Oct '25

Hello nova and cinder folks, In the preparation for the upcoming PTG, we have some topics that we would like to discuss - *[ironic][nova] *Graphical Console follow-up https://etherpad.opendev.org/p/ironic-ptg-2026.1#L137 - *[ironic][nova][cinder] *NVMe over TCP https://etherpad.opendev.org/p/ironic-ptg-2026.1#L75 Next week we will be booking some time slots for ironic, feel free to reachout to us on #openstack-ironic with the time slots that would work for all teams. Best regards, -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic Core* *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 3

[PTG][ironic][neutron] cross-project session
by Iury Gregory 24 Oct '25

24 Oct '25

Hello neutron folks, In the preparation for the upcoming PTG, we would like to have a cross-project section to discuss about the VXLAN attachments [1] , we can book a slot that would work for the people that are interested in the topic. Next week we will be booking some time slots for ironic, feel free to reachout to us on #openstack-ironic with the time slots that would work for the neutron team. [1] https://etherpad.opendev.org/p/ironic-ptg-2026.1#L97 Best regards, -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic Core* *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 3

[openstack][octavia]Resize a Load Balancer
by Nguyễn Hữu Khôi 22 Oct '25

22 Oct '25

Hello. I see that patch https://review.opendev.org/c/openstack/octavia/+/890215 Could I ask why we cannot merge it? Nguyen Huu Khoi

3 5

[oslo][messaging] Container fix of QManager breaks it for containers
by Dmitriy Rabotyagov 22 Oct '25

22 Oct '25

Hey folks, I wanted to raise attention to a relatively old issue, which has had a patch around since January [1]. Basically a regression [2] was introduced and backported to 2024.1 as part of an attempt to fix QManager execution in containers. However, it does not account for the possibility of os.getpgrp() returning 0 in some edge cases, which makes, for instance, impossible to sync database for Nova during upgrades, if QManager is used. Thus I'm asking to kindly review the [1] as it appears to be a blocker for some upgrades involving affected versions of oslo.messaging. I have not spotted this patch right away, so I proposed an alternative [3], but I'm happy to abandon it in favor of [1]. Thanks in advance for upcoming reviews :) [1] https://review.opendev.org/c/openstack/oslo.messaging/+/939540 [2] https://review.opendev.org/c/openstack/oslo.messaging/+/928034 [3] https://review.opendev.org/c/openstack/oslo.messaging/+/958528

2 3

[Ceph Tracing] Limited Jaeger traces for OSD, no MON/MGR/RGW
by Thamanna Farhath 14 Oct '25

14 Oct '25

Hello openstack Community, I am using Ceph as the backend storage for OpenStack and deployed it via ceph-ansible.I enabled Jaeger tracing on Ceph cluster using: - Global Ceph config: ceph config set global jaeger_tracing_enable true - Jaeger Docker all-in-one docker run -d --name jaeger -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 -e COLLECTOR_OTLP_ENABLED=true --network host -p 6799:6799/udp -p 6832:6832/udp -p 5778:5778 -p 16686:16686 -p 4317:4317-p 4318:4318 -p 14250:14250 -p 14268:14268 -p 14269:14269 -p 9411:9411 jaegertracing/all-in-one:1.27 --processor.jaeger-compact.server-host-port=6799 Issue: - Only OSD traces appear with limitation traces(`enqueue_op`, `op-request-created`) - No traces from MON, MGR, or RGW Questions: 1. Is this the correct process for enabling tracing? 2. How can I capture traces for MON, MGR, RGW? 3. How can I see all OSD operations? Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

2 3

[neutron] oslo.messaging and port notifications broadcast
by Thomas Goirand 09 Oct '25

09 Oct '25

Hi, Is it possible, with oslo.messaging, to have 3 daemons to get the Neutron port.{create,update,delete}.end notification events? I tried hard, but no mater how I do it, only one of my 3 daemons get the message. I'm about to add forwarding feature to the other 2 when one receives an event. Is there a better way? Cheers, Thomas Goirand (zigo)

5 12

[ptl][venus][tc] Need a PTL volunteer for OpenStack Venus project team
by Goutham Pacha Ravi 07 Oct '25

07 Oct '25

Hello Stackers, We're missing a Project Team Lead (PTL) for the OpenStack Venus project team for the "2026.1" (Gazpacho) release cycle. If you're interested, please let us know by proposing a PTL appointment (e.g. [1]). Thanks, Goutham Pacha Ravi (gouthamr) [1] https://review.opendev.org/c/openstack/governance/+/899781

1 2

[ptl][vitrage][tc] Need a PTL volunteer for OpenStack Vitrage project team
by Goutham Pacha Ravi 07 Oct '25

07 Oct '25

Hello Stackers, We're missing a Project Team Lead (PTL) for the OpenStack Vitrage project team for the "2026.1" (Gazpacho) release cycle. If you're interested, please let us know by proposing a PTL appointment (e.g. [1]). Thanks, Goutham Pacha Ravi (gouthamr) [1] https://review.opendev.org/c/openstack/governance/+/882139

1 2

[ptl][tc] OpenStack 2025.2 Flamingo OpenInfra Live
by Allison Price 02 Oct '25

02 Oct '25

Hi everyone, As we get closer to next week’s release, I wanted to reach out about doing an OpenInfra Live episode about OpenStack 2025.2 ‘Flamingo.” If you are a PTL or TC member who would like to present project highlights, please let me know. The episode will air next Thursday, October 2 at 1400 UTC. If you are unfamiliar, you can check out the Epoxy version here: https://www.youtube.com/watch?v=qX2-8oyFVPk Cheers, Allison

5 7

East-West and the compute VM flows come to a centralized gateway for security audit
by Andy Zhou 01 Oct '25

01 Oct '25

Hello Everyone, Any advice about configure of Openstack or OVN/OVS, to implement a centralized gateway of all the flows of VMs for flow audit? Since the default type is distributed mode for the East-West flow, I want to know if we can change to a centralized one? Thank you! Best regards, Andy Zhou

2 2

I can not get user list with project in openstack version epoxy
by cheung 01 Oct '25

01 Oct '25

Dears: I can get user list with project in openstack version caracal. # openstack project list -f value 7fb2be327b4c4f9e83db04a4b5cb922b service c1bcb532eca44aadabb028b1ee715412 admin de4012f880e7408f9fb21b67930c21ac project_it # openstack user list -f value 84b39214b13148d68bf88242aa6abdf9 admin 62f7113645c24199a9946cd16911ca64 glance b21da7173fe3400f91d3eb73f392474d nova 95a6ff7b9bba42f9aadf3b07a0811330 placement 4ac268a8e75b4a4288f067e28ad14425 neutron 46fa578d54624e06ae2e0b3761a67de7 cinder 1c1646579b5042a6bb463e8f46b7762f test001 57689f8310e744889dce33d6b32f4524 test002 # openstack user list -f value --project project_it 1c1646579b5042a6bb463e8f46b7762f test001 57689f8310e744889dce33d6b32f4524 test002 # openstack user list -f value --project service 4ac268a8e75b4a4288f067e28ad14425 neutron 46fa578d54624e06ae2e0b3761a67de7 cinder b21da7173fe3400f91d3eb73f392474d nova 62f7113645c24199a9946cd16911ca64 glance 95a6ff7b9bba42f9aadf3b07a0811330 placement # dpkg -l| grep keyston ii keystone 2:25.0.0-0ubuntu1 all OpenStack identity service - Daemons ii keystone-common 2:25.0.0-0ubuntu1 all OpenStack identity service - Common files ii python3-keystone 2:25.0.0-0ubuntu1 all OpenStack identity service - Python 3 library ii python3-keystoneauth1 5.6.0-0ubuntu1.1 all authentication library for OpenStack Identity - Python 3.x ii python3-keystoneclient 1:5.4.0-0ubuntu1 all client library for the OpenStack Keystone API - Python 3.x ii python3-keystonemiddleware 10.6.0-0ubuntu1 all Middleware for OpenStack Identity (Keystone) - Python 3.x But I can not get user list in epoxy version. # openstack project list -f value 0087125cb3564da39a5e87dc61aece78 project_it 8b6a848d2d7841118567f1dad2eeb9f5 admin dcaa69462fd3447ca75133a8ce4b95c3 service # openstack user list -f value 27bd419eb7bc4da58f9e246232a12720 placement 7c5a457f461440e5a24a368f827ecafc admin 846cca4cb4394d1ab4e8d95dffb63ce2 glance 92122f012abb4db38a0d3ca287c04122 nova ad039b4d1f4f4c42a59e69e56eef4f16 neutron ebde13fec7584f5180becb88afa0e1c7 cinder f4cf0b16f52e407d994e2aa729936580 test002 f9ee38a0a4cb412dbd293a83b5b32dc5 test001 # openstack user list -f value --project project_it Either group or user should be specified # openstack user list -f value --project service Either group or user should be specified What do I miss? I need to read which one document? 本電子郵件及其所有附件所含之資訊均屬機密，僅供指定之收件人使用，未經寄件人同意不得揭露、複製或散布本電子郵件。若您並非指定之收件人，請勿使用、保存或揭露本電子郵件之任何部分，並請立即通知寄件人並完全刪除本電子郵件。網路通訊可能含有病毒，收件人應自行確認本郵件是否安全，若因此造成損害，寄件人恕不負責。 The information contained in this communication and attachment is confidential and is intended only for the use of the recipient to which this communication is addressed. Any disclosure, copying or distribution of this communication without the sender's consents is strictly prohibited. If you are not the intended recipient, please notify the sender and delete this communication entirely without using, retaining, or disclosing any of its contents. Internet communications cannot be guaranteed to be virus-free. The recipient is responsible for ensuring that this communication is virus free and the sender accepts no liability for any damages caused by virus transmitted by this communication.

3 4

Using slave_connection in keystone for a read-only local database node
by Tyler Wilson 30 Sep '25

30 Sep '25

Hello All, I'm trying to get keystone to respect my slave_connection configuration to use a local database node in my galera cluster. I have this set currently; connection = mysql+pymysql://keystone:$PASSWORD@$DB_PRIMARY_WRITE_IP/keystone slave_connection = mysql+pymysql://keystone:$PASSWORD@$DB_LOCAL_READ_IP/keystone However whenever I have this configured I still am getting queries sent to the $DB_PRIMARY_WRITE_IP for even simple things like 'openstack user list'. Is there some other configuration I need to set for this to go to the read DB node? I have query logging enabled on the mariadb side to confirm where the requests are going. For troubleshooting I changed them both to the local DB node IP, and it can indeed process the sql requests fine. Operating System: Ubuntu 24.04 Package Version: 2:25.0.0-0ubuntu1 Thanks for any assistance!

2 1

Debian packages for Flamingo are available and validated
by Thomas Goirand 30 Sep '25

30 Sep '25

Hi, I am finished packaging Flamingo, at least for all artifacts that were released already. I was able to run tempest on it, and all went well. I uploaded all to Debian Unstable already minor a few packages (like Ironic, that is having issues coping with pysnmp 7, and mistral that is stuck on one of its unit tests: I'll investigate both soon). Packages are available through the usual channel. To get the osbpo.debian.net backport repository for Trixie, do: apt-get install extrepo extrep enable openstack_flamingo apt-get update Note that osbpo is now updated automatically on all git push based on event, rather than a cron job, so it's kind of instant now. So there's no reason to use the http://<debian-suite>-<openstack-release.debian.net repositories anymore (these are now only useful for me, internally, to build backport packages with Jenkins). Also, the deb-status page is also event driven, and updated each time a new package is updated. Please see: https://osbpo.debian.net/deb-status/ In there, you will see that I also took the time to update all past OpenStack release to the latest point release for all deliverables. Please report bugs through the usual channel: https://www.debian.org/Bugs/Reporting I'll package final versions as they come, though changes are expected to be minimal (if any change at all), as for every OpenStack release. Cheers, Thomas Goirand (zigo)

1 0

[openstack] about libvirt exporter
by Nguyễn Hữu Khôi 30 Sep '25

30 Sep '25

Hello. I see that this exporter looks like it collects a lot of information such as projectname, username or flavor of metrics but it looks not popular. It could help us build a very useful dashboard. https://github.com/zhangjianweibj/prometheus-libvirt-exporter I just want to understand some thoughts. Nguyen Huu Khoi

3 3

how to spare resource for evacuation
by Jiatong Shen 30 Sep '25

30 Sep '25

Hello experts, I would like to ask if there is a way to reserve some resources (CPU and Memory) in advance and later use them in case one compute node crashes. For example, vSphere implemetens Cluster Resources Percentage Admission Control [1] and could reserve resources beforehand. Thank you very much for the help. -- Best Regards, Jiatong Shen [1] https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/vsphere-…

2 2

[i18n] Current Weblate Migration Status
by Seongsoo Cho 30 Sep '25

30 Sep '25

Hello i18n team, OpenStack's current translation platform(translation.openstack.org) is based on Zanata, which is no longer maintained. To ensure a sustainable translation workflow, the i18n team has been migrating from Zanata to Weblate. This work officially started following the CMU Summer semester mentoring shared by Kendall Nelson in May (link), and has since been moving forward in collaboration with the Korea User Group and mentees participating in the government-sponsored Open Source Contribution Academy program. 1. Migration progress Migration scope: - Download translated .po files from Zanata and upload them to Weblate - The same language set configured in Zanata is also applied in Weblate. Branches: - Currently, only the master branch is being migrated. - We are exploring ways to support stable branches in the future. Migration Contents: - At this stage, the migration targets strings inside source code and release notes. - We are in the process of expanding this to include documentation as well. We started with Horizon and its plugins, and the following projects have already been successfully migrated to Weblate: • cloudkitty-dashboard • designate-dashboard • freezer-web-ui • heat-dashboard • horizon • ironic-ui • magnum-ui • manila-ui • networking-bgpvpn • neutron-fwaas-dashboard • neutron-vpnaas-dashboard • octavia-dashboard • trove-dashboard • zaqar-ui • zun-ui 2. New Zuul jobs for Weblate To replicate the existing Zanata-based Zuul workflow, we are adding new Weblate jobs. • Patch: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/921878 We plan to reuse the translation-jobs-master-only Zuul templates and update the following playbooks to run both Zanata and Weblate tasks: • https://opendev.org/openstack/project-config/src/branch/master/playbooks/tr… • https://opendev.org/openstack/project-config/src/branch/master/playbooks/tr… • Patch: https://review.opendev.org/c/openstack/project-config/+/961499 3. Migration scripts Although they are one-off scripts, we are adding them to the i18n repository to document how we migrated from Zanata to Weblate. • Language sync tool: https://review.opendev.org/c/openstack/i18n/+/961371 • Zanata-to-Weblate migration tool: https://review.opendev.org/c/openstack/i18n/+/961075 4. Next steps for migration We have implemented everything needed to replace the Zanata-based jobs with Weblate. Once the Zuul job patches are merged, we will verify the upstream pipeline. Our goal is to migrate all projects from Zanata to Weblate by October. After verifying the pipeline, we plan to shut down Zanata. 5. Future plans Beyond this migration, we plan to expand translation targets — including OpenStack governance documents and the docs/ directories of many projects — to provide broader translation opportunities. Anyone interested in contributing is warmly welcome to join us in the #openstack-i18n IRC channel and say hello! Thanks, Best Regards Seongsoo Cho -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

3 4

[nova][cpu] Question about cpu_policy=dedicated with thread_policy=isolate in Victoria
by Aleksandar Cerepnalkovski 30 Sep '25

30 Sep '25

Hi all, What I'm trying to do is isolate vCPUs on separate physical cores where pair siblings will be reserved / not used by any other VM nor by this VM as well. Of course it is about SMT/HT enabled hosts. So by using a combination of extra spec on flavor (cpu_policy=dedicated , plus thread_policy=isolate), i'm always receiving errors ( no host available) . I'm using the Victoria OpenStack release. I've found (also playing with AI tools) that this combination is tricky (buggy) in Victoria and might not work and it might always fail. Actually what this combination is introduced for ? 1. If is it for what i meant ( forcing SMT enabled host to behave like non-SMT host, for some number of cores not all) then why is it not working ? 2. If not, what is the purpose of this combination ? Thanks, BR Aleksandar

1 0

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

30 Sep '25

Hello Stackers, It's release week [1]! We've pulled out a lot of stops to get the 32nd release of OpenStack packed with exciting improvements [2]. Project teams have released their final RCs for all deliverables following the cycle-with-rc release model in preparation for the coordinated release on October 1st, 2025. Work has begun on the 2026.1 "Gazpacho" release [3]. This next one is a SLURP release—alongside major feature work, the community is actively prioritizing paying down technical debt, most of which has been identified as Community Goals [4]. In the next few weeks, cycle-trailing projects will work on supporting the 2025.2 "Flamingo" release. They will join the rest of the community in a week of design discussions at the OpenInfra Project Teams Gathering, scheduled for October 27–31st, 2025. If you're looking to seed or participate in a discussion here, please add your topics to the many discussion Etherpads that have been created for the event [5]. In the past week, the OpenStack Technical Committee was re-formed with three returning (frickler, bauzas, and cardoe) and one new member (tonyb). We're looking to fill roles such as TC chair, vice-chair, and liaisons to various project teams, including the OpenStack VMT, this week. The retirement of the "shade" client library was approved; functionality provided by this library has long been available as a part of openstacksdk. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee occurred on September 23rd, 2025 [6]. The meeting began by acknowledging the recently concluded TC elections, congratulating the elected members, and thanking the election officials for their work. We discussed the status of "leaderless" projects—Venus, Vitrage, and OpenStack Charms. For OpenStack Charms, Felipe Reyes (freyes) submitted a patch to appoint himself as PTL. For Venus and Vitrage, the committee decided to gather more data for a thorough discussion next week. The group noted low activity for Venus and maintenance activity for Vitrage, though its core-team list is significantly outdated and requires cleanup. The discussion also touched on the completed action item of vendoring the ply library into yaql, which sparked a lengthy debate on the implications for downstream package maintainers and distributions, with the consensus being to keep the change but acknowledge the concerns. The meeting wrapped up with a brief note on the broken CI for the Skyline project and attempts to contact the core maintainers whose time has been stretched thin. The next meeting of the OpenStack TC is today, September 30th, 2025. The meeting will be hosted on OFTC's #openstack-tc channel. Please find the meeting's agenda and other details on the wiki page [7]. I hope you'll be able to join us there! I'd like to note that any community member is welcome to edit this wiki page at any time to seed a new topic of discussion. === Governance Proposals === ==== Merged ==== - Add gouthamr's nomination for 2026.1 TC chair | https://review.opendev.org/c/openstack/governance/+/962049 - Fix small mistake with month in subject resolution | https://review.opendev.org/c/openstack/governance/+/962512 - Retire shade | https://review.opendev.org/c/openstack/governance/+/962197 - Add TC/PTL results from 2026.1 election | https://review.opendev.org/c/openstack/governance/+/961598 ==== Open For Review ==== - Appoint Felipe Reyes as PTL for OpenStack Charms | https://review.opendev.org/c/openstack/governance/+/962121 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Extend Monasca's inactive state | https://review.opendev.org/c/openstack/governance/+/959392 - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-10-01: OpenStack 2026.1 "Flamingo" release day - 2025-10-03: OpenStack's Birthday Meetup, Austin: https://www.meetup.com/openinfra-austin/events/310508680 - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ - 2025-10-04: OpenInfra Board meeting: https://board.openinfra.org/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] 2025.2 "Flamingo" Release highlights: https://releases.openstack.org/flamingo/highlights.html [3] 2026.1 "Gazpacho" Release Schedule: https://releases.openstack.org/gazpacho/schedule.html [4] OpenStack-wide Goals: https://governance.openstack.org/tc/goals/selected/index.html [5] Gazpacho PTG Etherpads: https://ptg.opendev.org/etherpads.html [6] TC Meeting IRC Log, Sep 23rd, 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-23-17.00.html [7] TC Meeting Agenda, Sep 30th, 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[ironic] Cancelling October 13th, 20th, 27th meetings.
by Julia Kreger 29 Sep '25

29 Sep '25

Greetings everyone, We're at the end of the release cycle and we will soon have a summit[0] *and* the PTG later in October. As such, the Ironic team discussed upcoming meetings during our weekly meeting[1] and reached the consensus to cancel the meetings for October 13th, 20th, and 27th. The 13th and 20th for proximity to Open Infra Summit, and the 27th because of the PTG[2] during which the team will likely be meeting the entire week. If you have any questions, please let us know! -Julia, on behalf of the Ironic project. [0] :https://summit2025.openinfra.org/ [1]: https://meetings.opendev.org/meetings/ironic/2025/ironic.2025-09-29-15.03.l… [2]: https://etherpad.opendev.org/p/ironic-ptg-2026.1

1 0

Need information on services
by engineer2024 29 Sep '25

29 Sep '25

Hi, Are there any existing projects in OpenStack equivalent to lambda in aws, which provides function-as-a service model ?

2 2