2.0

2 Select DataStores from the drop-down menu.
3 Expand the tier folder containing the datastore or storage profile that you want to move.
4 Right-click the datastore or storage profile that you want to move to another tier and select Move this
Datastore to another tier.
5 Right-click the tier folder to which you want to move this datastore and select Put the Datastore/Storage
Profile in this tier.
The datastore or storage profile is moved to the new tier folder.
Configuring a Pricing Matrix for Virtual Machines
vCenter Chargeback Manager provides functionality to charge a fixed cost for virtual machines in a hierarchy
based on the vCPU count and memory.
You can define one or more pricing matrices for the virtual machines in your hierarchies, such that the virtual
machines are charged a fixed cost based on the vCPU count and memory bundle. This cost is applied only for
the duration when a virtual machine is powered on and is not pro-rated.
A price matrix is associated with a cost model and can contain multiple cost entries for different vCPU count
and memory bundles. You can also define a criterion to specify the hierarchies for which the price matrix is
applicable. You can define multiple pricing matrices with different hierarchy selection criteria for each cost
model defined in vCenter Chargeback Manager. Each hierarchy selection criteria for a selected cost model
must be unique. Also, each entry in the pricing matrix must be unique.
vCenter Chargeback Manager applies the fixed cost defined in the pricing matrix on the virtual machines in a
hierarchy by running a job that periodically checks for new and updated hierarchies, and hierarchy selection
criteria and the corresponding pricing matrix. Based on the hierarchy and entity selection criteria, the
application uses the corresponding pricing matrix to apply the fixed cost on the virtual machines in the
hierarchies that match the specified criterion as follows:
1 vCenter Chargeback Manager checks for the hierarchy selection criteria and the corresponding pricing
matrices defined in it.
2 vCenter Chargeback Manager uses the pricing matrix corresponding to the first matching criterion for
each hierarchy.
3 vCenter Chargeback Manager first searches for a row in the pricing matrix that has the same vCPU count
as in the virtual machine.
4 If such a row is not found, then vCenter Chargeback Manager selects the row with the next higher value
of vCPU count than in the virtual machine.
5 For the selected vCPU count, vCenter Chargeback Manager checks for a memory value equal to or higher
than the memory in the virtual machine.
6 If a row with the vCPU count or memory value equal to or higher than the vCPU count or memory in the
virtual machine is not found, then vCenter Chargeback Manager uses the default cost configured in the
matrix.
NOTE For hierarchies imported from vCloud Director, the vCPU count and memory allocation values
synchronized from the vCloud Director database is considered for applying the fixed cost. For hierarchies
created in vCenter Chargeback Manager, the vCPU count and memory utilization values synchronized from
the vCenter Server database is used for applying the fixed cost.
If a virtual machine configuration is changed, then the corresponding change in the fixed cost is applicable
from the time the configuration change is effected. If the fixed cost in the pricing matrix is changed, then the
change is effected from the next run of the job.
Chapter 5 Managing and Configuring vCenter Chargeback Manager Cost Elements
VMware, Inc. 91