HP Matrix Operating Environment 7.3 and 7.3 Update 1 Infrastructure Orchestration User Guide

To see the IP address of the VM Host where a virtual machine was provisioned, in the infrastructure
orchestration console Services tab, select the service and click Service Details. Select the server
group, and select the Resource Details tab in the lower pane. The rightmost column is labeled
Resource Binding ID, and contains the IP address of the ESX host where the VM was ultimately
created.
Allocating storage to virtual machines
Matrix infrastructure orchestration uses the following guidelines to place virtual machine disks.
• Matrix infrastructure orchestration allocates storage to the datastore on the target VM Host
with the most free space available.
• For each VM, the boot disk and private data disks can be allocated to different storage
volumes, with the following exceptions:.
◦ Integrity VM disks must use the same Storage Volume Name or be left blank.
◦ Cloud server disks do not support Storage Volume Names and must be left blank.
◦ Hyper-V VM linked clone disks must have the same Storage Volume Name or be left
blank. Hyper-V VM linked clone cannot be spread across different datastores.
NOTE: By default, specifying storage volume names when adding a disk to a VM is
restricted to administrators. To enable all users to specify storage volume names when
adding a disk to a VM, change the value of the hpio.properties
user.disk.add.storage.volume.names.restricted property from true to
false.
For Integrity VMs, a single Shared Logical Volume Manager (SLVM) datastore may be
composed of one or more physical volumes/disks. IO interprets an SLVM datastore as a single
entity, with a single size.
• For ESX 4.0 and later, if a shared disk is defined for the server group, all disks for all the VMs
in the server group are allocated to the same datastore. (Hyper-V, Integrity VM, and ESX 3.5
do not support shared disks.)
When shared disks are specified, the first VM in the service takes longer to create than
subsequent VMs. This occurs because the first VM is created separately. After its completion,
the rest of the VMs are created in parallel.
• If linked clone provisioning is specified (by selecting Deploy as Linked Servers in the server
group configuration), all disks for all VMs in the server group are allocated to the same
datastore.
The provisioning time for linked clones is increased by the need to first provision a parent VM,
which is then used to create the child VMs.
Linked clone provisioning can also require more space than is designated in the template. If
you deploy only one server, the amount of disk space will be more than the template because
you are provisioning a parent VM and a child VM. However, if you deploy more than one
server, the total size might be less than the template because the space needed by the parent
VM is deducted from the total. The parent VM is powered off and used to create the child
VMs. The parent VM is never powered on again; only the children VMs are powered on.
• If there are no shared disks, no Storage Volume Names, and no linked clones, then each VM
in the server group and its disks may be allocated to different hosts on different datastores,
or to the same host and different datastores, based on free space.
Virtual data disk names can contain letters (A-Z, a-z), numbers (0-9), space, underscore, and
hyphen. Other characters, including double-byte characters, are not allowed. Physical data disks
and boot disks can contain localized names.
120 Matrix infrastructure orchestration provisioning and allocation