7.4

Table Of Contents
n
How much of that storage is already allocated in vRealize Automation
For example, even if the vCenter Server has storage available for the datastore/cluster, if sufficient
storage is not reserved in the reservation then provisioning fails with a "No reservation is available to
allocate..." error. The allocated storage on a reservation depends on the number of VMs (regardless of
their state) on that specific reservation. See the VMware Knowledge Base article Machine XXX: No
reservation is available to allocate within the group XXX. Total XX GB of storage was requested
(2151030) at http://kb.vmware.com/kb/2151030 for more information.
Reservations
You can create a vRealize Automation reservation to allocate provisioning resources in the fabric group to
a specific business group.
For example, you can use reservations to specify that a share of the memory, CPU, networking, and
storage resources of a single compute resource belongs to a particular business group or that certain
machines be allocated to a specific business group.
Note Storage and memory that are assigned to a provisioned machine by a reservation are released
when the machine to which they are assigned is deleted in vRealize Automation by the Destroy action.
The storage and memory are not released if the machine is deleted in the vCenter Server.
You can create a reservation for the following machine types:
n
vSphere
n
vCloud Air
n
vCloud Director
n
Amazon EC2
n
Azure
n
Hyper V (SCVMM)
n
Hyper-V Stand-alone
n
KVM (RHEV)
n
OpenStack
n
XenServer
You can configure security settings for the virtual machines to be provisioned by specifying information in
a reservation, blueprint, or guest agent script. If the machines to be provisioned requires a guest agent,
you must add a security rule that contains that requirement to the reservation or the blueprint. For
example, if you use a default security policy that denies communication between all machines, and rely
on a separate security policy to allow communication between specific machines, the guest agent might
be unable to communicate with vRealize Automation during the customization phase. To avoid this
problem during machine provisioning, use a default security policy that allows communication during the
customization phase.
Configuring vRealize Automation
VMware, Inc. 249