- openstack-discuss - lists.openstack.org

[designate] DNS records stuck in PENDING state but records created succesfully
by Jadon Naas 23 Sep '25

23 Sep '25

Hello! I am using Designate on 2023.2 with a PowerDNS backend. I have a recordset with three A records created through Designate. The A records are stuck in "PENDING" state with action "CREATE" or "UPDATE". The records were successfully created in PowerDNS, and changes are pushed to PowerDNS. However, the record status never finishes updating. Deleting and recreating the recordset results in the same situation. I do not see any notable errors in the logs for Designate or for PowerDNS. I have checked that the Desigate configuration for the nameservers and for the targets match the correct IP addresses for my PowerDNS server and for my Designate service hosts. Would folks have any suggestions for what I could do to determine what is preventing Designate from updating these records or to manually update the status of the records? Thank you! Jadon Naas

2 1

[publiccloud-sig] Public Cloud SIG meeting d.d. 23 September
by Kees Meijs | Nefos 23 Sep '25

23 Sep '25

Hello Stackers, Tomorrow (that's 23 September) 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 See you tomorrow! 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 1

Compatebilty
by nahoms＠altacomputec.com 23 Sep '25

23 Sep '25

The customer currently uses 15 Dell PowerEdge R650 servers for their OpenStack private cloud and wants to expand. Is there any compatibility issue if we propose Lenovo servers along with the existing Dell ones?

2 1

[octavia] Creation of several master amps
by yardalgedal＠gmail.com 23 Sep '25

23 Sep '25

Hi all, we're using octavia of version zed and caught a case when it regularly creating 3 amphorae instead of 2. We have not had any amphorae for which of these LBs and I did failover for each of them: openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer failover 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer failover 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 openstack loadbalancer failover f9f859d0-2b31-449b-8723-700bb7f3f3f4 then first backup amphorae was created pretty fast openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 3dfa43cd-2719-487e-8ba2-8a4aa0fe7301 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | BACKUP | 10.94.64.112 | 10.210.73.197 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | b39472aa-04a0-42b8-8c09-4617ea1a0f33 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | BACKUP | 10.94.64.232 | 10.210.64.32 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | 60af8e11-c6ad-45f0-8e07-1bcc4a477444 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | BACKUP | 10.94.64.74 | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ but then it started to create 2x Master's for each (!) of them (we can talk about lags, but not in case of 3x): openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 3dfa43cd-2719-487e-8ba2-8a4aa0fe7301 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | BACKUP | 10.94.64.112 | 10.210.73.197 | | 3dd9bdb4-0dfe-4d77-b08f-02fbbffcd892 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | BOOTING | None | None | None | | ff6ec3de-6942-4978-9ea5-d793ff1fdbf8 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | BOOTING | None | None | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | b39472aa-04a0-42b8-8c09-4617ea1a0f33 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | BACKUP | 10.94.64.232 | 10.210.64.32 | | 9909b300-d266-4344-b6fc-edc4af651485 | 96223d34-6941-4bc5-881a-ddfd83070739 | BOOTING | None | None | None | | cc123c55-2953-425e-867e-f4057483bb09 | 96223d34-6941-4bc5-881a-ddfd83070739 | BOOTING | None | None | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | 60af8e11-c6ad-45f0-8e07-1bcc4a477444 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | BACKUP | 10.94.64.74 | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ as a result we started to have 3x Master's for them openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 3dfa43cd-2719-487e-8ba2-8a4aa0fe7301 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | BACKUP | 10.94.64.112 | 10.210.73.197 | | 3dd9bdb4-0dfe-4d77-b08f-02fbbffcd892 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | MASTER | 10.94.64.56 | 10.210.73.197 | | 14e8acfe-8510-4629-a583-53ba88f91eca | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | MASTER | 10.94.64.30 | 10.210.73.197 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | b39472aa-04a0-42b8-8c09-4617ea1a0f33 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | BACKUP | 10.94.64.232 | 10.210.64.32 | | 9909b300-d266-4344-b6fc-edc4af651485 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | MASTER | 10.94.64.151 | 10.210.64.32 | | 9d197234-6411-4069-8be3-a399cc1fbc3a | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | MASTER | 10.94.64.212 | 10.210.64.32 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 60af8e11-c6ad-45f0-8e07-1bcc4a477444 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | BACKUP | 10.94.64.74 | 10.211.193.63 | | d086f283-b9d8-4b23-a782-e0ace769e893 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | MASTER | 10.94.64.225 | 10.211.193.63 | | 8a90fc7c-eb0a-4635-8ece-7c4704c60f7a | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | MASTER | 10.94.64.50 | 10.211.193.63 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ taskflow is enabled in our case, backend is redis can you suggest smth to check or maybe some updates were already done?

3 3

[all][tc] Retrospective for OpenStack Elections
by Goutham Pacha Ravi 22 Sep '25

22 Sep '25

Hello Stackers, The OpenStack Technical Committee would like to take a moment to reflect on the recently concluded elections [1][2]. Elections and renewal of governance are a cornerstone of our Open Community principle [3]. We firmly believe that well-governed projects are sustainable and successful. In the recent elections, we saw 78 electors cast their votes to elect members to the TC out of 173 eligible voters. Jeremy Stanley (fungi) is planning to follow up with some more detailed analysis, but I wanted to kick-start this thread to share a few insights and initiate a call-to-action. To be eligible to contest or vote in OpenStack elections, you must meet two criteria: - You must be an Active Contributor, which means you have had a change merged in the roughly one-year period prior to the elections. - You must be an "Individual Member" of the OpenInfra Foundation (not a "Community Member") at the time the electoral rolls are created. This date is published and typically occurs a few days before polling begins. For the recently concluded 2026.1 elections, we identified over 650 active contributors in the one-year timeframe. However, as you can see, the number of eligible voters and the number of actual voters were significantly smaller. We've identified a few key reasons for this: - Individual Membership Renewal: In the past few months, as the OIF has transitioned under the Linux Foundation, we asked all individual members to "renew" their memberships. OIF staff and OpenStack election officials noticed a drop in the electorate due to this new requirement. It's quite easy for an email seeking renewal to get lost in a crowded inbox. - Opt-in for Ballots: We host our elections with CIVS, a free and secure internet voting service. A ballot arrives via email when polling begins, but CIVS will not send you an email unless you have opted in. While we have tried to remind folks to enable these emails, they can still get "lost" in the noise. - Membership Type Confusion: Many of us may not realize that we need to be an "Individual" member of the OIF to participate in the governance process. I feel we need to do a better job of reminding people why this is needed, so they can make an informed choice about whether they'd like to impact the governance of OpenStack. Nearly 500 contributors are currently either "Community" members or have no affiliation with the OIF. We'd like to hear your thoughts and ideas on how we can improve in these areas (are there any more?). What can we do to ensure a wider and more engaged electorate in future elections? We believe that increasing participation is essential for the long-term health and success of the OpenStack community. Thank you, Goutham Pacha Ravi (gouthamr) OpenStack Technical Committee [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] https://opendev.org/openinfra/four-opens/src/branch/master/doc/source/openc….

2 1

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

22 Sep '25

Hello Stackers, We're wrapping up work on the 2025.2 "Flamingo" release [1] within all projects that follow the "cycle-with-rc" release model [2]. The coordinated release is scheduled for October 1, 2025. You can follow the cycle highlights that Project Team Leads and liaisons have put together to get a preview of what this release brings [3]. In the past week, election officials posted results from the Combined TC/PTL elections for the 2026.1 release cycle [4][5]. I'm happy to welcome Tony Breeds (tonyb) and welcome back Doug Goldstein (cardoe), Dr. Jens Harbott (frickler), and Sylvain Bauza (bauzas) to the OpenStack Technical Committee. On behalf of the TC, I'd also like to congratulate the newly appointed PTLs of 34 project teams. This includes Arnaud Morin (amorin), who is leading the Mistral project as a first-time PTL, and Li Liu (liliueecg), who is returning to Cyborg as PTL after the Stein release. Thank you all for dedicating your time to fill these important roles. In the past week, the TC didn't merge any new governance changes; however, a few are currently undergoing community review. === Weekly Meeting === The TC held its weekly meeting on OFTC's #openstack-tc IRC channel on September 16, 2025 [6]. We discussed the community's participation in the election process [7] and are seeking input on how the process can be improved. It's possible that any changes we come up with would need buy-in from the OpenInfra Foundation's Board and staff. We followed up on the effort to standardize database character sets and collations across OpenStack projects [8]. The TC agreed that consistency would be beneficial for operators and supported the plan to make this a community goal. We'll follow up regarding the details. We touched on the status of "leaderless" projects, specifically Venus, OpenStack Charms, and Vitrage. If we find no PTL volunteers, the TC plans to follow up with the project teams and discuss options like retirement, finding liaisons and switch projects to a DPL governance model, or moving the projects to a Special Interest Group (SIG). We briefly discussed the upcoming PTG (Project Teams Gathering), with a suggestion to dedicate the first two days to cross-project discussions to encourage collaboration. The meeting concluded with a discussion about vendoring a BSD-3 licensed library, ply, into the yaql project, which the TC approved after confirming the license is compatible with OpenStack's Apache V2 license [9]. The next meeting of the OpenStack Technical Committee is on September 23, 2025. This meeting will be hosted on OFTC's #openstack-tc IRC channel and will begin at 1700 UTC. Please find the meeting's agenda on the wiki [10]. I hope you'll be able to join us there! === Governance Proposals === ==== Open For Review ==== - Add TC/PTL results from 2026.1 election | https://review.opendev.org/c/openstack/governance/+/961598 - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - 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 - Extend Monasca's inactive state | https://review.opendev.org/c/openstack/governance/+/959392 === 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/ 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] "cycle-with-rc" release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] 2025.2 "Flamingo" Release highlights: https://releases.openstack.org/flamingo/highlights.html [4] 2026.1 TC election results: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [5] 2026.1 PTL election results: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [6] TC Meeting IRC Log, Sep 17th 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-16-17.00.html [7] 2026.1 Election Retrospective: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [8] Dealing with Mariadb/Mysql changes: https://etherpad.opendev.org/p/gazpacho-collations-charsets [9] Vendoring ply in OpenStack: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [10] TC Meeting Agenda, Sep 23rd 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[diversity] [outreachy] Call for mentors for Dec 2025 cohort
by Dmitry Tantsur 22 Sep '25

22 Sep '25

Hi folks! It's the Outreachy time of the year. Despite the enormous financial and organizational difficulties, the December cohort will start soon, and OpenStack is, as usual, a part of it. We're looking for mentors and their projects. Please submit your ideas to https://www.outreachy.org/communities/cfp/openstack/ by this Friday, Sep 26th. You can check my blog post https://owlet.today/posts/how-to-propose-the-best-project-for-outreachy/ on some tips. Note that, just like in the previous cycle, we'll only be able to fund one intern. I still hope we get a few project proposals for interns to choose from. Let me know if you have any questions! Dmitry on behalf on OpenStack community coordinators. P.S. Apologies for the late notice: it took us some time to confirm everything.

1 0

[neutron] bug deputy report for 2025w38
by Bence Romsics 22 Sep '25

22 Sep '25

Hi Team, We had the following new reports last week. Two of the High bugs are unassigned at the moment. High: * https://bugs.launchpad.net/neutron/+bug/2124252 [L3] A router with multiple GW ports fails when deleting the first one fixes proposed by Rodolfo: https://review.opendev.org/q/topic:bug/2124252 * https://bugs.launchpad.net/neutron/+bug/2124254 [L3] A router with multiple GW ports, if the first is deleted, the GW info is empty unassigned * https://bugs.launchpad.net/neutron/+bug/2124269 Can't bind an HA router_gateway port to chassis unassigned, could be related to the migration to HA Chassis Group RFEs: * https://bugs.launchpad.net/neutron/+bug/2123836 [RFE] Set a local TXT record in the DHCP agent/dnsmasq * https://bugs.launchpad.net/neutron/+bug/2124215 [RFE] Implement more graceful handling of dhcp_lease_duration reduction Opinion: * https://bugs.launchpad.net/neutron/+bug/2123848 [ovn-octavia-provider] Octavia LB not reachable with custom firewall appliance According to Froyo this should be discussed with OVN cores first. Invalid: * https://bugs.launchpad.net/neutron/+bug/2124259 [ovn] Direct routing (non NAT) does not work between VLAN and Geneve networks Problematic backport of WIP patches. * https://bugs.launchpad.net/neutron/+bug/2125034 During live-migration nova-conductor report 'No valid host was found' due to duplicated port bindings This looks like a nova bug, so I routed it to them. Cheers, Bence

1 0

[kolla][kolla-ansible] Python dependency handling in custom Ansible module without toolbox
by sarah.kh09＠gmail.com 22 Sep '25

22 Sep '25

Hi everyone, I'm developing a new Ansible module for one of the kolla-ansible roles, and it depends on a Python package that needs to be installed via pip on the target nodes. I understand that Kolla Ansible generally avoids installing Python packages directly on hosts, and prefers handling such dependencies through the kolla_toolbox container. However, in my case: - Deploying a sidecar container isn't feasible within our current architecture - Delegating execution to localhost or kolla_toolbox would introduce complexity that we’d rather avoid Given these considerations, I'm looking for alternative ways to handle this dependency while staying aligned with Kolla's principles of reproducibility and container isolation. Has anyone faced a similar situation or found a clean workaround? Is using kolla-toolbox the only standard and recommended approach in such cases? Thanks a lot for your help and feedback!

2 2

[nova] Nova API call duration increases after upgrading to Caracal
by Chang Xue 21 Sep '25

21 Sep '25

Hello, we recently upgraded from Bobcat to Caracal. After upgrading, an interesting increment of duration of nova api call is observed. It's involved to multiple API calls, e.g. os-query-sets, /v2.1/servers/detail, etc. And it seems to be accumulated, meaning whenever nova-api is restarted, the duration seems to be fairly fast, giving response within like 80, 90 ms. As it keeps running for like up to 10 days, the duration increases to over 500 ms. I noticed that Caracal is using UnifiedLimitsDriver instead of DbQuotaDriver. I tried to change nova.conf to use DbQuotaDriver but it seems not working well with reducing the duration. I understand that calling to Keystone and Placement (and likely other external APIs) could result to longer duration, but pretty confused why it shows up as accumulated. Wondering if anyone else in Openstack community noticed the similar issue, thanks!

6 14

[aodh][ceilometer] how create alarms with prometheus ceilometer backend
by Nguyễn Hữu Khôi 21 Sep '25

21 Sep '25

Hello. I try to set up alarm such as: openstack alarm create --type prometheus --type prometheus --name memory_high_alarm --query 'memory_usage{resource_id="21d0792e-2d01-4df9-958a-d9018d13207f"}' --threshold 10 I use ceilometer with prometheus backend but when it shows: +---------------------------+------------------------------------------------------------------+ | Field | Value | +---------------------------+------------------------------------------------------------------+ | alarm_id | cb7b8d07-0af1-4771-92c8-1a4c2ce4d1d1 | | name | memory_high_alarm | | description | prometheus alarm rule | | enabled | True | | ok_actions | [] | | alarm_actions | [] | | insufficient_data_actions | [] | | repeat_actions | False | | type | prometheus | | time_constraints | [] | | project_id | 31ef81adc8ad406e9e91e3eb8776c959 | | user_id | 2e7a252719434d93ae0d270c8753294d | | timestamp | 2025-09-18T14:10:50.467568 | | state | *insufficient data * | | state_timestamp | 2025-09-18T14:10:50.467568 | | state_reason | Not evaluated yet | | severity | low | | evaluate_timestamp | 2025-09-18T14:10:50.485384 | | comparison_operator | eq | | threshold | 10.0 | | query | memory_usage{resource_id="21d0792e-2d01-4df9-958a-d9018d13207f"} | +---------------------------+------------------------------------------------------------------+ and in aodh logs: 2025-09-18 21:20:02.442 1079 INFO aodh.evaluator [-] initiating evaluation cycle on 1 alarms 2025-09-18 21:20:02.442 1079 WARNING aodh.evaluator [-] Skipping alarm cb7b8d07-0af1-4771-92c8-1a4c2ce4d1d1, unsupported type: prometheus I am using openstack 2025.1 I would like to get some guides on this, Many thanks. Nguyen Huu Khoi

2 6

[aodh]how the evaluation process works
by Nguyễn Hữu Khôi 21 Sep '25

21 Sep '25

Hello, I would like to understand how the evaluation process works. For example, I have this rule: openstack alarm create --name memory_use_test \ --type gnocchi_resources_threshold \ --metric memory.usage \ --threshold 102 \ --comparison-operator gt \ --aggregation-method mean \ --granularity 60 \ --evaluation-periods 3 \ --resource-id dca36039-c603-422c-8366-f6ba4e9539c3 \ --resource-type instance Does this mean that when the alarm-evaluator service is running per a period, it will check the last 3 data points, each aggregated over 60 seconds? Thank you. Regards. Nguyen Huu Khoi

2 2

[ptl][charms][tc] Need a PTL volunteer for OpenStack Charms project team
by Goutham Pacha Ravi 20 Sep '25

20 Sep '25

Hello Stackers, We're missing a Project Team Lead (PTL) for the OpenStack Charms 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/+/943254

2 2

[release] Release countdown for week R-1, Sep 22 - 26
by Elõd Illés 19 Sep '25

19 Sep '25

Development Focus ----------------- We are on the final mile of the 2025.2 "Flamingo" development cycle! Remember that the 2025.2 "Flamingo" final release will include the latest release candidate (for cycle-with-rc deliverables) or the latest intermediary release (for cycle-with-intermediary deliverables) available. September 26th, 2025 is the deadline for final 2025.2 "Flamingo" release candidates as well as any last cycle-with-intermediary deliverables. We will then enter a quiet period until we tag the final release on October 1st, 2025. Teams should be prioritizing fixing release-critical bugs, before that deadline. Otherwise it's time to start planning the 2026.1 "Gazpacho" development cycle, including discussing Forum and PTG sessions content, in preparation of OpenInfra Summit Europe (Paris-Saclay, France; October 17th-19th, 2025) and virtual OpenStack PTG (October 27th-31st, 2025). Actions ------- Watch for any translation patches coming through on the stable/2025.2 branch and merge them quickly. If you discover a release-critical issue, please make sure to fix it on the master branch first, then backport the bugfix to the stable/2025.2 branch before triggering a new release. Please drop by #openstack-release with any questions or concerns about the upcoming release ! 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 Előd Illés irc: elodilles @ #openstack-release

1 0

[neutron] VPN service/router stays PENDING_CREATE - 2024.2 Dalmatian
by Shubham Yadav 19 Sep '25

19 Sep '25

Hello OpenStack Community, I'm working with OpenStack VPNaaS (using strongSwan as the backend driver) and have a question about tunnel configuration capabilities. Current Setup: OpenStack VPNaaS with strongSwan driver (StrongSwanDriver) Single VPN Service (gateway) with multiple IPSec Site Connections Each connection targets different remote peers with distinct subnets Configuration Details: VPN Service: Connected to a single router Multiple IPSec Site Connections under the same VPN Service: Connection 1: To MY office (10.10.100.0/24) via peer 68.x.y.34 Connection 2: To Rackspace (172.24.60.0/22) via peer 184.n.p.53 Shared IKE and IPSec policies across connections Local endpoint groups covering multiple subnets (192.168.0.0/24, 10.43.0.0/16) Question: Is it supported/recommended to have multiple IPSec Site Connections under a single VPN Service? I understand this creates multiple tunnels from the same OpenStack router to different remote peers. Current Issue: One of my connections shows "PENDING_CREATE" status while the other is "ACTIVE". I'm trying to determine if this is: A configuration issue on my end A limitation of having multiple tunnels per VPN service A strongSwan-specific behavior in the OpenStack context Specific Questions: Does VPNaaS officially support multiple IPSec connections per VPN Service? Are there any known limitations or best practices when using multiple tunnels? Should each remote site have its own dedicated VPN Service instead? I've checked the documentation but couldn't find clear guidance on multi-tunnel scenarios. Any insights from the community would be greatly appreciated. Environment: OpenStack version: 2024.2 Dalmatian Neutron VPNaaS with strongSwan backend Kubernetes-deployed OpenStack (OpenStack-Helm) Waiting for your reply, Thank you for your time and assistance! Best regards, Shubham

1 0

[all][elections][ptl] 2026.1 Gazpacho: PTL Election Conclusion & Results
by Sławek Kapłoński 18 Sep '25

18 Sep '25

Hi, Thank you to the electorate, to all those who voted and to all candidates who put their name forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. Now for the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Adjutant - Dale Smith (dalees) * Barbican - Mauricio Harley (mharley) * Blazar - Pierre Riteau (priteau) * Cinder - Jon Bernard (jbernard) * Cloudkitty - Rafael Weingartner () * Cyborg - Li Liu () * Designate - Omer Schwartz () * Glance - Cyril Roelandt () * Heat - Takashi Kajinami (tkajinam) * Horizon - Tatiana Ovchinnikova (tmazur) * Keystone - Artem Goncharov (gtema) * Kolla - Michal Nasiadka (mnasiadka) * Magnum - Dale Smith (dalees) * Manila - Carlos Silva (carloss) * Masakari - sam sue () * Mistral - Arnau Morin (amorin) * Neutron - Brian Haley (haleyb) * Nova - Rene Ribaud (Uggla) * Octavia - Michael Johnson (johnsom) * OpenStack Helm - Vladimir Kozhukalov (kozhukalov) * OpenStackAnsible - Dmitriy Rabotyagov (noonedeadpunk) * OpenStackSDK - Artem Goncharov (gtema) * Puppet OpenStack - Takashi Kajinami (tkajinam) * Quality Assurance - Ghanshyam Maan (gmaan) * Rally - Andrey Kurilin (andreykurilin) * Skyline - Wenxiang Wu (wu_wenxiang) * Storlets - Takashi Kajinami (tkajinam) * Sunbeam - Guillaume Boutry (gboutry) * Swift - Tim Burke (timburke) * Tacker - Yasufumi Ogawa (yasufum) * Telemetry - Matthias Runge (mrunge) * Trove - wu chunyang (wuchunyang) * Zaqar - Hao Wang (wanghao) * Zun - Hongbin Lu () Elections: * Horizon: https://civs1.civs.us/cgi-bin/results.pl?id=E_2cbcfa05fd0ec211 For remaining projects (without PTL candidates), TC will work on the appointment. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all involved in the PTL election process, Slawek Kaplonski, on behalf of the OpenStack Technical Election Officials

2 1

PTG October 2025 Team List Announcement
by Kendall Nelson 18 Sep '25

18 Sep '25

Hello Everyone! The October 2025 Project Teams List is official! Projects + Teams - OpenInfra Project Teams - Kata Containers - StarlingX - - OpenStack - Services - Blazar - Cinder - CloudKitty - Ironic - Keystone - Kolla - Magnum - Manila - Neutron - Nova - Octavia - OpenStack Horizon - OpenStack-Ansible - Sunbeam - Swift - Telemetry - Other OpenStack Teams - Eventlet Removal - openstack-i18n - Release Management - Technical Committee If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign up for time via the PTGBot[1] once it is configured to accept those reservations. As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://opendev.org/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: http://ptg.openinfra.org/ <http://ptg.openinfra.o/g>

1 0

[heat][mistral][tc] Status of ply
by Takashi Kajinami 18 Sep '25

18 Sep '25

Hi, As you might know, some of the OpenStack projects, heat and mistral, use yaql to support flexible user input. The yaql library has been tiny and stable, thanks to the ply[1] library which is the python-written implementation of lex and yacc . However, it was declared that no further release of ply is planned[2] and the author now suggests copying it into the project[3]. The old released version has been working so far, but I'm unsure if it could survive through recent drastic changes in python package tooling. Looking at the code, it seems all codes are tagged with BSD 3-clause license[3] though the repository lacks the LICENSE file. I guess that the easiest approach is to import the codes to somewhere within yaql (like yaql._ply) and use the imported codes, with a note explaining these codes are imported from ply. This follows the suggestion by the author, but I'd like to get some guidance from TC to make sure it won't break the whole license expectation. An alternative approach is to implement our own parser, though I'm not too sure if that's feasible at least from my PoV. If we want this approach, then we need actual volunteer for it who will immediately start working on it. If neither of the two options above work, we might end up removing yaql functionality completely from OpenStack. AFAIK the one in heat was added for TripleO which was already retired so the impact may be limited, while for mistral removal could have lager impact. Thank you, Takashi [1] https://github.com/dabeaz/ply [2] https://github.com/dabeaz/ply?tab=readme-ov-file#important-notice---october… [3] https://github.com/dabeaz/ply?tab=readme-ov-file#questions-and-answers [4] https://github.com/dabeaz/ply/blob/master/src/ply/lex.py#L10-L33 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

4 5

[horizon][ptg] Call for 2026.1 PTG Horizon topics
by Tatiana Ovchinnikova 18 Sep '25

18 Sep '25

Hello everyone, I have started to put together the etherpad [1] for the upcoming PTG to collect all Horizon related topics we wanted to discuss. Our usual session slots will stay, and if any other slot is needed, please feel free to suggest! [1] https://etherpad.opendev.org/p/horizon-gazpacho-ptg With kind regards, Tatiana

1 0

[all][elections][tc] 2026.1 Gazpacho Technical Committee Election Results
by Sławek Kapłoński 18 Sep '25

18 Sep '25

Hi, Please join me in congratulating the 4 newly elected members of the Technical Committe (TC). Sylvain Bauza (bauzas) Dr. Jens Harbott (frickler) Tony Breeds (tonyb) Doug Goldstein (cardoe) Full results: https://civs1.civs.us/cgi-bin/results.pl?id=E_6cede1084d4586eb Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. Slawek Kaplonski, on behalf of the OpenStack Technical Election Officials

2 1

[openstack-helm] K8s cluster broken after reboot
by Viswanath Ediga 18 Sep '25

18 Sep '25

Hello All, I am trying openstack-helm for the fist time. I could deploy the kubernetes cluster using deploy-env <https://opendev.org/openstack/openstack-helm/src/branch/master/roles/deploy…> role in a multinode test environment. But after the reboot of controlplane node, cluster seems to be brokent Kubectl is giving below error *kubectl get pods -AError from server (Forbidden): pods is forbidden: User "kubernetes-admin" cannot list resource "pods" in API group "" at the cluster scope* Any help is appreciated Regards, Kasi Viswanath

1 0

[neutron] L3 routing using VPP
by Kees Meijs | Nefos 18 Sep '25

18 Sep '25

Hi Stackers, Getting more and more enthusiast about Vector Packet Processor (VPP), I'm curious about real life experience with VPP and L3 routers using Neutron (OVS). Did someone dare to actually do this? 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.

2 2

Putting DB/WAL on SSD on
by William Muriithi 17 Sep '25

17 Sep '25

Hello, We want to use ceph as the openstack storage system and we can afford a purely SSD based storage system. So we are planning to just setup meta data on SSD and leave the data on HDD The documentation around this isn't very clear and wonder if someone can explain a bit Here is what the documentation say:- https://docs.ceph.com/en/reef/start/hardware-recommendations DB/WAL (optional) 1x SSD partion per HDD OSD 4-5x HDD OSDs per DB/WAL SATA SSD <= 10 HDD OSDss per DB/WAL NVMe SSD What does this mean? I am sorry to say, but it look a tad ambiguous to me, but suspect its obvious once one have experience. I have 6 8TB disk per system, and I want to use replication so will end up with 18 OSD I am hoping I don't need 18 SSD as we don't even have enough bays If we can add in 2 800GB SSD per hardware, how do we optimally map those 18 DW/WAL to a total of 6 SSD disks? Regards, William

4 6

[all][elections][tc][ptl][horizon] Combined PTL/TC 2026.1 cycle Election Voting Last Days
by Ian Y. Choi 16 Sep '25

16 Sep '25

We are coming down to the last hours for voting in the TC and Horizon elections. Voting ends Sep 17, 2025 23:45 UTC. Search your Gerrit preferred email address[0] for the messages with subjects like... Poll: OpenStack 2026.1 Cycle Technical Committee Election Poll Poll: OpenStack 2026.1 Cycle - Horizon PTL Election Poll That is your ballot and links you to the voting application. Please vote. If you have voted, please encourage your colleagues to vote. Candidate statements are linked to the names of all confirmed candidates: https://governance.openstack.org/election/ What to do if you don't see the email and have a commit in at least one of the official project teams' deliverable repositories[1]: * check the trash of your gerrit Preferred Email address[0], in case it went into trash or spam * find the ID of at least one commit merged to an official deliverable repo[1] over the current and previous cycles, confirm you are an Open Infrastructure Foundation Individual Member[2], and then email the election officials[3] or get in touch in the #openstack-elections channel on the Freenode IRC network. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Please vote! Thank you, [0] Sign into review.openstack.org and go to Settings > Contact Information. Look at the email listed as your Preferred Email. That is where the ballot has been sent. [1] https://opendev.org/openstack/governance/src/tag/to-be-released/reference/p… [2] https://www.openstack.org/profile/ [3] https://governance.openstack.org/election/#election-officials

1 0

Live-migration never completes memory copy
by Karl Kloppenborg 15 Sep '25

15 Sep '25

Hi Openstack Teams, We’re attempting to live-migrate instances off of a node, we continuously hit a timeout issue where memory copy doesn’t work: 2025-09-12 08:55:20.116 971204 INFO nova.virt.libvirt.driver [None req-250bc815-3323-4619-aef8-a11fdf92b27a 405874cabc5b4bf3912a5f89d54eb0d1 21eb701c2a1f48b38dab8f34c0a20902 - - default default] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] Migration running for 274 secs, memory 100% remaining (bytes processed=281505, remaining=8595255296, total=8604033024); disk 100% remaining (bytes processed=0, remaining=0, total=0). 2025-09-12 08:55:58.807 971204 INFO nova.virt.libvirt.driver [None req-250bc815-3323-4619-aef8-a11fdf92b27a 405874cabc5b4bf3912a5f89d54eb0d1 21eb701c2a1f48b38dab8f34c0a20902 - - default default] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] Migration running for 312 secs, memory 100% remaining (bytes processed=281505, remaining=8595255296, total=8604033024); disk 100% remaining (bytes processed=0, remaining=0, total=0). 2025-09-12 08:56:02.468 971204 INFO nova.compute.manager [None req-1f91a8d6-1fa7-47b2-8c3f-70925fb7a219 - - - - - -] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] During sync_power_state the instance has a pending task (migrating). Skip. 2025-09-12 08:56:37.985 971204 INFO nova.virt.libvirt.driver [None req-250bc815-3323-4619-aef8-a11fdf92b27a 405874cabc5b4bf3912a5f89d54eb0d1 21eb701c2a1f48b38dab8f34c0a20902 - - default default] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] Migration running for 352 secs, memory 100% remaining (bytes processed=281505, remaining=8595255296, total=8604033024); disk 100% remaining (bytes processed=0, remaining=0, total=0). 2025-09-12 08:57:17.377 971204 INFO nova.virt.libvirt.driver [None req-250bc815-3323-4619-aef8-a11fdf92b27a 405874cabc5b4bf3912a5f89d54eb0d1 21eb701c2a1f48b38dab8f34c0a20902 - - default default] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] Migration running for 391 secs, memory 100% remaining (bytes processed=281505, remaining=8595255296, total=8604033024); disk 100% remaining (bytes processed=0, remaining=0, total=0). 2025-09-12 08:57:56.877 971204 INFO nova.virt.libvirt.driver [None req-250bc815-3323-4619-aef8-a11fdf92b27a 405874cabc5b4bf3912a5f89d54eb0d1 21eb701c2a1f48b38dab8f34c0a20902 - - default default] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] Migration running for 431 secs, memory 100% remaining (bytes processed=281505, remaining=8595255296, total=8604033024); disk 100% remaining (bytes processed=0, remaining=0, total=0). Has anyone got insights for this issue? Your help is greatly appreciated. Thanks, Karl. Karl Kloppenborg Chief Technology Officer m: +61 437 239 565 resetdata.com<https://resetdata.com/> [cid:reset_69557fc2-1d63-4932-b5fd-93bd4f39ca7b.png] ResetData supports Mandatory Client Related Financial Disclosures – Scope 3 Emissions Reporting For more information on the phasing of these requirements for business please visit; https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-sta…<https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-sta…> This email transmission is intended only for the addressee / person responsible for delivery of the message to such person and may contain confidential or privileged information. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you, nor may you use, review, disclose, disseminate or copy any information contained in or attached to it. Whilst this email has been checked for viruses, the sender does not warrant that any attachments are free from viruses or other defects. You assume all liability for any loss, damage or other consequences which may arise from opening or using the attachments. If you received this e-mail in error please delete it and any attachments and kindly notify us by immediately sending an email to contact(a)resetdata.com.au<mailto:contact@resetdata.com.au>

4 8