7.3

vRealize Automation storage allocation checks if there is sufficient space available on the datastore to
accommodate virtual machine disks during a create or reconfigure request. However, when the machine
is powered on, if enough space is not available to create swap files on the vCenter Server endpoint, the
machine fails to power on. When the power on operation fails, any customizations that depend on the
machine also fail. The machine may also be disposed of. Depending on the size of the request, feedback
that the machine is not powering on or not provisioning is not immediately obvious.
You can use the vSwap allocation check to help overcome these limitations by checking swap space
availability for the maximum size swap file as part of the vRealize Automation create and reconfigure
process for vCenter Server endpoints. To enable the vSwap allocation check, set the custom property
VirtualMachine.Storage.ReserveMemory to True in the machine component or overall blueprint.
Consider the following behaviors for vSwap allocation checks:
n
The swap file is located on the datastore that contains the virtual machine. Alternate vCenter Server
configurations for locating swap files on a dedicated or different datastore are not supported.
n
Swap size is considered when creating or reconfiguring a virtual machine . The maximum swap size
is the size of the virtual machine's memory.
n
Reserved values for vRealize Automation storage reservations in a host must not exceed the physical
capacity of the compute resource.
n
When creating a reservation, the sum of the reserved values must not exceed the available storage
space.
n
Resource pool or host level or virtual machine level memory reservations on vSphere are not
collected from the vSphere endpoint and not considered during the calculations on
vRealize Automation.
n
vSwap does not validate the swap space that is available during power on operations for existing
machines.
n
You must re-run data collection to capture any changes made to the vSphere endpoint relative to
vSwap.
Removing Datacenter Locations
To remove a datacenter location from a user menu, a system administrator must remove the location
information from the locations file and a fabric administrator must remove location information from the
compute resource.
For example, if you add London to the locations file, associate ten compute resources with that location,
and then remove London from the file, the compute resources are still associated with the location
London and London is still included in the location drop-down list on the Confirm Machine Request page.
To remove the location from the drop-down list, a fabric administrator must edit the compute resource and
reset the Location to blank for all compute resources that are associated with the location.
The following is a high-level overview of the sequence of steps required to remove a datacenter location:
1 A system administrator removes the datacenter location information from the locations file.
Managing vRealize Automation
VMware, Inc. 73