- openstack-discuss - lists.openstack.org

[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 19 Sep '25

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

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

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

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

19 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