r/openstack • • May 04 '24

Dear OpenStack we need to talk

60 Upvotes

Hi! My name is Kirill. I want to talk about a topic that bothers me.

The foundational problem

Most of the problems I hear about OpenStack is that it is very bad at scales > 500+ hypervisor. But the main problem is not OpenStack itself, but the fundamental technologies that used underhood:

  • RabbitMQ turned out to be a bad solution for massive installations. The loss of messages, the eternal split brain drive OpenStack operators crazy. I have heard that some companies hire Erlang programmers to solve such problems. The community is actively developing alternatives to Mnesia called Khepi, but the transition will take a long time.

  • Multi-master MySQL / Galera cluster - all the same problems, only with the database. Neither MySQL nor PostgreSQL out of the box support horizontal scaling. This is a problem at the DNA level of these databases.

There is a similar problem with Kubernetes, which is actually limited to 10k nodes due to the fundamental technology - etcd.

If we are talking about OpenStack, then both of these problems are actually encapsulated in two small libraries:

  • oslo.db

  • oslo.messaging

An alternate universe

I know it sounds crazy, but let's imagine for a second what the OpenStack world would look like if instead of RabbitMQ, scalable solutions like GCP Pub/Sub or Amazon MQ were used, and Google Spanner or AWS Aurora were used instead of MySQL.

These technologies allow you to scale by regions, are able to process petabytes of data and billions of messages. They are reliable and work smoothly like a Swiss watch. If OpenStack installations were based on technologies capable of withstanding such loads, then there would be no problems with either ml2/ovs during full sync, or with systems like Ceilometer or Keystone. OpenStack clouds could serve 50k+ hypervisors and millions of users in one installation.

Sounds incredible, doesn't it?

However, both Google Spanner and Amazon MQ are vendor-based cloud solutions that cannot be used in reality.

The world is moving forward

But we live in 2024 and over the past 5 years there has been a "boom" of horizontally scaled technologies in opensource. Here are just some of them.

NewSQL DBMS with Horizontal scaling:

Given the scalability capabilities, these technologies can be used as 2 in 1 - both as a database and as a message broker for RPC request-response (long running operations) scenarios and for RPC Fanout. For example, YDB supports two features out of the box - a database and a message broker in the same cluster (see Topic API docs).

There have been attempts

I have already seen earlier attempts to do this in 2017 with an example

However, nothing worked out, because there are too many abstraction leaks (error specific codes) in oslo.db, which do not allow replacing MySQL even with PostgreSQL.

What should I do?

It may sound naive, but strategically, the entire OpenStack community needs to focus on just two libraries in the coming years:

  • oslo.db

  • oslo.messaging

If we remove all the abstraction leaks in the code that do not allow using alternative solutions other than MySQL+RabbitMQ, then in the future we will be able to make OpenStack truly scalable, not inferior to Big3 providers like AWS or GCP.

By 2024 we already have more choices than just MySQL Galera or PostgreSQL, then by 2027-2030 there will be even more such solutions. The world is moving forward and it's worth taking care of the future right now.

If you have any thoughts on this, I would be happy to chat in PM https://www.linkedin.com/in/kirill-bespalov/


r/openstack • • Nov 15 '22

STOP using packstack or devstack installation if you’re not a developer.

46 Upvotes

Pretty much everything is on the title, don’t use all in one solution and especially those two one when looking to « try Openstack ».

Many of you don’t get enough knowledge on Openstack but even lower linux/network/database/hypervisor/messaging queue or even just micro services concepts.

You’re basically shouting yourself in the foot and because you’ll probably fail install it as they’re not aimed to be used by beginners, you’ll end up being frustrated of Openstack.

Your first move should 100% time be manual installation step by step.

FWIW I’m an Openstack and kolla/kolla-ansible developer and professional architect on it since the first public 2010 releases and I’ve seen too much people failing to learn Openstack because they want to take the short path and focused on all in one installation.


r/openstack • • Mar 13 '26

We built a keystoneauth plugin that lets you use browser-based SSO (OpenID Connect / SAML + MFA) from the OpenStack CLI: no more application passwords

39 Upvotes

