TECHNICAL WHITE PAPER / 10
Technical Note: Using VMware vCenter Chargeback
Manager with VMware vCloud Director
Backdate functionality is not currently available for vCloud hierarchies; it can be applied against only
vCenter hierarchies.
Custom attributes can be defined against any object within the hierarchy. By default, the system creates
an attribute called vCloudEntityID
vCloud Director entity. This system-defined attribute indicates the object type and ID as stored in the
If a vApp, network, or catalog file is deleted using vCloud Director, it is automatically removed from vCenter
Chargeback Manager. If an organization or organization vDC is deleted using vCloud Director, it remains in
Cost data associated with that organization/chargeback hierarchy is not automatically deleted. These hierarchies
NOTE: If an object or hierarchy is deleted using vCenter Chargeback Manager but still exists in vCloud Director,
this is an irreversible operation. There is no method for selectively resynchronizing the hierarchy structure
between the two products. vCloud hierarchies deleted from vCenter Chargeback Manager are not recreated
by the vCloud Director data collector. Exercise caution when deleting hierarchy objects within vCenter
Chargeback Manager.
Allocation Units
vCenter Chargeback Manager tracks resource allocations for all vCloud entities in each hierarchy. The vCloud
Director data collector sets allocation unit values in vCenter Chargeback Manager. When the allocations change
in vCloud Director, the allocation units are updated accordingly.
NOTE: For vCloud entities such as vDCs and vApps, vCenter Chargeback Manager solely tracks allocation. Usage
or reservation data from vCenter Server is not correlated. vCenter Chargeback Manager gets usage and
reservation data for the virtual machines pulled from vCenter Server.
Allocation Pool
and memory are based on the overage flags configured. Modify the VMware vCloud Director apply overage
charge on Allocation Pool vDC attribute on the vCloud Director data collector to enable or disable overage
charging.
false (default), allocation unit = configured limit in vCloud Director.
true, allocation unit = configured limit in vCloud Director* percentage of resources guaranteed.
This enables overage charging.
global overage flag = true
allocation unit: 10GB* 50 percent = 5GB
It is possible to override the global setting by assigning the EntityLevelOverageFlag attribute on an individual
entity. Overage flags are applicable only to newly created Allocation Pool vDCs. The allocation units of existing
Allocation Pool vDCs are not changed.
Reservation Pool
reserved (set to the limit) and the customer should be billed accordingly.
Pay As You Go
do not appear, ensure that a connection to the vCenter Server hosting the cloud workloads has been established.
Commentaires sur ces manuels