OpenStack Is Dead? Long Live Modern OpenStack!

For years, the term OpenStack has conjured images of complicated, monolithic infrastructure. While battle-tested, many viewed it as "boring" or even "legacy." But what if the solution wasn't to replace it, but to aggressively modernize it using the best tools from the cloud-native world?

That's the path forward pioneered by a lots of operators like. Their journey showcases how integrating technologies like Kubernetes, Keycloak, and the Cluster API isn't just possible—it's creating a far more robust, scalable, and manageable OpenStack distribution.

The Foundation: Cloud-Native Automation with Atmosphere

The first step in modernization was admitting that traditional configuration management tools were holding them back. After starting with manual deployments, then moving through Puppet and OpenStack Ansible, companies hit roadblocks related to scaling and consistency.

The pivotal move was migrating OpenStack's core services to run as Helm charts on Kubernetes.

This entire deployment process is now bundled into the Atmosphere project, an Ansible collection designed to be simple and fully integrated. By running OpenStack components as containers on a Kubernetes cluster, they immediately unlocked the power of the CNCF ecosystem. Now, core operations are handled by battle-tested community tools:

• Monitoring: Using the kube-prometheus stack via a standard Helm chart.
• Logging: Employing Vector and Loki for distributed log aggregation.
• External Services: Replacing complex configuration management roles with Kubernetes Operators for databases (like Percona XtraDB) and messaging queues. This allows Vex host to outsource the day-two operations of these services to the experts who built the operators.

Identity Management: Killing the Password

One of OpenStack's historical pain points has been identity and access management (IAM), often described as "hacky" for Federated authentication. The modern solution? Keycloak.

By installing Keycloak as the primary identity broker, a modern OpenStack cloud instantly gains:

1. Centralized Identity: Easy integration with corporate identity providers like Azure AD or Okta.
2. Zero-Trust Security: Centralized enforcement of multi-factor authentication (MFA) and instant revocation of access.

Crucially, they solved two major administrative issues:

• User Synchronization: A custom Keystone Keycloak backend ensures that all users and groups from the corporate directory are visible and can be assigned roles in OpenStack before they ever log in.
• CLI Access: The Keystone auth web SSO driver eliminates passwords for command-line access. When a user runs a CLI command, a browser window opens, Keycloak handles the authentication via SSO, and the CLI receives a temporary token. No passwords, no problem.

CaaS Done Right: The Cluster API Transformation

For OpenStack to be a true Infrastructure-as-a-Service (IaaS) provider, it needs to be able to reliably deploy and manage consumer Kubernetes clusters (CaaS). The legacy OpenStack Magnum project often required messy bash scripts for every new Kubernetes version.

The innovation here is the Cluster API (CAPI) driver for Magnum.

Instead of trying to reinvent the wheel, Magnum is now simply an API wrapper around CAPI, leveraging the management cluster already running OpenStack services. This small change has massive operational implications for users:

• Reliability: Kubernetes clusters deployed this way are inherently more robust.
• Advanced Features: Users automatically get auto-scaling, auto-healing, and rolling upgrades for their Kubernetes clusters, all delivered by CAPI itself.

The Horizon Line: Rust, RPC, and Next-Gen UIs

Looking ahead, Vex host is pushing the boundaries even further:

• The Rust Factor: They are exploring using Rust with Python bindings to gradually replace core OpenStack libraries. The goal is to build lightweight, single-binary containers for OpenStack services, drastically reducing complexity and external dependencies.
• RabbitMQ’s Demise: To eliminate the notorious RabbitMQ component, they are working on replacing the message bus with simple gRPC-based RPC calls. This shift would remove a constant pain point for operators and simplify the overall architecture.
• Sunrise Dashboard: Recognizing that the Horizon dashboard is showing its age, they are developing Sunrise, a Next.js application that uses server-side rendering and talks directly to the OpenStack APIs, promising a faster, more modern user experience without a complex middle layer.

Conclusion

OpenStack is far from dead—it's evolving. By aggressively adopting the best of the cloud-native ecosystem, embracing open-source integration, and solving legacy problems with modern code, operators are proving that OpenStack can be a highly scalable, secure, and genuinely exciting platform once again.