With support for vSphere 8 ending on October 11, 2027, many VMware customers are evaluating their path to VMware Cloud Foundation (VCF) 9.1.
What many discover is that VCF 9.1 is not simply a version upgrade. It often requires significant changes to infrastructure, storage, networking, hardware, and operations. For organizations that adopted VMware because it simplified infrastructure management, the move to VCF 9.1 can feel like a step in the opposite direction.
For organizations looking to modernize while maintaining flexibility and control, OpenNebula provides a compelling alternative.
VCF 9.1 Requires a Significantly Larger Management Footprint
These services run as dedicated appliances and form part of a separate management domain that must be deployed, maintained, monitored, upgraded, and secured throughout the platform lifecycle.
OpenNebula takes a different approach. A typical OpenNebula deployment relies on a lightweight management layer centered around the OpenNebula Frontend, providing virtualization, networking, storage, Kubernetes orchestration, monitoring, automation, and user management through a single control plane.
A minimal OpenNebula Frontend requires only 16 GB of RAM, allowing organizations to dedicate significantly more infrastructure capacity to business applications rather than cloud management services.
VCF 9.1 Pushes Customers toward a Specific Storage Architecture
Storage is another area where many VMware customers face difficult decisions. vSAN is the default storage platform integrated into VMware Cloud Foundation and is central to VMware’s validated reference architectures and deployment models. At the same time, VMware has announced the deprecation of vVols, with support scheduled for removal in a future release.
Organizations that have invested heavily in SAN, NAS, iSCSI, Fibre Channel, or specialized storage platforms may therefore need to reassess long-term storage strategies as part of their migration planning.
OpenNebula allows organizations to continue leveraging existing investments in:
- iSCSI storage
- Fibre Channel SANs
- NFS-based storage
- Ceph deployments
- Local storage
- Enterprise storage arrays
Instead of forcing infrastructure to conform to a prescribed architecture, OpenNebula adapts to the storage strategy that best fits business and operational requirements.
VCF 9.1 Makes NSX Part of the Journey
For many VMware environments, networking modernization is one of the most significant aspects of a VCF migration. VMware Cloud Foundation incorporates NSX as a core platform component and embeds it deeply within the management and workload domain architecture. Organizations moving to VCF should therefore evaluate the operational, architectural, and skills implications of adopting NSX as part of their cloud modernization strategy.
For some teams, this introduces additional operational complexity, new management workflows, and additional training requirements compared with traditional VMware networking deployments.
OpenNebula offers a more flexible networking model. Organizations can deploy simple VLAN-based networks for traditional virtualization environments or implement advanced networking capabilities using VXLAN overlays and Open vSwitch when required. This allows infrastructure teams to deploy the level of networking sophistication they actually need rather than adopting a one-size-fits-all architecture.
VCF 9.1 may accelerate hardware refresh cycles
Hardware compatibility is becoming another important consideration. Broadcom documentation for VCF/ESX 9.x identifies CPU series, systems, and servers that are deprecated or reaching end-of-life status, and states that some deprecated CPU support will be discontinued in a future ESX release. For organizations running stable but older infrastructure, this can bring hardware refresh planning forward as part of a VCF migration assessment.
OpenNebula provides greater flexibility in infrastructure planning by supporting a broad range of x86 platforms and Linux distributions. This allows organizations to maximize the value of existing infrastructure investments while modernizing at a pace aligned with business priorities rather than platform requirements.
VCF 9.1 Introduces Additional Operational Complexity
The migration itself can be challenging. Organizations may need to:
- Redesign storage architectures
- Migrate networking to NSX
- Disable Enhanced Linked Mode during upgrades
- Upgrade vCenter to irreversible hardware versions
- Rework identity integration and authentication mechanisms
- Deploy and manage multiple new platform components
Each of these activities introduces project risk, operational overhead, and additional costs. OpenNebula provides a simpler operational model while still delivering enterprise cloud capabilities, including:
- Multi-tenancy
- Self-service provisioning
- Role-based access control
- Monitoring and reporting
- Automation and orchestration
- Kubernetes integration
- Hybrid and edge cloud support
The result is a cloud platform that remains powerful without becoming unnecessarily complex.
An Alternative Path Forward
For organizations evaluating VCF 9.1, the key question is no longer simply how to upgrade VMware. The real question is whether the benefits of VCF justify the additional infrastructure requirements, architectural changes, operational complexity, and subscription costs.
OpenNebula offers another path: a modern private cloud platform that allows organizations to maintain control over their infrastructure, continue leveraging existing storage and networking investments, and reduce management overhead while preserving enterprise-grade capabilities.
As 2027 approaches, VMware customers should evaluate not only their next upgrade, but also whether they want to continue following an increasingly complex infrastructure roadmap—or adopt a platform designed around simplicity, flexibility, and freedom of choice.
If you’re assessing your options for life after vSphere 8, OpenNebula provides a practical and cost-effective alternative to the VCF 9.1 migration journey.
0 Comments