October 2025 - openstack-discuss - lists.openstack.org

[FOSDEM] Call for participation: Virtualization and Cloud infrastructure Room at FOSDEM 2026
by Piotr Kliczewski 28 Oct '25

28 Oct '25

We are excited to announce that the call for proposals is now open for the Virtualization and Cloud infrastructure devroom at the upcoming FOSDEM 2026, to be hosted on 31st of January. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We invite everyone involved in these fields to submit your proposals by 5th December 2025. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM, libvirt, shared storage, virtualized networking, cloud security, clustering and high availability, interfacing with multiple hypervisors, hyperconverged deployments and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 5th December 2025 Acceptance notifications: 10th December 2025 Final schedule announcement: 15th of December 2025 Devroom: 31st of January Submit Your Proposal During submission [1] please make sure to select Virtualization and Cloud infrastructure from the Track list. Please provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, Piotr Kliczewski and Tal Nisan In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Code of Conduct Following the release of the updated code of conduct for FOSDEM[2], we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] https://fosdem.org/submit [2] https://fosdem.org/2026/practical/conduct/

1 0

[swift][ptg] Ops Feedback Session - 29th October at 1300 UTC
by Matthew Oliver 27 Oct '25

27 Oct '25

As we've done in PTGs past, we're getting devs and ops together to talk about Swift: what's working, what isn't, and what would be most helpful to improve. We're meeting in the gazpacho swift meetpad room ( https://meetpad.opendev.org/swift-ptg-gazpacho) on Wednesday at 13:00UTC -- if you run a Swift cluster, we hope to see you there! Even if you can't make it, we'd appreciate it if you can offer some feedback on the etherpad ( https://etherpad.opendev.org/p/swift-gazpacho-ops-feedback) This has always been a highlight at every PTG for us swift devs. Have your say and help make Swift even better! Matt

1 0

[tacker][ptg] 2025.10 vPTG Planning
by Yasufumi Ogawa 27 Oct '25

27 Oct '25

Hi tacker team, As we discussed in the previous meeting, we'll have two days sessions for the vPTG. I've fixed time slots for our vPTG session[1] and setup the etherpad[2]. Please add your items on the etherpad if you have any proposal. - 29th Oct. 8am-10am UTC (5pm-7pm JST/KST) - 31th Oct. 8am-10am UTC (5pm-7pm JST/KST) [1] https://ptg.opendev.org/ptg.html [2] https://etherpad.opendev.org/p/oct2025-ptg-tacker Regards, Yasufumi

1 0

[kolla][kolla-ansible][kayobe] Bifrost usage poll
by William Szumski 27 Oct '25

27 Oct '25

Hi all, I was just trying to get an idea for the number of operators relying on the Bifrost support in Kolla-Ansible as it was recently deprecated in Kolla[1]. We are planning the next steps for its replacement, and are not sure if it is is only Kayobe users that would be affected. If you you are using Bifrost and not using Kayobe, I would appreciate if you could reply to this message. We will also be discussing Bifrost as the first topic in the Kayobe/Kolla PTG session on Wednesday 19th November at 13:00 UTC and would encourage you to come along and discuss its future. Although, nominally it is the Kayobe session, we've made the first topic on the agenda so that you easily drop out if you aren't interested in the rest of the discussion. [1] https://review.opendev.org/c/openstack/kolla-ansible/+/945501 Thanks, Will

1 1

[tc][all][security] Supporting Post-Quantum Cryptography in OpenStack code (all projects)
by Jean-Philippe Jung 27 Oct '25

27 Oct '25

