Planning Guide—VMware Cloud Foundation 3.x on VxRail
Executive Summary
VMware Cloud Foundation on VxRail Product Overview
VMware Cloud Foundation on VxRail Deployment
Data Center Requirements
Use Cases and High-Level Design
Cloud Foundation on VxRail Workload Planning
Application Dependencies and Routing Decisions
Cloud Foundation on VxRail Physical Network Planning
VxRail Cluster Deployment Preparation
Prepare for VMware Cloud Foundation Management VI Workload Domain
Prepare for Cloud Foundation Application Virtual Network
Prepare for Cloud Foundation VI Workload Domain
Cloud Foundation on VxRail Footprints for Sizing
Cloud Foundation on VxRail VLANs
VxRail Network Configuration
Cloud Builder and Management VI Workload Domain Configuration
Application Virtual Network Configuration
VI Workload Domain Configuration Settings
NSX Routing Settings
Example Switch Configuration Settings for BGP Peering
Deciding on single-site VxRail cluster or stretched cluster
Deciding on single-site VxRail cluster or stretched cluster
-
If you deploy VxRail stretched clusters instead of a single-site cluster in order to meet availability requirements, be aware of the impact this decision has in planning the workload. A VxRail stretched cluster requires double the number of VxRail nodes to support any planned workload, as each site must be able to support that workload in the event of a site failure.
Figure 15 Impact of VxRail stretched cluster on virtual machine workload
In addition, every write operation by a virtual machine is performed on the vSAN datastore at both sites. Therefore, the size of the physical storage positioned to support any planned workload must be doubled.