An allocation model determines how and when the allocated provider virtual data center (VDC) compute and memory resources are committed to the organization VDC.
|Flex Allocation Model||Elastic Allocation Pool Model||Non-Elastic Allocation Pool Model||Pay-As-You-Go Model||Reservation Pool Model|
|Elastic||Based on the organization VDC configuration.||Yes||No||Yes||No|
|vCPU Speed||If a VM CPU limit is not defined in a VM sizing policy, vCPU speed might impact the VM CPU limit within the VDC.||Impacts the number of running vCPUs in the Organization VDC.||Not Applicable||Impacts VM CPU Limit||Not Applicable|
|Resource Pool CPU Limit||Organization VDC CPU limit apportioned based on the number of VMs in the resource pool.||Organization VDC CPU allocation||Organization VDC CPU allocation||Unlimited||Organization VDC CPU allocation|
|Resource Pool CPU Reservation||Organization VDC CPU reservation is apportioned based on the number of vCPUs in the resource pool. Organization VDC CPU reservation equals the organization VDC CPU allocation times the CPU guarantee.||Sum of powered on VMs and equals the CPU guarantee times the vCPU speed, times the number of vCPUs.||Organization VDC CPU allocation times the CPU guarantee||None, expandable||Organization VDC CPU allocation|
|Resource Pool Memory Limit||Organization VDC memory limit is apportioned based on the number of VMs in the resource pool.||Unlimited||Organization VDC RAM allocation||Unlimited||Organization VDC RAM allocation|
|Resource Pool Memory Reservation||Organization VDC RAM reservation is apportioned based on the number of VMs in the resource pool. The organization VDC RAM reservation equals the organization VDC RAM allocation times the RAM guarantee.||Sum of RAM guarantee times vRAM of all powered-on VMs in the resource pool. The resource pool RAM reservation is expandable.||Organization VDC RAM allocation times the RAM guarantee||None, expandable||Organization VDC RAM allocation|
|VM CPU Limit||Based on the VM sizing policy of the VM.||Unlimited||Unlimited||vCPU speed times the number of vCPUs||Custom|
|VM CPU Reservation||Based on the VM sizing policy of the VM.||0||0||Equals the CPU speed times the vCPU speed, times the number of vCPUs.||Custom|
|VM RAM Limit||Based on the VM sizing policy of the VM.||Unlimited||Unlimited||vRAM||Custom|
|VM RAM Reservation||Based on the VM sizing policy of the VM.||0||Equals vRAM times RAM guarantee plus RAM overhead.||Equals vRAM times RAM guarantee plus RAM overhead.||Custom|
Converting a Legacy VDC Allocation Model to a Flex Allocation Model
You add a VM placement and VM sizing policy to a VDC with an elastic allocation pool model, non-elastic allocation pool model, pay-as-you-go model, or reservation pool model. If the VM placement or VM sizing policy is not compatible with the existing VDC allocation model, you can decide to convert the VDC to a flex organization VDC.
VM Policy Compliance
Legacy VDC conversion does not cause VM non-compliance. If an administrator changes the VM compute values or VM group membership of a VM directly in the vCenter Server instance, a VM can become non-compliant with the assigned VM sizing or VM placement policy. A VM can also become non-compliant if a user with the necessary privileges changes the VM reservation and limit values by using the vCloud API. If there is a non-compliant VM, vCloud Director Tenant Portal UI displays a warning message. The tenant can see detailed information about the cause for the non-compliance and can make the VM compliant again, which reapplies the policies to the VM.