Hi, I am the OpenStack Security Product Manager at Red Hat. I also support Post Quantum Cryptography in OpenStack and k8s (well, OpenShift for us), and I cover some areas of confidential computing. I see one existential risk to OpenStack in the near future: support for post-quantum cryptography (PQC) [0] Based on my latest discussion with industry experts, I expect that around 2029 (likely) or 2030 (at best), there would be powerful enough Q-Computers to break traditional cryptography. Meaning we have to prepare OpenStack to support post-quantum crypto (ML-KEM urgently, ML-DSA as soon as possible) in the upstream code. As we also need to provide time for operators/customers to implement the "fixed" code, we are in early 2028 territory to achieve sufficient PQC coverage in OpenStack upstream. This would give OpenStack users time to implement this code. Time is running out; we’re already almost in 2026! A point to keep in mind is that the initial PQC algorithms might fall short and be replaced in the future. Thus, this PQC support exercise should also be a “cryptographic agility” exercise: we should have a few libraries we know how to call, and if a new crypto algorithm comes out, it should be easy to enable it in the code. I used AI engines to have a look at the OpenStack upstream code (not all projects, but a chunk of the most commonly used), and I came back with 17 different cryptographic modules, 7 of which received no commits in over 2 years. It might be directly in the code or in pulled dependencies. The first step to solving a problem is recognizing we have one. We have a problem. I am seeking help from the TC to raise the urgency of this work across all OpenStack projects and to help me lead an effort to reduce the number of cryptographic modules used in OpenStack (my personal opinion is that there should be no more than five). Doing this may involve work in each OpenStack Project team; and I can help organize this effort. I'm seeking the following from the TC and/or project teams: Portions of this work will be isolated to specific repositories managed by a project team, while others will involve "cross-project" synchronization. What vehicles can we use to have a "call-to-action" for project teams to get someone to look into their specific projects? How can we go about community wide collaboration? I've created a document [1] that I assembled from AI analysis of part of the OpenStack code. It gives an overall view of the problem we face. Looking forward to hearing from you and collaborating upstream to improve OpenStack. Regards, Jean-Philippe (JP) Jung jjung(a)redhat.com irc: jjung [0] Quantum what? Quantum computers will break current encryption algorithms like RSA and elliptic curve cryptography using Shor's algorithm, exposing all data encrypted today. Adversaries are already harvesting encrypted data to decrypt later once quantum computers mature. OpenStack powers critical cloud infrastructure globally. Deploying post-quantum cryptography (PQC) upstream is essential because downstream distributions and deployments inherit these security foundations. Without upstream PQC integration, the entire OpenStack ecosystem remains vulnerable, putting sensitive workloads, government systems, and enterprise data at risk. The migration takes years, so implementing PQC now in the codebase is operationally necessary, not optional. [1] https://wiki.openstack.org/wiki/Post_quantum_openstack

7 12

[Neutron] Bug deputy Oct 20-27
by Jakub Libosvar 27 Oct '25

27 Oct '25

Hi, I was the bug deputy last week. There was one bug reported by Rodolfo that was set to high priority but has no assignee. Here is the summary. High ---- * [OVN] Error when using tunnelled external networks and multihoming GW routers https://bugs.launchpad.net/neutron/+bug/2129750 Needs assignee Medium ------ * unittest test_ovsdb_monitor overwrites ovs.Stream module variables https://bugs.launchpad.net/neutron/+bug/2129284 Assigned to myself Patch proposed https://review.opendev.org/c/openstack/neutron/+/964493 * VPNaaS endpoint group creating with non-unique endpoints takes a long time to fail https://bugs.launchpad.net/neutron/+bug/2129681 Assigned to Sebastian Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/964686 Low --- * [OVN] Avoid creating session less admin context in the OVN client methods https://bugs.launchpad.net/neutron/+bug/2129674 Assigned to Rodolfo Patches proposed: - https://review.opendev.org/c/openstack/neutron/+/964788 - https://review.opendev.org/c/openstack/neutron/+/964679 Incomplete ---------- * Mixed port configuration native and tagged traffic whould not pass native vlan to trunk list https://bugs.launchpad.net/neutron/+bug/2129533 Needs an assignee to follow up with the reporter

1 0

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

26 Oct '25

Hello Stackers, Welcome to the Project Teams Gathering week [1][2]. Throughout the week, there are a lot of discussions planned over multiple tracks. The OpenStack Technical Committee will be meeting virtually as well as a part of this, and the meetings are between 1600 UTC and 1800 UTC on Tuesday, October 28, 2025, and between 1600 UTC and 1800 UTC on Friday, October 31, 2025. At 1600 UTC on Tuesday, October 28, 2025, we'll be meeting with maintainers across all project teams. If you are a PTL, a DPL liaison, or a core reviewer, please join us so we can have a productive discussion on impactful cross-project work that needs to happen in the 2026.1 "Gazpacho" release. The rest of the week is action-packed as well. I'd recommend that you consult the discussion Etherpads and stay plugged in via the #openinfra-events IRC channel on OFTC. If you'd like to propose new topics on the TC's PTG etherpad [3], please add them at the end of the pad under "Parking Lot," and I'll try to get them scheduled. === Weekly Meeting === The OpenStack Technical Committee held its last weekly IRC meeting on October 21, 2025 [4]. We confirmed the inactivity of the Vitrage and Venus project teams, noting they could face retirement before the M-2 milestone of the 2026.2 release if activity doesn't resume. A significant portion of the discussion focused on the long-standing inactive status of Monasca, with most present TC members strongly favoring proceeding with its retirement. There was also a preference for keeping it inactive for another cycle due to awareness of external interest in reviving it, though this interest has yet to materialize into active contributions. The consensus was to seek more votes on the retirement patch and close this out after the Project Teams Gathering. Other updates included the Skyline project's core reviewer self-nomination [5], where the Project Team Lead (PTL) welcomed the candidate, but the TC agreed that adding the person to the core reviewer group was premature given their lack of review history. Patches in the CI to reflect Gazpacho release runtime updates have merged [6], with only a patch for Grenade struggling with CI instability. Gate health is generally stable, though the recent outages of docker.io and quay.io highlighted a need for more autonomy in container image hosting. Finally, the committee discussed topics for the upcoming Project Team Gathering (PTG), including the need to address the use of unmaintained crypto libraries across OpenStack projects. The TC will not be meeting over IRC this week in lieu of the PTG. Weekly IRC meetings will resume next on November 4, 2025. === Governance Proposals === ==== Merged ==== - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 ==== Open For Review ==== - Propose jlarriba to Telemetry PTL | https://review.opendev.org/c/openstack/governance/+/964516 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 === Upcoming Events === - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ - 2025-11-04: OpenInfra Board meeting: https://board.openinfra.org/ - 2025-11-15: Celebrating 15 years of OpenStack, Montréal - 2025-11-15: KCD + OpenInfra Days, Hangzhou: https://sessionize.com/kcd-hangzhou-and-oicd-2025/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2026.1 "Gazpacho" Release Schedule: https://releases.openstack.org/gazpacho/schedule.html [2] 2026.1 PTG Etherpads: https://ptg.opendev.org/etherpads.html [3] OpenStack TC 2026.1 PTG Etherpad: https://etherpad.opendev.org/p/oct2025-ptg-os-tc [4] TC Meeting IRC Log, Oct 21, 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-10-21-08.00.html [5] 2026.1 runtime update: https://review.opendev.org/q/hashtag:%222026-1-runtime-update%22+(status:op… [6] Skyline core contributor discussion: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…

