When deploying a VI workload domain, you specify the storage, name, compute, and networking details. Based on the selected storage, you provide vSAN parameters, NFS share details, VMFS on FC datastore information, or vVols storage details. You then select the hosts and licenses for the VI workload domain and start the workflow.
The workflow automatically:
- Deploys a vCenter Server Appliance for the new VI workload domain within the management domain. By using a separate vCenter Server instance per VI workload domain, software updates can be applied without impacting other VI workload domains. It also allows for each VI workload domain to have additional isolation as needed.
- Connects the specified ESXi servers to this vCenter Server instance and groups them into a cluster. Each host is configured with the port groups applicable for the VI workload domain.
- Configures networking on each host.
- Configures vSAN, NFS, VMFS on FC, or vVols storage on the ESXi hosts.
- For the first VI workload domain, the workflow deploys a cluster of three NSX Managers in the management domain and configures a virtual IP (VIP) address for the NSX Manager cluster. The workflow also configures an anti-affinity rule between the NSX Manager VMs to prevent them from being on the same host for high availability. Subsequent VI workload domains can share an existing NSX Manager cluster or deploy a new one. To share an NSX Manager cluster, the VI workload domains must use the same update method. The VI workload domains must both use vSphere Lifecycle Manager (vLCM) images, or they must both use vLCM baselines.
- By default, VI workload domains do not include any NSX Edge clusters and are isolated. To provide north-south routing and network services, add one or more NSX Edge clusters to a VI workload domain. See NSX Edge Cluster Management.
Note: You can only perform one VI workload domain operation at a time. For example, while you are deploying a new VI workload domain, you cannot add a cluster to any other VI workload domain.