The latest OpenStack SLURP release is out. 500+ contributors from 100 organizations and nearly 9,000 changes. For organizations currently weighing their migration options, the timing couldn’t be more relevant. Gazpacho addresses many of the key requirements for production migrations and, as an SLURP release, supports direct upgrades from the previous SLURP — no intermediate steps required.
Migration just got faster
The single most impressive feature in Gazpacho is parallel live migrations in Nova. Previously, live migration processed memory transfers sequentially. Now multiple connections run simultaneously, which means moving large workloads across hosts or zones is significantly faster.
The OpenStack community didn’t add this by accident. It was explicitly flagged as high demand from operators seeking a VMware alternative. That context matters, and it’s built for the organizations that are actively planning migrations right now.
Alongside this, live migration with vTPM support means security-sensitive workloads — the kind that previously had to be shut down, migrated cold, and restarted — can now move live. For customers in regulated industries, this removes one of the last remaining arguments for staying on legacy platforms.
Bare metal provisioning became less manual
If you’re running hybrid environments — virtual machines alongside physical servers — bare metal has historically been where operational complexity accumulates. Ironic in Gazpacho addresses this directly.
Auto-detection of deployment interfaces removes the need to manually specify deployment methods per node. Automatic protocol detection for NFS and CIFS over Redfish simplifies boot configuration. Trait-based port scheduling automates network placement based on actual infrastructure attributes rather than manual assignment.
For our customers managing dozens or hundreds of physical nodes, this is a meaningful reduction in provisioning overhead.
Networking at enterprise scale
The Neutron OVN driver received substantial updates in Gazpacho. BGP support, North-South routing for external ports, and allowed address pairs with virtual MAC addresses are all now available.
In practice, this matters for customers with complex network topologies — multi-tenant environments, hybrid connectivity, and workloads that span private and public infrastructure. These were historically the scenarios where OpenStack required workarounds or additional tooling. Gazpacho closes those gaps natively.
Storage and I/O performance
Two changes here that will be felt rather than just read about. Default IOThread per QEMU instance offloads disk I/O processing from vCPUs — in high-density environments, this translates directly to more consistent performance under load. The asynchronous volume attach API reduces latency by decoupling long-running storage operations from API response time, which matters for customers running automated provisioning at scale.
Neither of these is headline-grabbing. Both will show up in performance benchmarks and operational metrics.
Security tooling that fits enterprise environments
OpenStack-Ansible now integrates with OpenBao — the open source fork of HashiCorp Vault — for PKI management. For customers who already run Vault-based certificate infrastructure, this means OpenStack stops being the exception that requires separate tooling and becomes part of a unified security posture.
This matters especially in regulated environments where certificate lifecycle management is audited. Aligning OpenStack’s PKI with enterprise-standard tooling removes a compliance friction point that has come up repeatedly in customer conversations.
What this means if you’re evaluating a migration
The conversation around VMware alternatives has shifted over the past 18 months. It’s no longer about whether open source infrastructure is technically capable — it’s about whether your team can operate it confidently and whether the upgrade path is predictable.
