Sovereign by Architecture: Building AI Infrastructure for the EU AI Act
The EU AI Act takes effect August 2026. Compliance starts at the infrastructure layer. Learn why sovereign AI needs OpenStack, Kubernetes, and Atmosphere.
Insights, updates, and stories from our team
The EU AI Act takes effect August 2026. Compliance starts at the infrastructure layer. Learn why sovereign AI needs OpenStack, Kubernetes, and Atmosphere.
Learn how a lightweight keystoneauth1 plugin brings your existing browser-based MFA and SSO to the OpenStack CLI, with no changes to any client tools.
Hyperscaler AI looks fast but hides long-term lock-in and rising costs. See how OpenStack and Kubernetes deliver GPU infrastructure you actually control.
Achieve near-zero downtime during OpenStack upgrades with Atmosphere’s new "ovsinit" utility and AVX-512-optimized OVS builds for faster, more efficient networking.
Upgrading OpenStack often comes with one unavoidable risk: temporary data plane interruptions. In Atmosphere, we’ve already solved a major part of this challenge by decoupling Open vSwitch (OVS) image builds from platform upgrades — eliminating unnecessary OVS restarts.
Now, we’re taking that even further. Atmosphere introduces two key improvements that make OpenStack networking faster and more resilient than ever:
ovsinit, purpose-built to minimize data plane downtime during restarts.Atmosphere’s Open vSwitch images are now compiled with AVX-512 support, unlocking advanced CPU instructions available on modern Intel processors.
That translates directly into higher throughput and efficiency for both kernel and DPDK datapaths — improving packet processing, reducing CPU load, and delivering smoother performance under heavy workloads.
These enhancements require no configuration changes — they’re automatic for any compatible hardware, bringing performance improvements out-of-the-box.
ovsinit: Minimal Downtime, Maximum ControlEven with previous optimizations, traditional Kubernetes behavior still caused short data plane interruptions when Open vSwitch daemons restarted. Kubernetes typically stops an old pod before starting a new one — meaning if image pulls are slow or startup takes time, networking can go dark for several seconds.
ovsinit fixes that by rethinking how Open vSwitch daemons are restarted inside Kubernetes.
When used as the container entry point, ovsinit:
ovs-vswitchd or ovsdb-server) is already running.appctl exit.syscall.Exec to start the new process in-place — preserving its PID and data plane state.Combined with a rolling update strategy, the new pod is fully online before the old one exits, allowing a smooth, low-latency transition.
In testing across production-like OpenStack environments:
That’s a massive improvement over traditional restarts, where data plane loss could last several seconds or more. In most real deployments, users won’t even notice the transition.
Reliable networking is critical for OpenStack operators. With these improvements, Atmosphere delivers:
ovsinit for minimal data plane disruptionTogether, these changes redefine what it means to run OpenStack with true production resilience.
Atmosphere continues to evolve through real production experience — solving the real-world challenges of OpenStack lifecycle management, upgrades, and performance tuning.
It isn’t a wrapper around OpenStack — it is OpenStack, engineered to deliver the reliability, control, and performance that operators expect.
Choose from Atmosphere Cloud, Hosted, or On-Premise.
Simplify your cloud operations with our intuitive dashboard.
Run it yourself, tap our expert support, or opt for full remote operations.
Leverage Terraform, Ansible or APIs directly powered by OpenStack & Kubernetes