The multi-machine service cost appears at various stages of the request and provisioning life cycle and is updated according to the current information in the request or on the provisioned item.

Table 1. Cost Displayed During the Request and Provisioning Life Cycle

Life Cycle Stage

Value Displayed for Cost

Viewing the catalog item details prior to request

Projected costs of the multi-machine service based on the cost profile, the values for machine resources specified in the component blueprints, lease duration specified in the multi-machine blueprint, and the daily costs specified in the component blueprints and multi-machine blueprint.

The values of some of the cost drivers can be unknown before a machine is requested:

  • The component blueprints can specify a range for machine resources or number of components of each type. The requester can specify any value within the blueprint range.

  • More than one reservation can be available for provisioning the component machines. If these reservations have different compute resources, different cost profiles can apply.

  • More than one datastore can be available for provisioning the component machines, either on the same reservation or on different reservations, that have different storage cost profiles.

  • If either more than one reservation or datastore is available, the daily cost appears as a range with the lower bound being the minimum resource usage multiplied by the lowest resource cost for memory, CPU, and storage, and the upper bound being the maximum resource use multiplied by the highest cost.

If the multi-machine blueprint specifies a value for lease duration, 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 values for machine resources and lease duration specified in the request form and the blueprint cost.

The daily cost can be a range if more than one reservation is available for provisioning the component machines and these reservations have different compute resources that vary in cost. Alternatively, more than one datastore can be available for provisioning the machine, either on the same reservation or on different reservations, that vary in cost.

By default, the request form shows the request for the multi-machine service, but the requester can select a specific component machine to edit the properties of the component. The values for daily and lease cost are updated as the user edits the relevant values in the request form. The user can also specify the number of machines of each type in the multi-machine service, which affects the total cost.

Viewing details of a submitted request or approving a request

Projected costs based on the requested machine resources, lease duration, and blueprint cost.

The daily cost can be a range if more than one reservation is available for provisioning the component machines and these reservations have different compute resources or different datastores that vary in cost.

Depending on the approval policy, an approver can edit the number of component machines or the lease duration, which can affect the cost. The approval applies to the multi-machine service as a whole. The component machines are not approved separately.

Viewing the details of a provisioned multi-machine service

Actual daily cost, lease cost, and cost-to-date based on the resource use of the provisioned component machines, lease duration, blueprint costs, and number of days since the multi-machine service was provisioned. You can view the cost details for the multi-machine as a whole and its component machines.