- openstack-discuss - lists.openstack.org

[horizon] Help review the patch https://review.opendev.org/c/openstack/horizon/+/961099
by Dong Ma 14 Oct '25

14 Oct '25

Hi, We’ve submitted a patch (https://review.opendev.org/c/openstack/horizon/+/961099) adding microversion support for Nova live migration. Appreciate any reviews from the core team so we can get it merged soon. Thanks, -- Dong Ma — vexxhost

1 0

How to set admin password during server create but not using user-data file
by Ahmad Milad Pour 14 Oct '25

14 Oct '25

Hello there, This is how I download an ubuntu cloud image: wget -c https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.i… -O ~/noble-server-cloudimg-amd64.img virt-customize -a noble-server-cloudimg-amd64.img \ --timezone Asia/Tehran \ --root-password password:q \ --run-command 'sed -i "s/^disable_root.*/disable_root: false/" /etc/cloud/cloud.cfg' \ --run-command 'grep -q "^ssh_pwauth:" /etc/cloud/cloud.cfg && sed -i "s/^ssh_pwauth:.*/ssh_pwauth: true/" /etc/cloud/cloud.cfg || echo "ssh_pwauth: true" >> /etc/cloud/cloud.cfg' \ --run-command 'printf "PasswordAuthentication yes\nPermitRootLogin yes\n" > /etc/ssh/sshd_config.d/99-allow-root.conf' \ --run-command "sed -e 's/^[# ]*PasswordAuthentication.*/PasswordAuthentication yes/g' -i /etc/ssh/sshd_config || true" \ --run-command "sed -e 's/^[# ]*PermitRootLogin.*/PermitRootLogin yes/g' -i /etc/ssh/sshd_config || true" \ --run-command 'systemctl enable ssh || systemctl enable sshd' \ --run-command 'systemctl disable systemd-networkd-wait-online.service' openstack image create --file ~/noble-server-cloudimg-amd64.img --disk-format qcow2 --container-format bare --public --property os_distro=ubuntu --property hw_qemu_guest_agent=yes "Ubuntu 24" || true rm -f noble-server-cloudimg-amd64.img cat <<EOF > /root/userdata.txt #cloud-config chpasswd: list: | root:q expire: False ssh_pwauth: True cmd: - systemctl disable systemd-networkd-wait-online.service EOF openstack server create --image "Ubuntu 24" --flavor first --network public_network --config-drive True ahmad --password 'ahmad' This is how I create image. I'm going to find a way if possible, to set the admin password during the "server create". Currently the root login is only possible with password "q". The "ahmad" is not working. I know I can change it via user-data file (I intentionally added there but not using it), but the question is can I set the password during the server create? I tried to use "virt-customize --install qemu-guest-agent", but the virt-customize has no network, so no installation. I also know I can do this: 1. create server 2. do whatever I want (install guest agent, etc) 3. create snapshot 4. create server from that snapshot But the issue is it's not automatic (I should manually login to do the modification) and its size is much more than the cloud image. Like, from 500 megabytes which is cloud image, goes around 3 gigabytes which is the snapshot. Any ways to reach what I'm looking for? Or even any better ways to do that? Regards, Ahmad

1 0

[ovn][wallaby][migration] Live migration more than 10s switchover
by Kamil Madac 14 Oct '25

14 Oct '25

Hello community, We are running a Wallaby TripleO installation with OVN networking. During live migration, we’re experiencing a connectivity outage lasting between *10 and 40 seconds* on the provider network to which the migrating VM is connected. I don’t see any errors in the ovn-controller, nova, or neutron logs. Is this behavior normal for the Wallaby release? We don’t see this issue in our Kolla-Ansible deployment running OpenStack 2024.2. I found that OVN multi-chassis port bindings were not yet implemented in Wallaby, but still — more than 10 seconds of downtime during live migration seems excessive. Has anyone observed similar behavior with older OpenStack releases, or is there any way to tune or optimize the switchover to reduce the outage duration? Thanks for any advice. Best regards, Kamil

1 0

[horizon] Help review the patch https://review.opendev.org/c/openstack/horizon/+/961099
by Dong Ma 13 Oct '25

13 Oct '25

Hi, We’ve submitted a patch (https://review.opendev.org/c/openstack/horizon/+/961099) adding microversion support for Nova live migration. Appreciate any reviews from the core team so we can get it merged soon. Thanks, -- Dong Ma — vexxhost

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2026.1/R-24)
by Goutham Pacha Ravi 13 Oct '25

13 Oct '25

Hello Stackers, We're twenty-four weeks away from the coordinated release of OpenStack 2026.1 "Gazpacho" [1]. In a couple of weeks, the community will be gathering to design and discuss features and bug fixes for this release [2]. PTLs and project liaisons are requested to finalize their project schedules for the PTG and strive to use the first two days solely for wider cross-project discussions. At the end of this week, a portion of our community will be participating in the OpenInfra Summit happening at the École Polytechnique Campus in Paris-Saclay, France [3]. There's a meet-and-greet session planned with the OpenStack Technical Committee on Sunday, October 19th starting at 17:05 UTC in the Becquerel room. If you're attending the summit, do try to add this to your calendar. During the past week, the TC didn't make any major governance updates. A few are currently undergoing community review. === Weekly Meeting === The last weekly meeting of the OpenStack TC occurred on October 7th, 2025 simultaneously over IRC [4] and video [5]. We had a small list of attendees and a short agenda. We noted that the governance changes to officially mark Venus and Vitrage as inactive are in progress. The retirement of Monasca is still held up, and the team is waiting for a response from a potential new maintainer. Discussions were held on the new APAC-friendly TC meeting slot, with the plan to review the poll results and schedule the first meeting shortly after the OpenStack Summit, likely on a monthly or bi-weekly cadence. I'll follow up with more details about this. We also discussed the need to refresh the TC Liaisons for several project teams (Freezer, Oslo, Release Management, and Requirements) and are seeking volunteers on the TC. We called for topics for the PTG. The TC will join project teams in analyzing the User Survey results [6]. The next meeting of the OpenStack Technical Committee will be hosted on OFTC's #openstack-tc channel on October 14th, 2025 at 1700 UTC. Please find the agenda for this meeting on the wiki [7]. I hope you're able to join us there. === Governance Proposals === ==== Merged ==== - Allow .gitignore in legacy repositories | https://review.opendev.org/c/openstack/governance/+/963867 - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 ==== Open For Review ==== - Mark Vitrage project-team inactive | https://review.opendev.org/c/openstack/governance/+/963227 - Mark Venus project-team inactive | https://review.opendev.org/c/openstack/governance/+/963228 - Retire ironic-inspector from bare metal program | https://review.opendev.org/c/openstack/governance/+/963470 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-22: OpenInfra Meetup, Jakarta Selatan: https://www.meetup.com/openinfraid/events/31140538 - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ - 2025-11-04: OpenInfra Board meeting: https://board.openinfra.org/ - 2025-11-15: Celebrating 15 years of OpenStack, Montréal - 2025-11-15: KCD+OpenInfra Days, Hangzhou: https://sessionize.com/kcd-hangzhou-and-oicd-2025/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) [1] 2026.1 "Gazpacho" Release Schedule: https://releases.openstack.org/gazpacho/schedule.html [2] OpenInfra Project Teams Gathering: https://ptg.openinfra.org/ [3] OpenInfra Summit: https://summit2025.openinfra.org/ [4] TC Meeting IRC Log, Oct 7th 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-10-07-17.01.html [5] TC Meeting Video Recording, Oct 7th 2025: https://youtu.be/s_j3LPg-f1M [6] OpenStack User Survey: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [7] TC Meeting Agenda, Oct 14th 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[glance] image upload fails "Unsupported Media Type", "Multiple formats detected: iso,gpt"
by Eugen Block 13 Oct '25

13 Oct '25

Good morning, after our recent upgrade to Epoxy we had troubles uploading images to Glance: openstack image create --disk-format raw --file .../opensuse/Leap-16.0-offline-installer-x86_64.install.iso --progress --public test-ebl [=============================>] 100% HttpException: 415: Client Error for url: http://controller.domain:9292/v2/images/e23d802e-d927-4f34-ae2d-1d6f54d6206…, Unsupported Media Type And in the logs this is reported: 2025-10-11 01:16:56.585 65675 ERROR glance.api.v2.image_data [None req-086ad005-a455-471a-bb0d-9dfe5e27eacf 89c5dcc8793d4867bae22d50e51e16b3 90c403f317ee47feb0dad58461e76fb1 - - default default] Multiple formats detected: iso,gpt: glance.common.exception.InvalidImageData: Multiple formats detected: iso,gpt This is the official openSUSE Leap 16 ISO file. For now I disabled the check by setting: [image_format] require_image_format_match = false The docs state that this is likely a bug: > Disabling this may be required in the case of false match (or > mismatch) issues, but those are bugs that should be filed and fixed. I tried a couple of different ISO files (Ubuntu, openSUSE, incl. older files), all fail with the same error. Uploading raw images seemed to work fine. ISOs are supported file formats according to the docs, could anyone shed some light on this? Thanks! Eugen

2 6

[neutron] Bug deputy Oct 6 - Oct 12
by Rodolfo Alonso Hernandez 13 Oct '25

13 Oct '25

Hello Neutrinos: This is the bug report from the last week (Oct 6 - Oct 12) High: * [VPNAAS] vpnaas AttributeError: 'dict' object has no attribute 'router' ( https://bugs.launchpad.net/neutron/+bug/2127169) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963493 * [VPNAAS] vpnaas no config update in ipsec.conf ( https://bugs.launchpad.net/neutron/+bug/2127166) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963490 * [VPNAAS] Libreswan config broken when used with new AEAD ciphers ( https://bugs.launchpad.net/neutron/+bug/2127159) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963489 * [VPNAAS] ovn-vpn-agent fails to delete vpn service ( https://bugs.launchpad.net/neutron/+bug/2127157) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963487 * OVN CI jobs on ironic are broken ( https://bugs.launchpad.net/neutron/+bug/2127038) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron/+/963390 (fixed). Medium: * ovn_dhcp4_global_options doesn't support keys with a list of values ( https://bugs.launchpad.net/neutron/+bug/2126923) Not assigned. Undecided: * Neutron not able to create external ports for virtual routers ( https://bugs.launchpad.net/neutron/+bug/2126913) Still deciding if this is a configuration issue. Regards.

1 0

Unable to create new instance while the computes are up
by Ahmad Milad Pour 13 Oct '25

13 Oct '25

Hello there, I asked the ChatGPT to help me to install the openstack on region, and to run a compute server. The ".sh" files are the installation. The "common_ask.sh" file is I run on both servers. The "region_ask.sh" is the file to install openstack and the region. The "compute_ask.sh" is the file to run the compute. The logs and errors are in the "region_details.txt" file. Would you please help me why the server I create has error and cannot be up? The way to create new instance is in the last lines of the "region_ask.sh" which is "openstack server create ...". Regards Ahmad

4 3

[tacker] Cancelling weekly IRC meeting
by Yasufumi Ogawa 12 Oct '25

12 Oct '25

Hi team, Due to a holiday and most of the core members aren't join, I'm cancelling tomorrow's meeting. Regards, Yasufumi

1 0

[OpenStack Ansible] [Deployment] Networking design
by holywine＠outlook.com 12 Oct '25

12 Oct '25

Hello, I am trying to build a minimum usable production-level cloud with OpenStack Ansible following online reference. The idea it shoud be able to scale up without radical change afterwards. Online reference: https://docs.openstack.org/project-deploy-guide/openstack-ansible/2025.1/ openstack-ansible version: stable/2025.1 Target hosts (Ubuntu 24.04LTS): 1) Infra1: Controller 1 + networking 2) Infra2: Controller 2 3) Compute 1: Compute 1 + storage 1 4) Compute 2: Compute 2 + storage 2 Deploy host: dev-host (Ubuntu 24.04LTS) Network: Each sever has two network adapter, say enp11s0f0 and enp11s0f1 (different server may have different port name, en0 and en1 for short). Public IP (en1) : Infra1 - 10.2.46.70/24, fixed IP permanently assigned by provider. Infra2, Compute 1, Compute 2 - 10.2.46.XX/24, dynamic IP temporary assigned for SW installation Private IP (en0): Infra1: 172.29.236.11/22, VLAN 10 172.29.240.11/22, VLAN 30 Infra2: 172.29.236.12/22, VLAN 10 172.29.240.12/22, VLAN 30 Compute 1: 172.29.236.13/22, VLAN 10 172.29.240.13/22, VLAN 30 172.29.244.13/22, VLAN 20 Compute 2: 172.29.236.14/22, VLAN 10 172.29.240.14/22, VLAN 30 172.29.244.14/22, VLAN 20 VLAN 10 - management network VLAN 30 - tunnel network VLAN 20 - storage network Target: Since only Infra1:en1 is available with fixed public IP, It would be the only Internet connection without any port bonding. What have been done: 1) All ordinary IPs and VLANs setting (as above Network part) - The settings are verified and working (verified by ping and curl) 2) user_variables.yml haproxy_keepalived_external_vip_cidr: "10.2.46.70/24" haproxy_keepalived_internal_vip_cidr: "172.29.236.11/22" haproxy_keepalived_external_interface: enp11s0f1 haproxy_keepalived_internal_interface: br-mgmt 3) openstack_user_config.yml internal_lb_vip_address: 172.29.236.11 external_lb_vip_address: 10.2.46.70 Based on experiences as network engineer previously and a lot of readings from books and online guidance esp. the OpenStack Ansible deployment reference, I understand there should/could be something extra to be done. Can anybody please give me a clue on what else to be done or it is enough to make it working? Sorry for disturbing if any but netwoking seems to be the most complicated part for OpenStack deployment. The online examples are hard to be comprehend and customized. One small example: Ubuntu seems to be promoting netplan, while the examples are all with /etc/network/interfaces file (difficult to adapte with Ubuntu24.04). Thanks a lot for help in advance!

2 4

[release] Release countdown for week R-24
by Thierry Carrez 10 Oct '25

10 Oct '25

Welcome back to the release countdown emails! These will be sent at major points in the 2026.1 "Gazpacho" development cycle, which should conclude with a final release on April 1st, 2026 (not a joke). Development Focus ----------------- At this stage in the release cycle, focus should be on planning the 2026.1 "Gazpacho" development cycle, assessing Gazpacho community goals and approving Gazpacho specs. General Information ------------------- The 2026.1 "Gazpacho" development cycle will be a classic 26-week-long cycle. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/gazpacho/schedule.html By default, the team PTL is responsible for handling the release cycle and approving release requests. This task can (and probably should) be delegated to release liaisons. Now is a good time to review release liaison information for your team and make sure it is up to date: https://opendev.org/openstack/releases/src/branch/master/data/release_liais… By default, all your team deliverables from the 2025.2 "Flamingo" release are continued in 2026.1 "Gazpacho" with a similar release model. Upcoming Deadlines & Dates -------------------------- OpenInfra Summit Europe: October 17th-19th, 2025 OpenStack PTG (virtual): October 27th-31st, 2025 Gazpacho-1 milestone: November 13th, 2025 -- Thierry Carrez (ttx)

1 0

[neutron] Drivers meeting canceled Friday, October 10th
by Brian Haley 09 Oct '25

09 Oct '25

Hello Neutrinos: I am going to cancel tomorrow's Drivers meeting as there are no topics and I will be out. At this point we should probably just add things to the PTG etherpad and discuss there [0]. Just a reminder there are still open specs that need updates and/or review, list is at [1]. Have a nice weekend! -Brian [0] https://etherpad.opendev.org/p/oct2025-ptg-neutron [1] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

[PTLs] [OpenStack TC] Anonymized User Survey Feedback
by Jimmy McArthur 09 Oct '25

09 Oct '25

As you know each year we conduct an OpenStack User Survey. A big chunk of that survey data is dedicated to OpenStack projects, WGs, etc… I’d like to invite you all to review the anonymized feedback from 2025[1]. Please review not only for feedback, but to determine if you want to update your TC, PTL or WG questions. Additionally, if the TC can ensure that questions are up to date wrt to project or working group status. For example, we know the InteropWG has been disbanded as of this year, so we should probably remove those questions for 2026. We would like to have ALL reviews/requests in no later than December 1, 2025. If we do not hear from your project, we will assume you want no changes. If you have any questions, please let myself or Allison Price know. Cheers, Jimmy [1] https://docs.google.com/spreadsheets/d/1bte_k0R3_rVzFF9ND5zTZV0j9liXI1PxPNo…

2 2

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

08 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][release][stable] 2024.1 Caracal transition to Unmaintained
by Elõd Illés 08 Oct '25

08 Oct '25

Hi teams, As 2025.2 Flamingo was released last week and we are in a less busy period, now is the good time to call your attention to the following: At the end of October 2024.1 Caracal is planned to transition to Unmaintained phase [1] (planned date: 2025-10-24). I have generated the list of the current *open* and *unreleased* changes in stable/2024.1 for every repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Caracal before moving stable/2024.1 branches to unmaintained/2024.1. Feel free to edit and extend these lists to track your team's progress! Note that the last hash on stable/2024.1 branch will be tagged ('2024.1-eom' tag) and transition patches will be generated soon. After the tagging and cutting unmaintained/2024.1 branch, the new unmaintained branch will be open to for bug fixes, but there won't be official releases for 2024.1 Caracal anymore. (You can get some information about the Unmaintained state on stable policy page [3]). *NOTE*: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken (final!!) releases! [1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/2024.1-caracal-final-release-before-eom [3] https://docs.openstack.org/project-team-guide/stable-branches.html#unmainta… Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0

[kolla] Next two weekly meetings - 8th Oct and 15th Oct
by Michał Nasiadka 07 Oct '25

07 Oct '25

Hello, The next two weekly meetings for Kolla are cancelled: 8th Oct (today) - due to unavailability of key participants 15th Oct (next week) - due to OpenInfra Summit

1 0

[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

[kolla][kolla-ansible] Managing Object Storage Backend via Kolla-Ansible
by Sara khosravi 07 Oct '25

07 Oct '25

Hello everyone, We are currently using Kolla-Ansible stable/2024.1 to manage our OpenStack deployment, including both core services and the Swift object storage backend. Our goal is to manage all OpenStack services, including object storage, through a unified lifecycle management tool. We understand that managing large volumes of data can affect the performance of other services. To address this, we've separated the data flow entry points that could become bottlenecks into dedicated host groups: a load balancer and a Swift proxy. Specifically, we've created two separate host groups: one for the secondary load balancer (which serves as the initial entry point) and another for the Swift proxy services. 🔹 Key Point 1: Decoupling Swift Traffic We’ve separated the Swift proxy nodes from the other OpenStack API services. This also means that the load balancer handling Swift traffic must be distinct from the main load balancer used for services like Nova, Glance, and Neutron. 🔹 Key Point 2: Keystone Endpoint Behavior Swift still registers with the existing Keystone service. Depending on the configuration: - If the second_loadbalancer is enabled, Keystone publishes the VIP (Virtual IP) of the secondary HAProxy as the Swift endpoint. - If it’s disabled, Keystone uses the direct API address of the Swift proxy node. 🔹 Key Point 3: Two Supported Configurations Kolla-Ansible supports two architecture models for Swift: Normal and Advanced. - Normal Configuration This is the default setup in stable/2024.1, where all OpenStack services, including Swift, share the same load balancer and traffic path. - Advanced Configuration This is recommended for large-scale deployments with heavy data volumes. In this setup, Swift traffic goes through a dedicated load balancer and proxy nodes, which reduces contention and improves performance. We’ve attached an architectural diagram to better illustrate the setup. We’d love to share this approach with the community and welcome any feedback or suggestions. Our goal is to make managing both compute and storage services within a single deployment framework as simple as possible. Thanks in advance for your insights!

3 3

[nova] limiting number of attached devices
by Pavlo Shchelokovskyy 07 Oct '25

07 Oct '25

Hi all, we've recently faced a peculiar issue with one of the users, namely: - fat VM with 100 cores - virtio-net multiqueue set up for the VM (`hw:vif_multiqueue_enabled`) - quite a number of NICs attached. On an attempt to attach yet another NIC (~20th), instance crashes with specific error message in the qemu log ``` qemu-system-x86_64: ../../accel/kvm/kvm-all.c:1754: kvm_irqchip_commit_routes: Assertion `ret == 0' failed. ``` After debugging, we believe that what's happening is we are hitting an intrinsic limit of IRQs in a KVM guest ( `KVM_MAX_IRQ_ROUTES 4096` here https://github.com/torvalds/linux/blob/master/include/linux/kvm_host.h#L2175 ). With multiqueue and this number of vCPUs, each new NIC adds ~200 interrupts in the guest, so with some other system ones and some more devices already present, at some point, adding one more NIC overflows this current limit. In this particular case, the problem is exaggerated by the fact that what's requesting the new NIC attachment is some sort of CNI-like automation inside the guest, reacting on some external events (like another k8s node going down and pods being migrated). This got me thinking - should nova be able to somehow hard-limit the number of attached devices to a VM? I do not think nova should be "counting the IRQs" per se, as there are things outside that nova does not necessarily know (like what and how many actual devices a given qemu machine type creates inside the guest). But having some knob on a user side, for example a special metadata set on the instance, or at least an extra spec property for the flavor, could possibly suffice in this case. I'm eager to hear your thoughts on this, please chime in with any ideas on how to prevent such self-destructing instances :-) Best regards, -- Dr. Pavlo Shchelokovskyy Principal Software Engineer Mirantis Inc www.mirantis.com

1 0

[kolla][kolla-ansible] Managing Object Storage Backend via Kolla-Ansible
by Sara khosravi 07 Oct '25

07 Oct '25

Hello everyone, We’re currently using Kolla-Ansible stable/2024.1 to manage our OpenStack deployment, including both core services and the Swift object storage backend. aiming to manage both core OpenStack services and the object storage service through a unified lifecycle management tool. We understand that handling large volumes of data can impact the performance of other services. To mitigate this, we've separated the data path entry points that could become bottlenecks into dedicated and distinct host groups—load balancer and Swift proxy. Specifically, we've introduced two host groups: one for the secondary load balancer (serving as the initial entry gateway) and another for the Swift proxy services. 🔹 **Key Point 1:** We've decoupled the Swift proxy from other OpenStack API services. As a result, the load balancer for Swift must also be isolated from the main load balancer handling other APIs. 🔹 **Key Point 2:** The Swift service registers itself with the existing Keystone service. Depending on the configuration: - If `second_loadbalancer` is enabled, Keystone will expose the load balancer VIP as the endpoint for object storage. - If `second_loadbalancer` is disabled, Keystone will use the direct API address of the Swift proxy. We've attached an architectural diagram to illustrate the overall setup. We’d love to share this approach and welcome any feedback or suggestions from the community. Our broader goal is to eliminate the barriers to managing both storage and OpenStack services simultaneously within a single deployment and through a unified tool. Thanks in advance for your insights!

2 1

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2026.1/R-25)
by Goutham Pacha Ravi 06 Oct '25

06 Oct '25

Hello Stackers, We're officially in the 2026.1 "Gazpacho" development cycle [1]. Congratulations on the successful and timely release of OpenStack's 32nd release: 2025.2 "Flamingo". For more information on the release, the OpenInfra Foundation staff have pieced together a release highlight on the OpenStack website [2], and project maintainers spoke about the release on OpenInfra Live [3] last week. In the past week, as our focus slowly began shifting between release boundaries, the OpenStack Technical Committee welcomed a new Vice-Chair, Michał Nasiadka (mnasiadka). We're exploring options for an alternate weekly meeting timing that could be friendly to our contributors in the Eastern Hemisphere. mnasiadka will be leading these meetings, while we still hope to continue a good cadence on our existing weekly meetings. I'll bring you more details about this change as we finalize the details. We're also actively planning sessions for the upcoming OpenInfra PTG. The OpenStack TC etherpad is available for you to propose topics [4]. Please feel free to add a topic along with your nick and timezone so we can coordinate a final schedule during the PTG week, avoiding as many conflicts as possible. In the past week, the TC appointed Felipe Reyes (freyes) as the PTL to the OpenStack Charms project [5]. We extended the "inactive" status of the Monasca team through the 2025.2 release cycle, and a decision on its retirement is imminent. There are similar proposals regarding other teams that had no PTL nominees in this past round of elections. === Weekly Meeting === The TC weekly meeting on September 30th 2025 [6] focused primarily on addressing leaderless projects and filling key TC roles. The committee proposed to mark both the Venus and Vitrage project teams as "inactive" and notify the openstack-discuss mailing list, as neither team has found a new Project Team Lead (PTL) so far. The Gerrit activity on both these projects has shown a slowdown, which could either mean maturity and stability, or lack of maintenance. Continuous integration system jobs are failing for some of the deliverables; therefore, they're not release-worthy for now. If maintenance and development activity does not resume over the 2026.1 release cycle, the deliverables will be retired. We discussed the need for TC liaisons to the Freezer, Oslo, Release Management, and Requirements projects. Sylvain Bauza (bauzas) and I will continue being the OpenStack VMT liaisons. We noted progress on the recent community engagement regarding Skyline's health and patch merging [7], and discussed plans to mentor one or more new core maintainers, and possibly hold a dedicated slot at the upcoming PTG (Project Team Gathering) to encourage further engagement. The TC is running an internal poll to find a preferred time slot and format (video vs. IRC) for future meetings, including a request for a slot that better suits EU and APAC time zones. The next meeting of the OpenStack TC is on October 7th 2025. This meeting will be hosted on Meetpad and IRC simultaneously. Please find the meeting's agenda and joining details in the wiki [8]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== - Add 2026.1 TC chair and vice-chair | https://review.opendev.org/c/openstack/governance/+/962614 - Extend Monasca's inactive state | https://review.opendev.org/c/openstack/governance/+/959392 - Appoint Felipe Reyes as PTL for OpenStack Charms | https://review.opendev.org/c/openstack/governance/+/962121 - pti: Remove reference to 'python setup.py' | https://review.opendev.org/c/openstack/governance/+/962920 - pti: Update to reference pyproject.toml | https://review.opendev.org/c/openstack/governance/+/962921 ==== Open For Review ==== - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Mark Vitrage project-team inactive | https://review.opendev.org/c/openstack/governance/+/963227 - Mark Venus project-team inactive | https://review.opendev.org/c/openstack/governance/+/963228 === Upcoming Events === - 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] 2026.1 "Gazpacho" Release Schedule: https://releases.openstack.org/gazpacho/schedule.html [2] 2025.2 "Flamingo" release page: https://www.openstack.org/software/openstack-flamingo [3] OpenInfra Live previewing the 2025.2 "Flamingo" release: https://www.youtube.com/watch?v=cdqL6umlM1w [4] OpenStack TC etherpad for 2026.1 "Gazpacho" PTG: https://etherpad.opendev.org/p/oct2025-ptg-os-tc [5] Appointing PTL for OpenStack Charms: https://review.opendev.org/c/openstack/governance/+/962121 [6] TC Meeting IRC Log, Sep 30th 2025:https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-30-17.00.html [7] Skyline Maintenance discussion: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [8] TC Meeting Agenda, Oct 7th 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[ironic][power] Anyone using PReP partitioning support?
by Julia Kreger 06 Oct '25

06 Oct '25

Greetings Power folks! The Ironic project is curious if anyone is using PReP partitioning support? Specifically Ironic has long had a code path to manage creation of the PReP partition for booting power hardware as part of the partition image path code, but as time has gone on we're unsure if anyone is actively using this code path on newer versions of Ironic, coupled with the general decline of partition image usage. If anyone is using Power with newer versions of Ironic, please let us know if you're using partition images with Ironic, thus using PReP partitions. Specifically we're curious because we have a discussion topic which has been raised for the upcoming PTG. Thanks! -Julia

2 2

[Nova] Need to reschedule the Nova upstream meeting ⏰
by René Ribaud 06 Oct '25

06 Oct '25

Hi everyone, We need to move the current Nova upstream meeting, as most contributors, myself included, are busy in another meeting at that time. Finding a new slot is not straightforward, since some of our meetings are recurring and the daylight saving changes add additional complexity. Over the past few weeks, I tried to narrow down the possible options, and here’s a short poll with different time slots to choose from: https://framadate.org/ao12zK6wR3K3nfbF If none of these options work for you, or if you have other suggestions, please reply to this thread. Please note that we might need to adjust the schedule again later in the year, either due to daylight saving changes or if our other recurring meetings start to overlap again. Thanks for your understanding and input! Cheers, René

1 0

[publiccloud-sig] Public Cloud SIG meeting d.d. 8 October
by Kees Meijs | Nefos 06 Oct '25

06 Oct '25

Hello Stackers, The day after tomorrow (that's 8 October) the bi-weekly Public Cloud SIG meeting will be held again. The publicly available video meeting will be conducted from 07:00 hrs UTC (09:00 hrs CEST) and on here: https://meetpad.opendev.org/publiccloud-sig Additional information to be found on https://wiki.openstack.org/wiki/PublicCloudSIG Unfortunately I'm unable to join myself this episode, but obviously feel free to discuss relevant topics. See you next time, or next week in Paris. Cheers, Kees __ Kees Meijs BICT Nefos Cloud & IT <https://nefos.com/contact> Nefos IT bv Burgemeester Mollaan 34a 5582 CK Waalre - NL kvk 66494931 +31 (0)88 2088 188 <tel:+31882088188> nefos.com <https://nefos.com/contact> The information contained in this message is intended for the addressee only and may contain classified information. If you are not the addressee, please delete this message and notify the sender; you should not copy or distribute this message or disclose its contents to anyone. Any views or opinions expressed in this message are those of the individual(s) and not necessarily of the organization. No reliance may be placed on this message without written confirmation from an authorised representative of its contents. No guarantee is implied that this message or any attachment is virus free or has not been intercepted and amended. General terms and conditions ("The NLdigital Terms") apply to all our products and services.

1 0

[neutron] Bug deputy report for week 40 of 2025 (September 29)
by Lajos Katona 06 Oct '25

06 Oct '25

Hi Neutrinos! Last week (week 40, from September 29) I was the Neutron bug deputy, please check the report for that week. As usual the team will discuss these bugs quickly during the weekly team meeting: https://meetings.opendev.org/#Neutron_Team_Meeting High Bugs ---------------- * Unassigned: https://bugs.launchpad.net/neutron/+bug/2126032 ([CI] Random failure network create with Error while executing command: HttpException: 503, Unable to create the network. No tenant network is available for allocation.) Only on 2025.1 branch * eventlet: https://bugs.launchpad.net/neutron/+bug/2126790 (q-dhcp process is not gracefully shutting down ) * eventlet: https://bugs.launchpad.net/neutron/+bug/2126791 (q-agt process is not gracefully shutting down ) * https://bugs.launchpad.net/neutron/+bug/2126033 (2025.2 centos jobs fails as https://trunk.rdoproject.org/centos9-2025.2/delorean-deps.repo not exists ) Yatin follows it. * https://bugs.launchpad.net/neutron/+bug/2126061 ([ovs-agent] slow start with large number of ports ) patch: https://review.opendev.org/c/openstack/neutron/+/962627 * https://bugs.launchpad.net/neutron/+bug/2126576 ([S-RBAC] Policies for local_ip_association don't work as expected), patch: https://review.opendev.org/c/openstack/neutron/+/962751 * https://bugs.launchpad.net/neutron/+bug/2126759 ([S-RBAC] Policies for l3_conntrack_helpers don't work as expected ) patch: https://review.opendev.org/c/openstack/neutron/+/962919 Medium Bugs ------------------ * Unassigned; https://bugs.launchpad.net/neutron/+bug/2126637 ([OVN] Router "after_update" event contains wrong information with GW multihoming API ) * Unassigned: https://bugs.launchpad.net/neutron/+bug/2126685 (test_add_external_port_avoid_flapping functional test failure ) * https://bugs.launchpad.net/neutron/+bug/2126570 (DHCP agent - created port not stored in cache, may cause "stale" ) patch: https://review.opendev.org/c/openstack/neutron/+/962323 * https://bugs.launchpad.net/neutron/+bug/2126588 ([OVN] The Logical_Router pinning breaks the external ports HA_Chassis_Groups ) patch: https://review.opendev.org/c/openstack/neutron/+/962746 Best wishes, Lajos Katona (lajoskatona)

1 0

[OpenStack Ansible] [Deployment] Retrieve upper constraints issue
by holywine＠outlook.com 05 Oct '25

05 Oct '25

Hello, Following the instruction here (https://docs.openstack.org/project-deploy-guide/openstack-ansible/2025.1/) step by step to deploy openstack with openstack-ansible stable/2025.1 release on four computers (Infra1, Infra2, compute1, compute2) with a fifth computer as deployer (localhost)。 During the execution of command “openstack-ansible setup-infrastructure.yml” error pops up and installation broke. The log is as the following: ... TASK [repo_server : Ensure deploy host u-c directory exists] ******************************************************************************************* ok: [infra1-repo-container-769e886d -> localhost] TASK [repo_server : Retrieve upper constraints using https] ******************************************************************************************** FAILED - RETRYING: [infra1-repo-container-769e886d -> localhost]: Retrieve upper constraints using https (5 retries left). FAILED - RETRYING: [infra1-repo-container-769e886d -> localhost]: Retrieve upper constraints using https (4 retries left). FAILED - RETRYING: [infra1-repo-container-769e886d -> localhost]: Retrieve upper constraints using https (3 retries left). FAILED - RETRYING: [infra1-repo-container-769e886d -> localhost]: Retrieve upper constraints using https (2 retries left). FAILED - RETRYING: [infra1-repo-container-769e886d -> localhost]: Retrieve upper constraints using https (1 retries left). fatal: [infra1-repo-container-769e886d -> localhost]: FAILED! => attempts: 5 changed: false dest: /etc/openstack_deploy/upper-constraints/upper_constraints_bfd91c04caf498be2bfda0732a2a0f9fa9306e07.txt elapsed: 0 gid: 0 group: root mode: '0644' msg: 'Request failed: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)>' owner: root size: 13007 state: file uid: 0 url: https://releases.openstack.org/constraints/upper/bfd91c04caf498be2bfda0732a… Can anybody please give a clue on what is going on and how to do troubleshooting? Thanks a lot in advance! Regards, Hewi

2 4

[OpenStack Ansible] [Deployment] Retrieve upper constraints issue
by holywine＠outlook.com 04 Oct '25

04 Oct '25

Hello, Following the instruction here (https://docs.openstack.org/project-deploy-guide/openstack-ansible/2025.1/) step by step to deploy openstack with openstack-ansible stable/2025.1 release on four computers (Infra1, Infra2, compute1, compute2) with a fifth computer as deployer (localhost)。 During the execution of command “openstack-ansible setup-infrastructure.yml” error pops up and installation broke. The log is as the following: ... TASK [repo_server : Ensure deploy host u-c directory exists] ******************************************************************************************* ok: [infra1-repo-container-769e886d -> localhost] TASK [repo_server : Retrieve upper constraints using https] ******************************************************************************************** FAILED - RETRYING: [infra1-repo-container-769e886d -> localhost]: Retrieve upper constraints using https (5 retries left). FAILED - RETRYING: [infra1-repo-container-769e886d -> localhost]: Retrieve upper constraints using https (4 retries left). FAILED - RETRYING: [infra1-repo-container-769e886d -> localhost]: Retrieve upper constraints using https (3 retries left). FAILED - RETRYING: [infra1-repo-container-769e886d -> localhost]: Retrieve upper constraints using https (2 retries left). FAILED - RETRYING: [infra1-repo-container-769e886d -> localhost]: Retrieve upper constraints using https (1 retries left). fatal: [infra1-repo-container-769e886d -> localhost]: FAILED! => attempts: 5 changed: false dest: /etc/openstack_deploy/upper-constraints/upper_constraints_bfd91c04caf498be2bfda0732a2a0f9fa9306e07.txt elapsed: 0 gid: 0 group: root mode: '0644' msg: 'Request failed: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)>' owner: root size: 13007 state: file uid: 0 url: https://releases.openstack.org/constraints/upper/bfd91c04caf498be2bfda0732a… Can anybody please give a clue on what is going on and how to do troubleshooting? Thanks a lot in advance! Regards, Hewi

1 0

[kolla][kolla-ansible] Managing Object Storage Backend via Kolla-Ansible
by sarah.kh09＠gmail.com 04 Oct '25

04 Oct '25

Hello everyone, We are currently using Kolla-Ansible stable/2024.1 to manage our OpenStack deployment, including both core services and the Swift object storage backend. Our goal is to manage all OpenStack services, including object storage, through a unified lifecycle management tool. We understand that managing large volumes of data can affect the performance of other services. To address this, we've separated the data flow entry points that could become bottlenecks into dedicated host groups: a load balancer and a Swift proxy. Specifically, we've created two separate host groups: one for the secondary load balancer (which serves as the initial entry point) and another for the Swift proxy services. 🔹 Key Point 1: Decoupling Swift Traffic We’ve separated the Swift proxy nodes from the other OpenStack API services. This also means that the load balancer handling Swift traffic must be distinct from the main load balancer used for services like Nova, Glance, and Neutron. 🔹 Key Point 2: Keystone Endpoint Behavior Swift still registers with the existing Keystone service. Depending on the configuration: - If the second_loadbalancer is enabled, Keystone publishes the VIP (Virtual IP) of the secondary HAProxy as the Swift endpoint. - If it’s disabled, Keystone uses the direct API address of the Swift proxy node. 🔹 Key Point 3: Two Supported Configurations Kolla-Ansible supports two architecture models for Swift: Normal and Advanced. - Normal Configuration This is the default setup in stable/2024.1, where all OpenStack services, including Swift, share the same load balancer and traffic path. - Advanced Configuration This is recommended for large-scale deployments with heavy data volumes. In this setup, Swift traffic goes through a dedicated load balancer and proxy nodes, which reduces contention and improves performance. We’d love to share this approach with the community and welcome any feedback or suggestions. Our goal is to make managing both compute and storage services within a single deployment framework as simple as possible. Thanks in advance for your insights!

1 0

[Kolla][Kolla-Ansible] Making the use of mirrors easier on container build
by Michael Still 04 Oct '25

04 Oct '25

Oh hello, For the last couple of years I've been working on trying to improve the VDI experience in OpenStack by enriching our SPICE capabilities. A series of patches has now landed in Nova that enable SPICE native console sessions from outside the cloud, I have a working (but probably not completely finished) SPICE native proxy, and the next step is adding deployment support to Kolla-Ansible so that I can start demoing an end to end implementation. I have a draft of those changes, but don't feel quite ready to push them to Gerrit just yet. As part of that I've been building my own Kolla images in my homelab CI environment for a couple of years now. I don't know about others, but for me by far the most common reason for these builds to fail is because of intermittent connectivity to upstream package repositories -- either flaky networking, random noise, or rate limiting. Increasingly I find myself carrying private patches to use local mirrors instead of the upstream sources. It occurs to me I might not be the only one with this sort of use case. I therefore wonder how the Kolla team would feel about abstracting the upstream sources of various build dependencies so that they were defined centrally? That would make it much easier both to override sources with local mirrors, as well as define exactly what upstream sources are required to conduct a build. If that's a reasonable thing to do, where would people see that list sitting? My initial thought is in the defaults for the kolla-build ansible role, but I am definitely not a Kolla expert so I am open to guidance here. Cheers, Michael -- Person on the internet. https://madebymikal.com. He / his / him.

2 2

[blazar] Meeting cancelled 16th October 2025
by Matt Crees 02 Oct '25

02 Oct '25

Hi all, Due to lack of availability of the core team, the fortnightly Blazar meeting will be cancelled on the 16th October. This means the next time that we'll meet will be at the PTG. I look forward to seeing you all there. Kind regards, Matt Crees, on behalf of the Blazar project.

1 0

OpenStack 2025.2 'Flamingo' on OpenInfra Live
by Allison Price 02 Oct '25

02 Oct '25

Hi everyone, Come learn about the latest OpenStack release, 2025.2 ‘Flamingo’ on OpenInfra Live tomorrow! We have a great lineup of community leaders who can talk about community-wide and project-specific progress. The episode will air tomorrow, October 2 at 1400 UTC and you can ask questions live that our contributors will answer during the episode. Goutham Pacha Ravi, OpenStack Technical Committee Iury Gregory, Ironic Rene Ribaud, Nova Carlos Silva, Manila Brian Haley, Neutron You can watch on YouTube[1] or LinkedIn[2]. See you there! Cheers, Allison [1] https://www.youtube.com/watch?v=cdqL6umlM1w [2] https://www.linkedin.com/posts/openinfra-foundation_learn-more-about-the-32…

1 1

Ironic Community dinner/meet-up at Open Infra Summit Europe 2025
by Riccardo Pittau 02 Oct '25

02 Oct '25

Hello ironicers! The Ironic community is organizing a dinner/meet-up on October Friday 17th in Paris, the first night of the Open Infra Summit Europe. If you'd like to join please add your name here: https://etherpad.opendev.org/p/Ironic_OIS_community_dinner_in_Paris We'll collect the number of participants by next Monday October 6th to be able to book enough time in advance. Ciao Riccardo

1 0

Short Bitergia dashboard outage due to maintenance
by Ildiko Vancsa 01 Oct '25

01 Oct '25

Hi OpenStack community, I’m reaching out to let you know that the OpenStack Bitergia metrics dashboard[1] will be unavailable for a short period of time due to scheduled maintenance, where the underlying OpenSearch cluster will be updated. Details of the downtime: * Start Date: Monday, October 06 at 800 UTC * End Date: Tuesday, October 07 at 1600 UTC __During this maintenance window, the dashboard will be inaccessible.__ Please also note that data updates will not resume until Wednesday (October 08). Thank you for your understanding. Best Regards, Ildikó [1] https://openstack.biterg.io/app/dashboards#/view/Overview

1 0

OpenStack 2025.2 "Flamingo" is officially released!
by Elõd Illés 01 Oct '25

01 Oct '25

Hello OpenStack community, The official OpenStack 2025.2 Flamingo release announcement has been sent out: https://lists.openstack.org/archives/list/openstack-announce@lists.openstac… Thanks to all who were a part of the 2025.2 Flamingo development cycle! This marks the official opening of the openstack/releases repository for 2026.1 Gazpacho releases, and freezes are now lifted. stable/2025.2 is now a fully normal stable branch, and the normal stable policy applies from now on. Thanks, Előd Illés on behalf of the Release Management team

3 2

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

01 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

[openstack-ansible] watcher support with openstack-ansible
by keshav bareja 01 Oct '25

01 Oct '25

Hi Team We would like to know if there is any plan to add watcher service support in openstack-ansible. Our current release is below and we need to add watcher service for our release. Openstack-ansible Caracal 2024.1 Regards Keshav

2 2

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 29 Sep '25

29 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 29 Sep '25

29 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 29 Sep '25

29 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

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

29 Sep '25

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

2 4

[Neutron][operators] LinuxBridge to OVN Outreach
by Daniel Failing 29 Sep '25

29 Sep '25

Hi all, Following on the good session we had last time discussing migrating out of LinuxBridge between operators, it was proposed to meet again in June. To find a good time slot, please respond to the following survey: https://newdle.cern.ch/newdle/TtbH8Dbv For reference, the notes from last meeting: https://etherpad.opendev.org/p/neutron-lb-ovn-migration Best, Daniel Failing CERN Cloud Infrastructure

2 3