To be alerted when this document is updated, click the Subscribe to Article link in the Actions box in the Actions box.
VMware vCloud Director が、組織VDC上のアロケーションプールにおいてCPU消費をレポートしないImpact/Risks:
There are two functional modes for Organization Virtual Datacenters (Org vDC) based on the Allocation Pool Model:
- Single Cluster Allocation Pool (SCAP)
- Elastic Allocation Pool
In earlier versions of vCloud Director 5.1.0, all Allocation Pools were functional only in SCAP mode since the feature did not exist. In vCloud Director 5.1.0, Allocation Pools only function in Elastic mode. In vCloud Director 5.1.2, there is an option to change between modes in a global fashion. You cannot have a subset Organization vDCs act in SCAP mode and the compliment act in Elastic mode.
When vCloud Director is running in SCAP mode:
- Allocation Pools are limited to deploy the Primary Resource pool of the Provider vDC.
- The properties of the Org vDC does not show a vCPU Frequency option.
- Consumption of the CPU Reservation in the Allocation Pool is 0, which is normal and expected.
When vCloud Director is running in Elastic Allocation Pool mode:
- Virtual machines can be deployed in any Resource Pool of the Provider VDC
- The properties of the Org vDC have a vCPU Frequency option. This works similar to the Pay-As-You-Go Org vDC model.
- Consumption of the CPU Reservation in the Elastic Allocation pool is a sum of the powered on virtual machines which have a guarantee configured on them.
Note: When switching between modes, guarantees are only applied to virtual machines at the time virtual machine is powered on. It may be required to stop and start the vApps inside the Org vDC to update their values as per the new Org VDC settings.
For more information about the differences between enabling and disabling Make Allocation pool Org VDCs elastic, see the Understanding Allocation Models section in the
vCloud Administrator's guide.