6.2

Table 2‑2. Cost Displayed During the Request and Provisioning Life Cycle
Life Cycle Stage Value Displayed for Cost
Viewing the catalog item details before a
request
Projected costs based on the cost profile, the lease duration specified in the blueprint,
the daily blueprint cost, and the machine resources on the physical machine.
More than one physical machine that matches the blueprint specifications can exist. If
these machines have different costs, the cost displays as a range.
If the blueprint has the at least option selected for resource matching, then the
candidate physical machines can have different specifications from what is selected in
the blueprint, resulting in higher costs than expected.
If the blueprint specifies a range for the lease duration or the daily cost is a range, the
lease cost appears as a range with the lower bound being the minimum lease duration
multiplied by the minimum cost, and the upper bound being the maximum lease
duration multiplied by the maximum cost.
Completing the request form Projected costs based on the cost profile, the lease duration specified in the request
form, the daily blueprint cost, and the machine resources on the physical machine.
More than one physical machine that matches the specifications in the request form
can exist. If these machines have different costs, the cost displays as a range.
If the blueprint has the at least option selected for resource matching, then the
candidate physical machines can have different specifications from what is specified in
the request form, resulting in higher costs than expected.
By default, the request form is populated with the minimum values for machine
resources and lease duration, and the values for daily and lease costs are calculated
accordingly. The costs are updated as the user edits the relevant values in the request
form.
Viewing details of a submitted request or
approving a request
Projected costs based on the requested lease duration, blueprint cost, and the
machine resources on the physical machine.
More than one physical machine that matches the specifications in the request can
exist. If these machines have different costs, the cost appears as a range.
If the blueprint has the at least option selected for resource matching, then the
candidate physical machines can have different specifications from what is specified in
the request, resulting in higher costs than expected.
Viewing the details of a provisioned
machine
Actual daily cost, lease cost, and cost-to-date based on the resource use of the
provisioned machine, lease duration, blueprint cost, and number of days since the
machine was provisioned.
Configure a Cost Profile
Fabric administrators can create cost profiles and associate them with physical machines to enable
calculation of a machine’s cost.
Prerequisites
Log in to the vRealize Automation console as a fabric administrator.
Procedure
1 Create a Cost Profile
Fabric administrators create cost profiles to define daily costs for memory and CPU for physical
machines.
IaaS Configuration for Physical Machines
VMware, Inc. 30