Starting with VMware Cloud Director 9.7, system administrators can create organization virtual data centers (VDC) by using the flex allocation model. With the combination of flex allocation and VM sizing policies, system administrators can control CPU and RAM consumption at both the VDC and the individual virtual machine (VM) levels. The flex allocation model supports all allocation configurations that are available in the existing allocation models.
If you create a non-flex organization VDC in VMware Cloud Director 9.7, you can reconfigure the organization VDC to use the flex allocation model. If an organization VDC is created by using VMware Cloud Director version earlier than 9.7, you cannot reconfigure the organization data centers to use the flex allocation model in version 9.7. In VMware Cloud Director 10.0 and later, all non-flex organization VDCs can be converted into flex VDCs.
|Elasticity||Enable or disable the elastic pool feature.|
|Include VM Memory Overhead||Include or exclude memory overhead in this VDC. When set to true, you might not be able to use the full capacity of the VDC because the memory overhead of every powered-on VM is also taken from the available capacity of the VDC. When set to false, the memory overhead is taken from the provider VDC and not from the allocated capacity of the VDC.|
|CPU allocation||The amount of CPU allocated to this VDC in MHz or GHz. The CPU allocation defines the CPU capacity of the VDC. The total CPU used by all VMs running in the VDC cannot exceed this value.|
The CPU limit defines the CPU quota of a VDC. In most cases, the CPU limit is equal to the allocated CPU capacity of the VDC.
Sometimes, you might be required not to allocate any CPU to the VDC, as in the pay-as-you-go model. In this case, you must set a quota on the overall CPU consumption by setting the CPU allocation to zero and the CPU limit to a non-zero value.
You might also use this setting to allow an unlimited CPU quota. If set to unlimited, the backing resource pools of the VDC in vCenter Server get unlimited CPU.
|CPU resources guaranteed||The percentage of CPU allocation that is physically reserved for the VDC.|
|vCPU speed||The default vCPU speed for VMs in the VDC.|
|Memory allocation||The amount of memory allocated to this VDC in MB or GB. This parameter defines the total memory capacity of the VDC. The total configured memory by all VMs running in the VDC cannot exceed this value.|
|Memory resources guaranteed||The percentage of memory allocation that is physically reserved for the VDC.|
|Maximum number of VMs||The maximum number of VMs in the VDC.|
As a VMware Cloud Director system administrator, you can configure a flex organization VDC to be elastic or non-elastic. When flex organization VDCs have the elastic pool feature enabled, the organization VDC spans and uses all resource pools that are associated with its provider VDC. In VMware Cloud Director 9.7, if you convert a non-elastic organization VDC to an elastic organization VDC, you cannot convert the same organization VDC back to a non-elastic.
The flex allocation model supports the capabilities of VM sizing policies without any constraints that other allocation models have. In the flex allocation model, the VM compute resource allocation depends on the VM sizing policies. If you do not define a VM sizing policy for an organization VDC, the compute resource allocation depends on the organization VDC allocation model. Using the combination of the flex allocation model and the organization VM sizing policies, a single organization VDC can accommodate VMs that use configuration that is common for all other allocation models. For more information, see Understanding VM Sizing and VM Placement Policies.
To create a flex organization VDC, you can use the VMware Cloud Director Service Provider Admin Portal or vCloud API. For information about vCloud API, see VMware Cloud Director API Programming Guide.