7.1

When a virtual reservation’s machine quota, memory, or storage is fully allocated, no further virtual
machines can be provisioned from it. Resources may be reserved beyond the physical capacity of a
virtualization compute resource (overcommied), but when the physical capacity of a compute
resource is 100% allocated, no further machines can be provisioned on any reservations with that
compute resource until the resources are reclaimed.
n
If the blueprint has specic network seings, the reservation must have the same networks.
If the blueprint or reservation species a network prole for static IP address assignment, an IP address
must be available to assign to the new machine.
n
If the blueprint or request species a location, the compute resource must be associated with that
location.
If the value of the custom property VRM.Datacenter.Policy is Exact and there is no reservation for a
compute resource associated with that location that satises all the other criteria, then provisioning
fails.
If the value of VRM.Datacenter.Policy is NotExact and there is no reservation for a compute resource
associated with that location that satises all the other criteria, provisioning can proceed on another
reservation regardless of location. This option is the default.
n
If the blueprint or request species the custom property VirtualMachine.Host.TpmEnabled, trusted
hardware must be installed on the compute resource for the reservation.
n
If the blueprint species a reservation policy, the reservation must belong to that reservation policy.
Reservation policies are a way to guarantee that the selected reservation satises any additional
requirements for provisioning machines from a specic blueprint. For example, you can use reservation
policies to limit provisioning to compute resources with a specic template for cloning.
If no reservation is available that meets all of the selection criteria, provisioning fails.
If multiple reservations meet all of the criteria, the reservation from which to provision a requested machine
is determined by the following logic:
n
A reservation with a lower priority value is selected before a reservation with a higher priority value.
n
If multiple reservations have the same priority, the reservation with the lowest percentage of its
machine quota allocated is selected.
n
If multiple reservations have the same priority and quota usage, machines are distributed among
reservations in round-robin fashion.
N While round-robin selection of network proles is not supported, round-robin selection of
networks (if any) is supported, which can be associated with dierent network proles.
If multiple storage paths are available on a reservation with sucient capacity to provision the machine
volumes, storage paths are selected according to the following logic:
n
If the blueprint or request species a storage reservation policy, the storage path must belong to that
storage reservation policy.
If the value of the custom property VirtualMachine.DiskN.StorageReservationPolicyMode is NotExact and
there is no storage path with sucient capacity within the storage reservation policy, then provisioning
can proceed with a storage path outside the specied storage reservation policy. The default value of
VirtualMachine.DiskN.StorageReservationPolicyMode is Exact.
n
A storage path with a lower priority value is selected before a storage path with a higher priority value.
n
If multiple storage paths have the same priority, machines are distributed among storage paths in
round-robin fashion.
Configuring vRealize Automation
212 VMware, Inc.