- openstack-discuss - lists.openstack.org

[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

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

28 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