If you run an OpenStack cloud with federated identity, you probably know this pain. Horizon works great. Users sign in via OpenID Connect or SAML, complete their MFA challenge in the browser, and land on their dashboard.

The CLI doesn't. Keystone's standard auth plugins expect a username and password passed directly. That breaks the moment your IdP requires a browser redirect or a second factor prompt. The common workaround is application specific passwords, static credentials created outside the IdP's normal auth flow. They bypass MFA entirely, rarely get rotated, and create the exact kind of long lived secret that federated identity was supposed to eliminate.

We built keystoneauth-websso to fix this. It lets any OpenStack CLI tool use the same browser based WebSSO flow Horizon uses, directly from your terminal.

Why the CLI doesn't "just work" with WebSSO

Keystone's WebSSO flow was designed for Horizon. Every step assumes a browser: the IdP redirect, the MFA challenge, the cookie-based session, and the auto-submitted HTML form that carries the token back. A CLI tool driving this with raw HTTP calls would basically need a full browser engine. Not practical.

How the plugin works

Instead of replicating a browser, we just use the actual browser. The plugin opens your default browser to kick off the WebSSO flow and spins up a short-lived HTTP server on localhost to catch the token when the flow completes.

Here's the full sequence:

1.     You run an OpenStack CLI command (e.g. openstack server list) with auth_type set to v3websso.

2.     The plugin constructs the federated WebSSO URL for your configured IdP/protocol, with ?origin=http://localhost:9990/auth/websso/ so Keystone knows where to POST the token.

