- openstack-discuss - lists.openstack.org

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 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

[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

[neutron] Bug deputy report for week 39 of 2025 (September 21st)
by Miguel Lavalle 29 Sep '25

29 Sep '25

I was the Neutron bug deputy last week. Following is a brief summary of the reported bugs: High bugs -------------- https://bugs.launchpad.net/neutron/+bug/2125478 [OVN] External ports scheduler (using HA_Chassis_Group) should consider the physical network mappings. Assignee Rodolfo Alonso. https://bugs.launchpad.net/neutron/+bug/2125500 Metadata port fixed IPs missing from port. It needs an owner. Medium ----------- https://bugs.launchpad.net/neutron/+bug/2125553 [OVN] Collocate the external ports in the same chassis as the gateway port. Assignee Rodolfo Alonso. Proposed fix https://review.opendev.org/c/openstack/neutron/+/962155 https://bugs.launchpad.net/neutron/+bug/2125569 [OVN] The method to sync the HA_Chassis_Group should always update the "ignore_chassis" variable. Assignee Rodolfo Alonso. Proposed fix https://review.opendev.org/c/openstack/neutron/+/962191 https://bugs.launchpad.net/neutron/+bug/2125715 OVN DHCPv6 support for Option 59. Assignee Harald Jensas. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/962317 Need further refinement -------------------------------- https://bugs.launchpad.net/neutron/+bug/2125573 Octavia LB FIP reachability broken when VRRP failover happens https://bugs.launchpad.net/neutron/+bug/2125482 Subsequent BGP speaker scheduled onto dragent does not work -- Miguel Lavalle He/Him/His Principal Software Engineer - OpenStack Networking mlavalle(a)redhat.com M: +1 (713) 859-0591

1 0

ovpn-dco on RHEL10 based distribution
by William Muriithi 28 Sep '25

28 Sep '25

Hello, I have a openvpn server on RHEL10 and I would like to use ovpn-dco on it. Currently, I don't have a working kernel on it. 2025-09-24 10:27:17 us=861227 Note: Kernel support for ovpn-dco missing, disabling data channel offload. This is the only working binaries. openvpn-2.7_beta1-1.el10_0.alma_altarch.x86_64_v2 openvpn-auth-oauth2-1.26.0-1.x86_64 [root@openvpn-lab ~]# If I install openvpn-2.6, the openvpn server wouldn't start because of this error. symbol lookup error: /usr/sbin/openvpn: undefined symbol: EVP_MD_CTX_get_size_ex, version OPENSSL_3.4.0. The kernel module seem ok as the system at least boot. Its just that openvpn don't work after the system is up. So, only way seem to figure out how to get openvpn 2.7 module booting on RHEL10 Kallsyms_lookup_name+0x4/0xd0 kernel BUG at arch/x86/kernel/cet.c:102! Oops: invalid opcode: 0000 [#1] PREMPT SMP NOPTI Tainted: [0]=OOT_MODULE, [E]=UNSIGNED_MODULE This is how I installed the dco that is breaking the boot process. https://community.openvpn.net/Pages/OpenVPN%20software%20repos OpenVPN software repos – community wiki<https://community.openvpn.net/Pages/OpenVPN%20software%20repos> Introduction This page contains instructions for using OpenVPN project's own software repositories. For OpenVPN 3 Linux, see the dedicated OpenVPN 3 Linux page. The OpenVPN project provides the latest OpenVPN releases (and development snapshots) as packages for major Linux distributions. This allow you to use more up-to-date version of OpenVPN than what is typically available in your ... community.openvpn.net yum copr enable @OpenVPN/openvpn-beta yum install kmod-ovpn That is, after that, the system wouldn't boot. Have anyone found a way to run dco on RHEL10. This is a openVPN server, so I didn't bother trying openVPN 3 Any pointer would be appreaciated. Regards, William

2 1

skyline patch merging, release and backports
by Doug Goldstein 28 Sep '25

28 Sep '25

Hello, It appears that skyline, both skyline-console and skyline-apiserver, have been broken from a test standpoint for a bit. Additionally the last patch from not one of the core members that has been merged was June 12th, which is also the last time a core member has commented on a patch not from the core members. There has been a recent uptick in contributors coming from another organization and I would like to help see their contributions land. Some of these are fixes so that the tests actually pass as well as fixes for other bugs and new features. There have also been requests for backports to 2025.1. What do we need to get this work to start landing and make sure this project stays healthy? fix for skyline-console tests: https://review.opendev.org/c/openstack/skyline-console/+/961092 fix for one of the two failing skyline-apiserver tests: https://review.opendev.org/c/openstack/skyline-console/+/961092 open skyline-apiserver changes: https://review.opendev.org/q/project:openstack/skyline-apiserver+status:open open skyline-console changes: https://review.opendev.org/q/project:openstack/skyline-console+status:open Thanks. — Doug

4 7

[openstack-ansible]Add Banner on openstack login page
by keshav bareja 26 Sep '25

26 Sep '25

Hi Team We need to add a banner or notification with a custom text on the openstack login page. Is there any way to do that ? openstack-ansible Carcal release 2024.1 Horizon 29.2.2 Regards Keshav Bareja

3 2

[ops][largescale-sig] Refactoring Ops-related activities - a discussion at the PTG
by Thierry Carrez 26 Sep '25

26 Sep '25

Hi everyone, We have several groups working in the OpenStack community to propose activities and content that are relevant to OpenStack operators: - The Ops meetup[1] group, currently producing Ops Radio Hour - The Large Scale SIG[2], producing the Scaling Journey documentation and the Large Scale OpenStack webinars - The Public Cloud SIG and the Scientific SIG, which focus on specific usage cases - Probably others that I miss... All of those groups overlap, and struggle with gathering enough volunteers to drive them forward. The fragmentation also hurts their discoverability for OpenStack operators out there, who are hungry to learn about the challenges of operating OpenStack and would like to hear more from the teams that do that successfully. I'd like to propose an open discussion at the PTG next month on how to refactor our ops-facing activities under a single, visible, and active banner. I propose we take a PTG meeting slot on Friday, October 31, at 16utc to discuss that with all interested volunteers. Thoughts, comments? -- Thierry Carrez (ttx)

2 1

[release] Release countdown for week R+0
by Thierry Carrez 26 Sep '25

26 Sep '25

Development Focus ----------------- We will be releasing the coordinated OpenStack 2025.2 "Flamingo" release next week, on October 1st, 2025. Thanks to everyone involved in the 2025.2 "Flamingo" cycle! We are now in pre-release freeze, so no new deliverable will be created until final release, unless a release-critical regression is spotted. Otherwise, teams attending the PTG should start to plan what they will be discussing there, by creating and filling team etherpads. You can access the list of PTG etherpads at: http://ptg.openstack.org/etherpads.html General Information ------------------- On release day, the release team will produce final versions of deliverables following the cycle-with-rc release model, by re-tagging the commit used for the last RC. A patch doing just that will be proposed. PTLs and release liaisons should watch for that final release patch from the release team. While not required, we would appreciate having an ack from each team before we approve it on the 1st, so that their approval is included in the metadata that goes onto the signed tag. Upcoming Deadlines & Dates -------------------------- Final 2025.2 "Flamingo" release: October 1st, 2025 OpenInfra Summit Europe: October 17th-19th, 2025 OpenStack PTG (virtual): October 27th-31st, 2025 -- Thierry Carrez (ttx)

1 0

For Information
by Suraj Silwal 26 Sep '25

26 Sep '25

I am just participating, I need get to go , please help me how I set up and contribute in openstack.

2 1

[openstack-ansible][ussuri] moving openstack deployment node to other host
by Danish Khan 25 Sep '25

25 Sep '25

Dear Team, Our controller1 node which was also openstack deployment node somehow crashed and is not accessible now. I am trying to make controller3 as new deployment node. Below is the step which I am planning to follow. I have backup of (openstack-ansible, openstack_deploy and ansible directory of controller1 ): 1. Place /opt/openstack-ansible directory from controller1 to controller3 2. copy /etc/openstack_deploy directory from controller1 to controller3 3. copy /etc/ansible/ directory from controller1 to controller3 4. run bootstrap on controller3 5. test if openstack-ansible has picked same clusters and inventory. Can someone please suggest if this is correct approach or if I am missing something. Regard, Danish

2 1

[kolla] [swift] Seeking reviews for reinstating Swift support for 2025.2
by Amir Hossein Ahmadi 25 Sep '25

25 Sep '25

Hello Kolla and OpenStack community, A few months ago, Swift support was removed from the Kolla project due to several challenges, including the need for role modernization, the lack of dedicated maintainership, and persistent CI failures. Following that, I volunteered to take on this effort. Over the last few months, I have been working to address these issues and am happy to report significant progress: - *Modernized Roles:* The Swift roles have been fully updated to align with the latest Kolla and Kolla-Ansible development standards. - *Reliable CI:* The associated Zuul jobs are now consistently green, with all tests successfully validated. - *Maintainership:* I have stepped up to maintain the Swift service within Kolla, ensuring its long-term health and stability. A considerable amount of effort has been invested to ensure this implementation is robust and maintainable for the community. With the *2025.2 release deadline just four weeks away*, the final and most critical step is to get these patches reviewed and merged. Your feedback and reviews are crucial to landing this work in time for the release. Reinstating Swift support would be a valuable addition for many operators. Any time you can spare to look over the patches would be greatly appreciated. You can find the main patch series here: https://review.opendev.org/q/topic:%22dev-swift-modernization%22 Thank you for your consideration and for all your contributions to the OpenStack community. Best regards, Amir Hossein (IRC: amir58118)

5 5

[largescale-sig] Next meeting: September 23, 14utc
by Thierry Carrez 24 Sep '25

24 Sep '25

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC at 14UTC. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250923T14 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 3

Upgrade Caracal --> Epoxy obstacles
by Eugen Block 24 Sep '25

24 Sep '25

Good morning, I just wanted to share some of our experience from this week when we upgraded our production cloud from Caracal to Epoxy (and also Ubuntu 22.04 --> 24.04). It wasn't as easy as previous upgrades, there were a couple of obstacles on the way. # RabbitMQ The main issue was rabbitmq, I'd say. Since the rabbitmq version was 3.9 on Jammy, we had to get to 3.12 for Noble. I had tried a lot of things in my test environment, in the end I decided to reduce the number of rabbitmq hosts to one, upgraded it with podman from 3.9 to 3.10 to 3.11 to enable the feature flags required for 3.12 (all still under Jammy). Then I could upgrade the OS to Noble so the package based rabbitmq-server would start successfully. # Database The recent thread about older password hashes (https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…) was helpful, we set the same passwords for those system users that came up in the MySQL query, and we didn't notice any issue. But there were two issues we had to deal with regarding the database: During nova-manage db sync we got these errors: 2025-09-22 14:08:19 2 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), fou nd type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). 2025-09-22 14:08:19 2 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). This had not popped up during my tests, but our production database is around 10 years old when we started with our OpenStack journey, my test environment is quite new. What fixed it was: mysql_upgrade check-if-upgrade-is-needed Then there's another thing I have to fully grasp yet, but we now have a ".local" directory in /var/lib/mysql: find /var/lib/mysql/.local/share/containers/storage/ /var/lib/mysql/.local/share/containers/storage/ /var/lib/mysql/.local/share/containers/storage/libpod /var/lib/mysql/.local/share/containers/storage/db.sql Which mysql_upgrade didn't like. I assume that podman created that, but I'm not sure why (I only created a rabbitmq pod). Anyway, I removed that directory so I could proceed with the db sync commands to complete the upgrade process. In my test cloud I removed podman, then restarted galera and the directory is gone, so that's what I'm gonna do in the production as well. # opentack-client Then there are these messages during every openstack command: Could not load 'message_list': module 'zaqarclient.queues.v2.cli' has no attribute 'OldListMessages' Could not load 'message_post': module 'zaqarclient.queues.v2.cli' has no attribute 'OldPostMessages' I'll need to check if they impact any of our scripts, we don't use zaqar, but removing that package would also remove heat, so that won't be possible. # nova-compute: I waited for version 19.2.1 of librbd1 to be released, otherwise nova-compute would fail: qemu-block-extra : Depends: librbd1 (>= 19.2.1-0ubuntu0.24.04.1) but 19.2.0-0ubuntu0.24.04.2 is to be installed # neutron-metadata-agent There's a bug for functioning agents showing as dead, applying the mentioned patches fixes it: https://bugs.launchpad.net/neutron/+bug/2112492 # Pacemaker We use pacemaker for high availability and during the dist-upgrade I had to run 'apt --fix broken', then remove resource-agents and resource-agents-base to get through the dist-upgrade, then install pacemaker and crmsh again afterwards. Not sure if anyone will read this far, but I wanted to get that off my chest. ;-) So obviously, most of the issues weren't really OpenStack issues, but I wanted to share this experience anyway. If you read this far, thanks! ;-) Regards, Eugen

3 2