1 0

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

26 Oct '25

Hi team, Sorry for the late notice. Due to the vPTG, I'd like cancel the IRC meeting this week. Yasufumi

1 0

Keystone+Keycloak OIDC 403 Error on openstack CLI test
by Tyler Wilson 25 Oct '25

25 Oct '25

Hello All, I'm trying to get a test idp setup going via this document: https://docs.openstack.org/kolla-ansible/latest/contributor/setup-identity-… and everything seems to be configured correctly however I am getting a 403 when I try to use the openstack CLI to test. # openstack token issue You are not authorized to perform the requested action. (HTTP 403) (Request-ID: req-be79246b-ccc1-4fbd-ba3f-fa98b9cae7ba) # openstack user show customer01 You are not authorized to perform the requested action. (HTTP 403) (Request-ID: req-4e385968-796e-44a0-8003-351188c202ba) In the keystone log I see a traceback with handle_unscoped_token and apply_mapping_filter (full output here: https://pastebin.com/xZ2qeCPW ) so maybe I'm missing something with permissions? I have the attribute mapping exactly as it is in the documentation, and im getting this when replicate the POST to userinfo with the bearer token; {"sub":"$UUID","email_verified":true,"name":"CustomerFirst CustomerLast","preferred_username":"customer01","given_name":"CustomerFirst","openstack-default-project":"customers","openstack-user-domain":"cloud.ld","family_name":"CustomerLast","email":"customer01(a)example.com"} I also checked keycloak and the user event log shows green authentications. Both domain and project exist in identity as well # openstack domain list | grep cloud.ld | $UUID | cloud.ld | True | | # openstack project list | grep customers | $UUID | customers | I'm using these exports for the client export OS_AUTH_URL=http://$KEYSTONE_IP:5000/v3 export OS_PROJECT_NAME="customers" export OS_PROJECT_DOMAIN_NAME="cloud.ld" export OS_USERNAME="customer01" export OS_PASSWORD="$USER_PASSWORD" export OS_INTERFACE=public export OS_IDENTITY_API_VERSION=3 export OS_CACERT=/etc/ssl/certs/ca-certificates.crt export OS_AUTH_TYPE=v3oidcpassword export OS_CLIENT_ID=Keystone export OS_CLIENT_SECRET=$SECRET_ALTHOUGH_DOESNT_MATTER export OS_IDENTITY_PROVIDER=cloud.ld export OS_PROTOCOL=openid export OS_ACCESS_TOKEN_ENDPOINT=https://$KEYCLOAK_IP:8443/realms/cloud.ld/protocol/openid-connect/token Is there anything I might be missing here? Thanks for any help!

3 3

[PTG][neutron] Neutron schedule
by Brian Haley 24 Oct '25

24 Oct '25

Hi Neutrinos and stackers, I have added a rough schedule to our etherpad [0] for next week's vPTG meetings, please check it and make sure the times work if you had added a topic. Based on my estimates we will only meet on Tuesday and Wednesday and not have anything on Thursday, subject to change based on how long discussions take. There are cross-projects with Ironic and Nova on Wednesday. Room info is all at [1]. See you then, -Brian [0] https://etherpad.opendev.org/p/oct2025-ptg-neutron [1] https://ptg.opendev.org/ptg.html

1 0