You can add each virtual reservation to one reservation policy. The reservation from which a particular virtual machine is provisioned is determined by vRealize Automation based on the reservation policy specified in the blueprint, if any, the priorities and current usage of the fabric group's reservations, and other custom properties.


Table 1. Reservation Policy Design Decisions

Decision ID

Design Decision

Design Justification

Design Implication

ROBO-CMP-019

Create at least one workload reservation policy for each ROBO.

Reservation policies are used to target a deployment to a specific set of reservations in each ROBO. Reservation policies are also used to target workloads into their appropriate vSphere resource pool.

None

ROBO-CMP-020

Create at least one reservation policy for placement of dynamically created edge services gateways into the User-Edge resource pool.

Required to place the edge devices into their respective edge vSphere resource pool.

None

A storage reservation policy is a set of datastores that can be assigned to a machine blueprint to restrict disk provisioning to only those datastores. Storage reservation policies are created and associated with the appropriate datastores and assigned to reservations.

Table 2. Storage Reservation Policy Design Decisions

Decision ID

Design Decision

Design Justification

Design Implication

ROBO-CMP-021

Within this design, storage tiers are not used.

The underlying physical storage design does not use storage tiers.

Both business groups will have access to the same storage.

For customers who utilize multiple datastores with different storage capabilities will need to evaluate the usage of vRealize Automation Storage Reservation Policies.