7.4

Table Of Contents
During provisioning, machines are placed on a host that is connected to the local storage. If the
reservation uses local storage, all the machines that are provisioned by the reservation are created
on the host that contains that local storage. However, if you use the
VirtualMachine.Admin.ForceHost custom property, which forces a machine to be provisioned to a
different host, provisioning fails. Provisioning also fails if the template from which the machine is
cloned is on local storage, but attached to a machine on a different cluster. In this case, provisioning
fails because it cannot access the template.
3 (Optional) Enter a number in the Machine quota text box to set the maximum number of machines
that can be provisioned on this reservation.
Only machines that are powered on are counted towards the quota. Leave blank to make the
reservation unlimited.
4 Specify the amount of memory, in GB, to be allocated to this reservation from the Memory table.
The overall memory value for the reservation is derived from your compute resource selection.
5 Select one or more listed storage paths.
The available storage path options are derived from your compute resource selection.
For integrations that use Storage Distributed Resource Scheduler (SDRS) storage, you can select a
storage cluster to allow SDRS to automatically handle storage placement and load balancing for
machines provisioned from this reservation. The SDRS automation mode must be set to Automatic.
Otherwise, select a datastore within the cluster for standalone datastore behavior. SDRS is not
supported for FlexClone storage devices.
You can select either individual disks in the cluster or a storage cluster, but not both. If you select a
storage cluster, SDRS controls storage placement and load balancing for machines that are
provisioned from this reservation.
6 If available for the compute resource, select a resource pool in the Resource Pool drop-down menu.
7 Click the Network tab.
Configuring vRealize Automation
VMware, Inc. 284