HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

◦ Multi-server (SCVMM service) templates are excluded.
◦ No explicit indication is given when a template is filtered from view.
• When using SCVMM 2012 with a Windows 2012 template, you must add the CDKEY to the
template. The CDKEY can be changed during the customization process if you add a new
key in the sysprep file. If the SCVMM is registered as a VME, then Insight Management uses
SCVMM only to deploy its templates. All other operations are executed by Insight Management
directly on the Hyper-V hosts, not through SCVMM.
• Create SCVMM templates with the “No Customization Required” option. IO overwrites the
SCVMM customization parameters with its own customization, and some SCVMM customization
parameters could persist after IO customization, potentially creating a confusing result.
• Create SCVMM templates with the Virtualization platform set to Microsoft Hyper-V.
To set this property:
1. Open the SCVMM manager.
2. Go to Library→Templates
3. Right-click in the template and select Properties.
4. Select the Dependencies tab.
5. Select the disk to be listed in the dependent list.
6. Under Virtualization platform, select Microsoft Hyper-V.
Configuring ESX memory oversubscription
When Matrix infrastructure orchestration is used to provision services with ESX virtual machines,
by default it uses memory oversubscription techniques to allow a larger number of virtual machines
to be provisioned to an ESX host.
The ESX virtual machines created by IO do not use memory reservation, and IO has a low
requirement for free memory in the ESX host when it checks if a virtual machine fits in a specific
host. (The default value is 2% of the virtual machine memory.) For example, if a service contains
a virtual machine that requires 4 GB of RAM, IO requires a VM Host to have approximately 82
MB of available memory (2% of 4 GB). Therefore, any VM Host with at least 82 MB of available
memory passes the memory check in the allocation phase of service provisioning.
This strategy allows a larger number of virtual machines to be provisioned to an ESX host, but in
some situations it might result in degradation of the virtual machine performance. This can happen
when there are too many virtual machines in a specific VM Host, and the VM Host starts swapping
the host memory to disk.
If a more conservative memory oversubscription approach is desired, IO can be configured to use
a more restrictive check of the available memory in the ESX host before provisioning a virtual
machine. The default value of 2% for the required available host memory can be increased.
Increasing this value might cause IO to fail in the resource allocation step when provisioning a
service with ESX virtual machines. This will happen whenever IO is not able to find an ESX host
with the required amount of available memory.
Increasing this configuration to 50% allows IO to be more conservative when provisioning ESX
virtual machines, while still allowing some level of memory oversubscription. To change this
configuration, edit hpio.properties in the default location at ..\Program Files\HP\
Matrix infrastructure orchestration\conf. Locate the property
esx.vm.requested.memory.max.percent and change the property to
esx.vm.requested.memory.max.percent=50.0.
After changing this value, restart the Matrix infrastructure orchestration service for the new
configuration to take effect. Changing this configuration does not affect services already provisioned.
Configuring an environment for virtual provisioning 45