6.2

n
Cost per CPU specified in the virtual blueprint or installed in the physical machine
n
Cost per GB of storage capacity as specified in the virtual blueprint (not used for physical machines,
because storage attached to physical machines is not discovered or tracked)
For finer definition of storage cost for virtual machines, you can also associate each known datastore on a
compute resource with a storage cost profile. A storage cost profile contains only a daily cost per GB of
storage. If you assign a storage cost profile to a datastore, this storage cost overrides the storage cost in
the cost profile assigned to the compute resource.
For virtual machines, the machine cost is calculated from the cost profile and storage cost profile on the
compute resource, the resources it consumes, and the daily blueprint cost. You can use the blueprint cost
to represent a markup for using the machine in addition to the resources that the machine consumes, for
example to account for the cost of specific software deployed with that blueprint.
For physical machines, the machine cost is calculated from the cost profile on the machine, the CPU and
memory on the machine, and the daily blueprint cost. You can use the blueprint cost to represent such
factors as storage cost or additional costs for using the machine.
You cannot apply cost profiles to machines provisioned on Amazon Web Services or Red Hat OpenStack.
For machines provisioned on these cloud platforms, the only cost factor is the daily cost in the blueprint
from which it was provisioned. The cost for vCloud Director vApps includes any cost profile and storage
cost profile on the virtual datacenter and the blueprint cost.
Machine Blueprints
A machine blueprint is the complete specification for a virtual, cloud, or physical machine and is used to
determine a machine’s attributes and how it is provisioned.
When a business group member requests a machine, the machine is provisioned according to the
specifications in the blueprint, such as CPU, memory, and storage. Blueprints specify the workflow used
to provision a machine and include additional provisioning information such as the locations of required
disk images or virtualization platform objects. Finally, blueprints specify policies such as the lease period
and which operations are supported on machines provisioned from the blueprint.
An example of a virtual blueprint might be one that specifies a Windows 7 developer workstation with one
CPU, 2GB of memory, and a 30GB hard disk. A cloud blueprint might specify a Red Hat Linux web server
image in a small instance type with one CPU, 2GB of memory, and 160GB of storage. A physical
blueprint might specify Windows Server 2008 R2 installed on a server with exactly two CPUs and at least
4GB of memory.
Machine blueprints can be either specific to a business group or shared among groups in a tenant.
n
Business group managers can create group blueprints that can only be entitled to users in a specific
business group. A business group manager cannot modify or delete shared blueprints.
n
Tenant administrators can create shared blueprints that can be entitled to users in any business
group in the tenant. Tenant administrators cannot view or modify group blueprints unless they also
have the business group manager role for the appropriate group.
Foundations and Concepts
VMware, Inc. 31