When employing vSAN, it is important to consider the impact on other resources in the vCloud Director environment because tenant organizations also require CPU and memory compute resources to operate. Organizations across a vCloud Director platform draw all of their resources from Org VDCs, whose resources are drawn from the respective Provider VDC. The Provider VDC resources are a collection of CPU, memory, network, and storage abstracted from the underlining vSphere platform.

In a hyper-converged vSAN environment, the appropriate allocation and balance of required CPU, memory and network resources is equally as important to calculate as storage to implement a successful design, and to provide for the ongoing operation of the Provider VDCs across the vCloud Director platform.

Just as a Provider VDC allows the service provider to pool infrastructure resources to create standard offerings to tenants, Provider VDCs can also be employed to group different levels of compute resources to compliment the different tiers of storage. Ensuring a balance of all three resource types is an important design calculation that must be addressed to provide optimum balance of compute, storage, and networks within the PVDC.

For instance, Tier 0 CPU, memory, and network resources can be combined with the fastest storage type to create a balanced Provider VDC, which can be priced to consumers at the appropriate level, typically at a higher cost than Tier 1 or 2, as illustrated in the following figure.