Update: Please have a look at the VMware Cloud Foundation 5.1 Technical Overview.
What is VMware Cloud Foundation (VCF)?
VMware Cloud Foundation is a multi-cloud platform that provides a full-stack hyperconverged infrastructure (HCI) that is made for modernizing data centers and deploying modern container-based applications. VCF is based on different components like vSphere (compute), vSAN (storage), NSX (networking), and some parts of the Aria Suite (formerly vRealize Suite). The idea of VCF follows a standardized, automated, and validated approach that simplifies the management of all the needed software-defined infrastructure resources.
This stack provides customers with consistent infrastructure and operations in a cloud operating model that can be deployed on-premises, at the edge, or in the public cloud.
What software is being delivered in VMware Cloud Foundation?
The BoM (bill of materials) is changing with each VCF release. With VCF 5.0 the following components and software versions are included:
- VMware SDDC Manager 5.0
- vSphere 8.0 Update 1a
- vCenter Server 8.0 Update 1a
- vSAN 8.0 Update 1
- NSX-T 4.1
- VMware Aria
Note: Only one vCenter Server license is required for all vCenter Servers deployed in a VMware Cloud Foundation system.
What happened to the Tanzu entitlements?
With the release of VCF 5.0, VMware plans to retire the perpetual licensing for VMware Cloud Foundation in Q3 2023.
Around the same time, we can expect that VCF is only being sold as part of the “Cloud Packs” (connected and disconnected):
As already mentioned here, customers have also no more option to buy “Tanzu Standard” and existing Tanzu Standard customers can “upgrade” to “Tanzu Kubernetes Grid” (TKG) and Tanzu Mission Control (add-on).
There are several options available. Please contact your VMware representative.
VMware Cloud Foundation Architecture
VCF is made for greenfield deployments (brownfield not supported) and supports two different architecture models:
- Standard Architecture
- Consolidated Architecture
The standard architecture separates management workloads and lets them run on a dedicated management workload domain. Customer workloads are deployed on a separate virtual infrastructure workload domain (VI workload domain). Each workload domain is managed by a separate vCenter Server instance, which allows autonomous licensing and lifecycle management.
Note: The standard architecture is the recommended model because it separates management workloads from customer workloads.
Customers with a small environment (or a PoC) can start with a consolidated architecture. This allows you to run customer and management workloads together on the same workload domain (WLD).
Note: The management workload domain’s default cluster datastore must use vSAN. Other WLDs can use vSAN, NFS, FC, and vVols for the principal storage.
What is a vSAN Stretched Cluster?
vSAN stretched clusters extend a vSAN cluster from a single site to two sites for a higher level of availability and inter-site load balancing.
Does VCF provide flexible workload domain sizing?
Yes, that’s possible. You can license the WLDs based on your needs and use the editions that make the most sense depending on your use cases.
How many physical nodes are required to deploy VMware Cloud Foundation?
A minimum of four physical nodes is required to start in a consolidated architecture or to build your management workload domain. Four nodes are required to ensure that the environment can tolerate a failure while another node is being updated.
VI workload domains require a minimum of three nodes.
This means, to start with a standard architecture, you need to have the requirements (and money) to start with at least seven physical nodes.
What are the minimum hardware requirements?
These minimum specs have been listed for the management WLD since VCF 4.0 (September 2020):
Can I mix vSAN ReadyNodes and Dell EMC VxRail deployments?
No. This is not possible.
What about edge/remote use cases?
When you would like to deploy VMware Cloud Foundation workload domains at a remote site, you can deploy so-called “VCF Remote Clusters”. Those remote workload domains are managed by the VCF instance at the central site and you can perform the same full-stack lifecycle management for the remote sites from the central SDDC Manager.
Prerequisites to deploy remote clusters can be found here.
Note: If vSAN is used, VCF only supports a minimum of 3 nodes and a maximum of 4 nodes per VCF Remote Cluster. If NFS, vVOLs or Fiber Channel is used as principal storage, then VCF supports a minimum of 2 and a maximum of 4 nodes.
Important: Remote clusters and remote workload domains are not supported when VCF+ is enabled.
Does VCF support HCI Mesh?
Yes. VMware Cloud Foundation 4.2 and later supports sharing remote datastores with HCI Mesh for VI workload domains.
HCI Mesh is a software-based approach for disaggregation of compute and storage resources in vSAN. HCI Mesh brings together multiple independent vSAN clusters by enabling cross-cluster utilization of remote datastore capacity within vCenter Server. HCI Mesh enables you to efficiently utilize and consume data center resources, which provides simple storage management at scale.
Note: At this time, HCI Mesh is not supported with VCF ROBO.
What is SDDC Manager?
SDDC Manager is a preconfigured virtual appliance that is deployed in the management workload domain for creating workload domains, provisioning additional virtual infrastructure and lifecycle management of all the software-defined data center (SDDC) management components.
You use SDDC Manager in VMware Cloud Foundation to perform the following operations:
- Commissioning or decommissioning ESXi hosts
- Deployment of workload domains
- Extension of clusters in the management and workload domains with ESXi hosts
- Adding clusters to the management domain and workload domains
- Support for network pools for host configuration in a workload domain
- Product licenses storage
- Deployment of vRealize Suite components.
- Lifecycle management of the virtual infrastructure components in all workload domains, and of vRealize Suite Lifecycle Manager components.
- Certificate management
- Password management and rotation
- NSX-T Edge cluster deployment in the management domain and workload domains
- Backup configuration
How many resources does the VCF management WLD need during the bring-up process?
We know that VCF includes vSphere (ESXi and vCenter), vSAN, SDDC Manager, NSX-T and eventually some components of the vRealize Suite. The following table should give you an idea what the resource requirements look like to get VCF up and running:
If you are interested to know how many resources the Aria Suite (formerly vRealize Suite) will consume of the management workload domain, have a look at this table:
How can I migrate my workloads from a non-VCF environment to a new VCF deployment?
VMware HCX provides a path to modernize from a legacy data center architecture by migrating to VMware Cloud Foundation.
Can I install VCF in my home lab?
Note: Please have a look at “VCF Holodeck” if you would like to create a smaller “sandbox” for testing or training purposes.
Where can I find more information about VCF?
Please consult the VMware Foundation 5.0 FAQ for more information about VMware Cloud Foundation.