3.     A single-request HTTP server binds to localhost:9990 (Python's built-in http.server — no external deps, no framework). 60-second socket timeout so it won't hang if you walk away.

4.     Your default browser opens to the constructed URL.

5.     You authenticate normally in the browser. MFA, hardware tokens, conditional access — all work because auth happens where those flows were designed to run.

6.     After auth, Keystone renders its callback template. Because the origin points to localhost:9990, the form auto-submits the unscoped token to the plugin's waiting server.

7.     The server parses the POST body, extracts the token, sends back a "you can close this tab" page, and shuts down.

8.     The plugin retrieves token metadata via GET /v3/auth/tokens and proceeds with your original command.

From your perspective: terminal pauses → browser tab opens → you authenticate → tab says "close me" → terminal prints results.

It plugs into keystoneauth1 with zero client changes

The plugin registers via stevedore/setuptools entry points as v3websso. Set auth_type: v3websso in your clouds.yaml or pass --os-auth-type v3websso and keystoneauth1 discovers it automatically. No patches to python-openstackclient. No vendor forks. No monkey-patching.

Under the hood it subclasses FederationBaseAuth and only implements get_unscoped_auth_ref. Catalog lookups, endpoint discovery, scoping — all work unchanged downstream.

Token caching (you don’t get a browser tab on every command)

After a successful auth, the plugin caches the unscoped token + metadata to a JSON file in your platform's user cache directory (via platformdirs). Filename is derived from auth_url + identity_provider so different clouds don't collide.

On subsequent runs, if a cached token is still valid, the plugin uses it directly. The browser flow only happens once per token lifetime (typically a few hours). Everything else is instant.

Security notes

·      Callback server only binds to localhost. Accepts one request, then shuts down.

·      60-second socket timeout — no indefinite blocking.

·      Cache files written with 0600 permissions.

·      The plugin never sees your IdP password. Auth happens entirely in the browser. The only artifact captured is the Keystone token (same thing Horizon gets).

What you need to set up

  • One Keystone config change: add http://localhost:9990/auth/websso/ to trusted_dashboard in keystone.conf.

  • Two runtime deps beyond keystoneauth1: multipart (POST body parsing) and platformdirs (cache path resolution).

  • The whole thing is ~300 lines of Python.

No changes to any CLI client.

TL;DR
If you've invested in federated identity for your OpenStack cloud, this plugin closes the last gap. Your users authenticate the same way whether they're in Horizon or the terminal. Same access policies, same session controls, same audit logs. No application passwords. No MFA exceptions for CLI workflows.

Apache 2.0 — github.com/vexxhost/keystoneauth-websso

If you're running into this problem or have questions about setting it up, drop a comment or reach out to us at VEXXHOST. We'd love to hear how you're handling CLI auth with federated identity.


r/openstack • • Apr 25 '25

First HomeLab OpenStack Deployment Was A Success!

Post image
39 Upvotes

Its not the most production ready thing ever, but it does work!

I deployed it with Kolla-Ansible's all-in-one configuration in a proxmox (using nested virtualization), im going to keep experimenting with it and gradually start getting it into a more "production" ready setup as time goes on

This is something i've wanted to do for a while so im very very glad i was able to get it running!


r/openstack • • Oct 08 '26

How to make Openstack Horizon fly

Thumbnail
thinknerd.de
38 Upvotes

We made a cache patch for horizon that makes horizon properly cache.

EDIT: 2026.1 patch and image also added to blogpost. All patches have also been commited to upstream. Lets see


r/openstack • • Nov 24 '25

Announcing Atmosphere 7.0.0 (OpenStack 2025.2 “Flamingo”): Feature Upgrades, Performance Optimizations, and Security Enhancements

34 Upvotes

We are pleased to announce the release of Atmosphere 7.0.0 OpenStack Flamingo Edition! This update brings exciting new features, including Rocky Linux & AlmaLinux 9 support, Amphora V2 for improved load balancer resiliency, enhanced monitoring dashboards, advanced BGP routing with OVN, and much more. 

Let’s dive into the major changes introduced in this release:  

  • Expanded OS Support: Now fully compatible with Rocky Linux 9 and AlmaLinux 9 for Ceph and Kubernetes collections. 

  • Amphora V2 Enabled by Default: Improved load balancer resiliency ensures seamless provisioning and eliminates resources stuck in pending states. 

  • Enhanced Monitoring and Alerts: New dashboards for Ceph, CoreDNS, and node exporters, along with refined alerts for Octavia load balancers and system performance. 

  • Advanced Networking with BGP: Support for FRR BGP routing with OVN, offering greater flexibility in networking configurations. 

  • Streamlined Backup Operations: Percona backups now use default backup images, reducing manual configurations and streamlining database operations. 

  • Performance Upgrades:  AVX-512 optimized Open vSwitch builds for improved hardware acceleration. Pure Storage optimizations for better iSCSI LUN performance. Major Kubernetes, Magnum, and OpenStack upgrades for stability, features, and bug fixes. 

  • Security Enhancements:  Multi-factor authentication via Keycloak. TLS 1.3 for libvirt APIs. Updated nginx ingress controller addressing key CVEs. 

  • Upgraded Base Images: OpenStack containers now run on Ubuntu 24.04 and Python 3.12 for enhanced security and better performance. 

These new features and optimizations are designed to deliver unparalleled performance, enhanced reliability, and streamlined operations, ensuring a robust and efficient cloud experience for all users. 

For a more in-depth look at these updates, we encourage you to explore this blog post and review the documentation. 

As the cloud landscape advances, it's essential to keep pace with these changes. We encourage our users to follow the progress of Atmosphere to leverage the full potential of these updates. 

If you require support or are interested in trying Atmosphere, reach out to us. Our team is prepared to assist you in harnessing the power of these new features and ensuring that your cloud infrastructure remains at the forefront of innovation and reliability.  

Keep an eye out for future developments as we continue to support and advance your experience with Atmosphere. 


r/openstack • • Jul 31 '24

Moving from VMWare to Openstack

34 Upvotes

For a long list of reasons my company is switching from VMWare to Openstack and we have a meeting with contractors today to discuss the path forward. I have many years experience with VMWare and 0 experience with Openstack.

What would be some good questions to ask? My 2 main concerns are hardware load balancing and a good migration path (5,000 vms). From my reading Openstack appears to have a vmotion equivalent but I haven't found many good details on it.

EDIT: Thank you to everyone who responded. There's a ton of helpful information here and it will take me some time to go through it all. We've decided to go with Platform9. Seems like they will make managing and maintaining OpenStack easier than without. I'm anticipating to start the buildout next month after security does all of their reviews to make things as difficult as possible :)


r/openstack • • Dec 19 '25

GPU P2P is disabled by default in OpenStack PCIe passthrough

31 Upvotes

Hi, it's Minh from Menlo Research.

We run GPU workloads on OpenStack with PCIe passthrough. Recently we found that GPU-to-GPU peer-to-peer communication was completely disabled in our VMs.

Running nvidia-smi topo -p2p r inside a VM showed every GPU pair as NS (Not Supported). All inter-GPU transfers were going through system RAM. We measured the bandwidth on bare metal with P2P disabled versus enabled. Without P2P, bidirectional bandwidth was around 43 GB/s. With P2P, 102 GB/s. That's a 137% difference.

QEMU has a parameter called x-nv-gpudirect-clique that enables P2P between passthrough GPUs. GPUs with the same clique ID can communicate directly. The syntax looks like this:

-device vfio-pci,host=05:00.0,x-nv-gpudirect-clique=0

The problem is getting this into OpenStack-managed VMs. We tried modifying libvirt domain XML directly with <qemu:commandline> arguments. Libvirt sanitizes custom parameters and often removes them. Even if you get it working, Nova regenerates the entire domain XML from its templates on every VM launch. Manual edits don't persist.

The solution we used is to intercept QEMU at the binary level. The call chain goes OpenStack to Nova to libvirt to QEMU. At the end, something executes qemu-system-x86_64 with all the arguments. We replaced that binary with a wrapper script.

The wrapper catches all arguments from libvirt, scans for vfio-pci devices, injects the clique parameter based on a PCIe-to-clique mapping, and then calls the real QEMU binary.

sudo mv /usr/bin/qemu-system-x86_64 /usr/bin/qemu-system-x86_64.real

sudo cp qemu-wrapper.sh /usr/bin/qemu-system-x86_64

sudo chmod +x /usr/bin/qemu-system-x86_64

sudo systemctl restart libvirtd nova-compute

The wrapper maintains a mapping of PCIe addresses to clique IDs. You build this by running nvidia-smi topo -p2p r on the host. GPUs showing OK for P2P should share a clique ID. GPUs showing NS need different cliques or shouldn't use P2P at all.

After deploying, nvidia-smi topo -p2p r inside VMs shows all OK. We're getting about 75-85% of bare metal bandwidth, which matches expectations for virtualized GPU workloads.

A few operational considerations. First, run nvidia-smi topo -m on the host to understand your PCIe topology before setting up cliques. GPUs on the same switch (PIX) work best. GPUs on different NUMA nodes (SYS) may not support P2P well.

Second, the wrapper gets overwritten when QEMU packages update. We added it to Ansible and set up alerts for qemu-system package changes. This is the main maintenance overhead.

Third, you need to enable logging during initial deployment to verify the wrapper is actually modifying the right devices. Set QEMU_P2P_WRAPPER_LOG=1 and check /var/log/qemu-p2p-wrapper.log.

We wrote this up in on our blog: https://menlo.ai/blog/gpudirect-p2p-openstack


r/openstack • • Dec 27 '25

Working OVS/OVN Prometheus Exporters for OpenStack with Kolla-Ansible Support

29 Upvotes

Hey folks,

I wanted to share some work I've been doing to improve OVS/OVN monitoring in my OpenStack environment. Running OpenStack 2025.1 with kolla-ansible, I found myself lacking visibility into the OVN/OVS layer, which became frustrating when troubleshooting networking issues.

Kolla-ansible doesn't provide built-in exporters for OVS/OVN metrics, so I went looking for solutions. I found @greenpau's original OVS/OVN exporters and ovsdb library, which were excellent tools but were archived about a year ago. @Liquescent-Development picked them up and made some improvements about 3 months ago, adding features like Grafana dashboards. However, they still needed patches to work properly with modern OVS versions (3.x+).

Updated Repos

I forked three repositories:

1. ovsdb library - https://github.com/lucadelmonte/ovsdb

  • Fixed compatibility issues with OVS 3.x+ where sometimes version info isn't stored in the DB anymore

  • Added intelligent version detection (queries ovs-appctl, schema, and /etc/os-release)

2. OVS Exporter - https://github.com/lucadelmonte/ovs_exporter

  • Created Kolla-Ansible integration guides and configs

  • Enhanced Grafana dashboards

  • Included Prometheus templated scrape configs and alert rules

3. OVN Exporter - https://github.com/lucadelmonte/ovn_exporter

  • Same ovsdb library integration

  • Kolla-Ansible compatible deployment configs

  • Enhanced Grafana dashboards

  • Included Prometheus templated scrape configs and alert rules

Installation

Each repo has a README with installation instructions. For kolla-ansible deployments, there are specific configuration files and systemd overrides in the assets/kolla-ansible/ directory that make integration hopefully straightforward.

I've also created an ansible role for deployment using kolla inventory/vars, I guess I could also share that if someone would like to have it.

Feedback Welcome

I've just deployed this to staging a couple of days ago, so I'm sure there are edge cases I haven't encountered yet. If you run into issues or have suggestions for improvements, please open a PR on any of the repos. I'm definitely not an expert on all OVS/OVN internals, so corrections and enhancements are very welcome!


Original upstream repos (credit where it's due):


r/openstack • • Jan 23 '24

Awesome lists about OpenStack

29 Upvotes

Hi everyone, check out my curated Awesome lists about OpenStack

It's like a handy guidebook with resources and tools to help you understand OpenStack better.

Feel free to give it a star, share, or contribute. Let's make this a go-to spot for all things OpenStack!

https://github.com/DragomirAlin/awesome-openstack-cloud


r/openstack • • Jul 19 '15

Goodbye, OpenStack (not my article) interesting perspective

Thumbnail gigofham.com
29 Upvotes

r/openstack • • Aug 09 '26

[Tool] I built an Oh My Zsh plugin to manage multiple OpenStack clouds, auto-venv, and fuzzy-find SSH / VNC consoles

28 Upvotes

If you work with more than one OpenStack cloud/project day to day, you know the drill: source ~/clouds/prod-openrc.sh, remember which venv has the right client version, openstack server list, ssh into whatever floating IP you copy-pasted from the output... I got tired of it and wrote a Zsh plugin to automate the parts I do 20x a day.

What it does:

- openv [cloud] — pick a cloud from clouds.yaml via fzf (with a live preview card showing auth URL / project / region, no secrets shown), activates the matching Python venv, and exports OS_CLOUD

- ops-ssh [user] [-i keyfile] [--insecure] — fuzzy-pick a server and SSH straight into its floating IP (prioritizes public IPs over private ones automatically); --insecure skips host-key checks, handy since floating IPs get recycled between instances constantly

- ops-console — fuzzy-pick a server and pop its Horizon VNC console URL open in your browser

- opcheck — quick openstack token issue sanity check so you find out your token expired before you're 3 commands deep into something

- opwho / opls — status of what's active / table of everything in clouds.yaml

- ophelp (or openv --help) — cheatsheet of everything below, printed in your terminal

- ~25 short aliases for the commands I run constantly (ops, opnet, opvol, opsec, opfl, oplb, etc. — full list in the README)

It's a normal Oh My Zsh plugin, MIT licensed, no telemetry, no dependencies beyond python3 + PyYAML + fzf (the plugin checks for these on load and warns if something's missing).▎

Install:

git clone https://github.com/whoami96/openstack-zsh-plugin.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/openstack

# add "openstack" to plugins=(...) in ~/.zshrc, then reload

Repo: https://github.com/whoami96/openstack-zsh-plugin

It's a fairly small, personal-scale tool — built it for my own workflow managing a handful of clouds — but figured it might save someone else the same repetitive typing. Happy to hear feedback or take PRs if it's missing something obvious for your workflow.


r/openstack • • Apr 21 '26

We just launched an OpenStack Jobs Board — hiring or job hunting, this is for you!

27 Upvotes

Hey everyone,

If you’re working in or around OpenStack, you’ve probably noticed the same thing we have: great talent and great opportunities, but they’re scattered everywhere.

So we launched a dedicated OpenStack Jobs Board (https://gitjobs.dev/?foundation=openinfra) to bring it all into one place.

Hiring?
Post your open roles and reach people who actually know OpenStack, from operators and platform engineers to contributors and architects. Use your Linux Foundation ID (LFID) to log in, then just tag “OpenStack” as one of the Skills and OpenInfra as the Project when placing your job. If you don’t have an LFID, it’s easy and free to create. 

Looking for a job?
Browse roles that specifically value OpenStack experience (not buried under generic “cloud” listings).

The goal is simple: make it easier for this community to find each other so we can continue building the future of open infrastructure together. 

We’re hoping this becomes a go-to resource for:

  • OpenStack operators & admins

  • Platform engineers

  • Contributors/devs

  • Anyone building or running open infrastructure

If you’re hiring, drop your roles in. If you’re job hunting (or just curious), please take a look.

We would also love feedback from this community! What would make this actually useful for you?


r/openstack • • Aug 20 '24

VEXXHOST Introduces Migratekit: Enabling Near-Zero Downtime in VMware to OpenStack Migrations

27 Upvotes

We are pleased to introduce Migratekit (github link: here) 

Developed as part of the broader open-source ecosystem by VEXXHOST, Migratekit is an open-source command-line interface (CLI) tool with a singular focus: expediting and streamlining the migration of virtual machines from VMware to OpenStack environments with minimal service interruption. 

The tool is the result of a concerted effort to facilitate a migration process where the majority of data transfer occurs without impinging on the virtual machine's operational uptime, thereby reducing the downtime to the narrowest margin during the final transition phase. 

Migratekit operates through a two-phase approach: 

Phase 1: Online Data Movement 

During this phase, Migratekit performs the bulk of the data transfer while the virtual machines remain active. This approach is crucial for maintaining operations and reducing the amount of downtime required for the migration. 

Phase 2: Cutover Completion 

The final phase involves a brief planned downtime to finalize the migration. This stage includes the synchronization of any remaining data and the transition of VM instances to the OpenStack environment. 

While it works with any OpenStack deployment, it has been extensively tested and validated against Atmosphere, our open-source cloud infrastructure platform. 

Migratekit's methodology is developed from a need for continuous service availability and the complexities of infrastructure migrations. It offers a practical solution for minimizing the impact on services during the shift to a new cloud platform.


r/openstack • • Oct 09 '19

SUSE drops OpenStack Cloud

Thumbnail
zdnet.com
26 Upvotes

r/openstack • • Oct 15 '26

Seeking an OpenStack expert technical author

25 Upvotes

Hello. I hope it's OK to post this here, let me know if not and I will remove it (I did ask the moderation team a week or so ago but didn't get any answer).

For some time, I have been looking for a technical author with real expertise in OpenStack, without much success.

If you can do OpenStack and documentation I'd love to talk to you. It's a full-time, permanent, globally remote role. You can live and work in almost any country, but it needs to be in EMEA or AMER time zones.

It's in my team at Canonical (the company behind Ubuntu). Here's more information about the technical author role in general, but I do suggest dropping me a line about this before diving into an application as I can give you some useful pointers and guidance.


r/openstack • • Jul 15 '26

CERN Openstack Talks and Resources

25 Upvotes

I notice they have great scale, and many public resources

CERN's private cloud runs in two data centers (Geneva and Budapest) with a total of about 5,000 servers (about 130,000 cores). By summer 2016, we expect to grow to about 200,000 cores. For block storage, CERN runs Ceph with a capacity of 3.5PB.

https://opensource.com/business/15/10/openstack-summit-interview-belmiro-moreira-cern

https://techblog.web.cern.ch/techblog/

https://videos.cern.ch/search?page=1&size=21&q=openstack#

https://cds.cern.ch/search?ln=en&sc=1&p=openstack&action_search=Search&op1=a&m1=a&p1=&f1=&c=Articles+%26+Preprints&c=Books+%26+Proceedings&c=Presentations+%26+Talks&c=Periodicals+%26+Progress+Reports&c=Multimedia+%26+Outreach&c=International+Collaborations


r/openstack • • Feb 20 '26

Operational challenges with OpenStack + Ceph + Kubernetes in production?

Post image
25 Upvotes

Hi,

I’m doing some research on operational challenges faced by teams running OpenStack, Ceph, and Kubernetes in production (private cloud / on-prem environments).

Would really appreciate insights from people managing these stacks at scale.

Some areas I’m trying to understand:

  • What typically increases MTTR during incidents?

  • How do you correlate issues between compute (OpenStack), storage (Ceph), and Kubernetes?

  • Do you rely on multiple monitoring tools? If yes, where are the gaps?

  • How do you manage governance and RBAC across infra and platform layers?

  • Is there a structured approval workflow before executing infra-level actions?

  • How are alerts handled today — email, Slack, ticketing system?

  • Do you maintain proper audit trails for infra changes?

  • Any challenges operating in air-gapped environments?

Not promoting anything — just trying to understand real operational pain points and what’s currently missing.

Would be helpful to hear what works and what doesn’t.


r/openstack • • Oct 30 '22

Is openstack still the best open source option?

25 Upvotes

I am planning on building a private cloud. Is openstack still the most relevant or is it dying off? Are there better options? My needs include creating VMs, networking to access VM outside of network, image creation, snapshot creation, and block storage. Possibly also usage tracking, but not absolutely necessary. I dont need a full on public cloud set up, it is just for my own small operation. For this use case, would openstack be the best option long term or is there a better alternative? I am currently using a public cloud but it isnt a good fit.


r/openstack • • Oct 14 '26

OpenInfra Live recap: what's new in OpenStack 2026.2 Hibiscus (TC, VMT, Nova, Neutron, Ironic, Manila, Watcher, Freezer)

24 Upvotes

The OpenInfra Foundation did an OpenInfra Live episode on the 2026.2 Hibiscus release, with PTLs and leads from a bunch of projects.
It's 90 minutes long, so here's my summary of the main points for anyone who doesn't have time to watch it all.

Video: https://www.youtube.com/watch?v=37p9C0n0LLw

Technical Committee

  • 16 years and 34 releases in. Contributors are up 21% and changes up 28% vs the previous release, mostly driven by AI infra, confidential computing and digital sovereignty use cases

  • Core reviewers now count as active contributors and get voting rights for TC and project team elections

  • New Contributor Experience WG (onboarding + community health), new PQC (post-quantum crypto) pop-up team, new RISC-V SIG, and an agentic workflows repo under the TACT SIG for sharing AI-assisted dev practices

  • Bug trackers audited for embargoed reports, core security teams reformed per project, PTLs encouraged to formally delegate release/security roles

  • Retired: Vitrage, Venus, cinderlib. Onboarded: Lustre (DevStack plugin)

  • Ongoing goals for Indri: secure RBAC defaults, eventlet removal, rootwrap to oslo.privsep migration. Proposed new goals: security reporting instructions in every repo and a PQC timeline

  • Main concern going forward: the contributor base is growing, but there aren't enough new maintainers

Vulnerability Management Team

  • 42 OSSAs and 13 OSSNs so far in 2026. No year since 2016 (the previous record year) had more than 8 OSSAs or 3 OSSNs

  • Part of an industry-wide flood: the oss-security list is already at ~2,500 emails vs ~1,168 for all of last year

  • About 150 security bugs this year, over half led to an advisory or note, and ~5-10% were "AI slop" that still took hours to triage

  • CVE assignment is slower due to MITRE backlog, so some OSSAs ship before a CVE exists. Security notes moved out of the wiki into YAML files in the docs repo

  • The best reports come from operators running real clouds. You don't need a polished write-up, just report what you're seeing

Nova

  • Confidential computing: AMD SEV-SNP and Intel TDX support, including attestation tokens

  • vGPU (mdev) lifecycle can now be managed in Cyborg instead of local nova.conf. Variant driver support (newer GPUs) is planned next cycle

  • Unpin/repin an instance's AZ without recreating it. Instances with Manila shares attached can now be migrated/resized

  • Native threading by default (except the noVNC/SPICE console proxies), new thread pool tuning options, and graceful shutdown part 2

  • Next cycle: cross-cell live migration, graceful shutdown part 3

Neutron

  • EVPN Type 5 routes (advertise whole CIDRs, multi-DC project networks) and BGP route leaking (advertise project CIDRs into the fabric without floating IPs/NAT)

  • Indirect floating IPs: FIP API now accepts router_id, for multi-router transit and gateway VM setups

  • PVLAN support (promiscuous / community / isolated ports) and a configurable stateless default security group, handy for DPDK

  • Closed more ML2/OVN gaps: L3 scheduler API to view/control gateway chassis, and multi-segment routed provider networks

  • L3 HA keepalived state change monitor rewritten from a Python daemon into a POSIX shell script: 15x less memory, just restart the agent

  • 150+ bugs fixed, ~100 stale bugs closed, 7 of 8 approved RFEs done

Ironic

  • Old legacy hardware drivers retired, focus moves to Redfish. Firmware ops move to a dedicated firmware interface

  • TLS 1.3 by default (still configurable for older BMCs)

  • RBAC to block specific steps. Runbooks can be matched to node traits, and runbooks with disable_ramdisk let you do firmware updates without booting IPA

  • Graphical console (noVNC) improvements

  • After a security audit by the Metal3 security team, defaults are safer: IPA no longer installs the bootloader, container registry TLS is verified, file URLs are filtered, oversized/nested JSON is rejected, and IPMI raw commands are disabled

  • Nova compute ironic driver starts up and performs faster

Manila

  • Native threading is now the default (eventlet still available via config). Share migration APIs graduated from experimental

  • Async revert-to-snapshot, and mountable snapshots can inherit the parent share's access rules

  • New Lustre and Weka drivers for AI/ML/HPC, with DDN EXAScaler coming

  • TLS cert validation for the Pure FlashBlade, Hitachi HSP and NetApp ONTAP drivers. OSSN-0103 fixed resource lock queries

  • Next cycle: share server replication, privsep migration, native OpenStack client support, NFS QoS, erasure-coded pools

Watcher

  • Eventlet deprecated, native threads by default. Cinder/Keystone/Glance now go through openstacksdk

  • Better locking in the cluster data model made audits ~6x faster

  • New delete and shelve instance actions, default parameters on audit templates. VM workload consolidation now checks allocation-based capacity

  • Next cycle: audit pipelines (one optimized action plan from several audits), a workload preemption strategy, and cross-AZ zone migration

Freezer

  • Central scheduler can now run on the control plane with service credentials, in HA with coordination, using trusts and Cinder backup to do the work. Effectively scheduled Backup-as-a-Service on top of cinder-backup

  • V1 API finally removed, resources are now project-owned, and secure RBAC policies are in place

  • openstack backup CLI plugin and a reworked Horizon plugin

  • Planning a V3 API (pagination, microversions, no Elasticsearch-style queries), and they're looking for input

TL;DR

Hibiscus is about confidential computing (SEV-SNP/TDX), AI/HPC readiness (vGPU via Cyborg, Lustre/Weka in Manila, bare metal firmware ops), safer defaults everywhere, and efficiency at scale. Also, the security report volume is no joke


r/openstack • • Oct 15 '25

Substation - New openstack tui

24 Upvotes

Found this on linkedin:

Substation is a comprehensive terminal user interface for OpenStack that provides operators with powerful, efficient, and intuitive cloud infrastructure management capabilities.

https://substation.cloud/


r/openstack • • Nov 12 '24

Kolla-ansible 2024.2

24 Upvotes

If someone interested

Kolla-ansible from my side is easiest and flexible way to deploy Openstack. Guys who are managing project are awesome https://launchpad.net/~kolla-drivers/+members#active

Official Announcement: https://lists.openstack.org/archives/list/[email protected]/thread/N5CDPAUTL57OBBISJUXGJGMGYJEEOCYV/

Release notes : https://docs.openstack.org/releasenotes/kolla-ansible/2024.2.html

Please report issues through:

https://bugs.launchpad.net/kolla-ansible/+bugs

Upgrade procedure https://docs.openstack.org/kolla-ansible/2024.2/user/operating-kolla.html


r/openstack • • Jul 12 '25

Are You Enjoying OpenStack?

23 Upvotes

To people using OpenStack how has it gone? I’ve been ramping on it for work and have mixed feelings. If an alternative existed would you consider it?


r/openstack • • Jun 08 '22

OpenStack Networking with OVN

23 Upvotes

Hi r/openstack, I made a couple of videos covering networking with OVN.

I tried to show the relationship between Neutron and OVN objects and how they come together. I also demonstrated a couple of tools that you can use to debug packet flows and network issues. Namely, ovs-appctl ofproto/trace, ovs-tcpundump and ovn-trace.

Hopefully some folks here will find them interesting and informative. Happy to take feedback and suggestions for anything else you would like to see related to OVN.

https://youtu.be/QpyHrjFfakk
https://youtu.be/DnqFFRVnMoc