To support more tenant workloads and improve high availability and isolation, or to introduce new services or workload types, you can plan to add more clusters to a workload domain.
You are considering increasing the number of workload domains for one of the following reasons:
-
Support increasing the overall number of workloads.
-
Improve the availability of workloads across workload domains.
-
Increase the separation of workloads across the workload domains for security, licensing, or other reasons.
-
Provide functional separation of services that use vCenter Server directly without impacting the existing vCenter Server instances.
-
Add support for different types of workloads such as virtual desktops (VDI) and containers, and for maintaining production and development environments.
Considerations
-
Although adding workload domains can improve the overall scalability of the solution and parallel life-cycle management, the life-cycle tasks and license requirements are also increased because of the new vCenter Server instances.
-
When deciding on the number of workload domains to deploy, consider these limits:
-
VMware Validated Design supports the vSphere maximum of 15 vCenter Server instances in a vCenter Single Sign-On domain. Beyond this number, a single pane of glass management for all vCenter Server instances in your environment is not be possible.
-
VMware Validated Design supports theVMware vRealize® Automation™ limit of 20 vCenter Server endpoints.
-
VMware vSphere® Replication™ can replicate up to 2,000 virtual machines between vCenter Server instances that are paired by using VMware Site Recovery Manager™. If you want to protect more than 2,000 workloads in this way, then you must deploy additional workload domains in each region.
-
-
Having additional vCenter Server endpoints in vRealize Automation means that if you want to be able to deploy the same template on more than one endpoint, you must implement a solution to manage workload virtual machine templates across the endpoints.
