Operating Environment Software Instruction Manual

not display on the Software tab of the infrastructure orchestration console, preventing the successful
creation of an IO template.
Microsoft System Center Virtual Machine Manager (SCVMM) templates
Matrix infrastructure orchestration enables the deployment of services using the Microsoft System
Center Virtual Machine Manager (SCVMM) template library. This is accomplished by selecting an
SCVMM Hyper-V template on the Software tab in an infrastructure orchestration service template.
SCVMM templates are displayed on the infrastructure orchestration console Software tab after
SCVMM is successfully registered in Insight Control virtual machine management. To register
SCVMM:
1. Discover the SCVMM server in Systems Insight Manager.
2. Enter valid SCVMM credentials on the VME tab. Select the Systems Insight Manager
Options→VME Options→Add or Edit VME Credentials.
Or, from the SCVMM server’s system properties, select the Tools & Links tab, then click Add
or Edit VME Credentials.
The SCVMM server itself is not representative of a server pool, nor is it licensed as a target for
deployment.
SCVMM is not a required component for Hyper-V deployment. SCVMM template deployment is
an option that coexists with deployments of HP Insight Control virtual machine management Hyper-V
templates.
The following constraints apply when using SCVMM templates.
• Microsoft SCVMM 2008 R2 is required for this integration
• A subset of SCVMM templates are included in the IO inventory:
Hyper-V templates with a single VM are included◦
◦ ESX and other hypervisor types are excluded
◦ Multi-server (SCVMM service) templates are excluded
◦ No explicit indication is given when a template is filtered from view
• 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.
• VMs deployed using SCVMM in a Hyper-V cluster environment are enabled for high availability
(HA) by default, even when the IO template specifies a non-HA VM. If the VM is later
deactivated and reactivated, it will continue to be enabled for high availability.
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 4GB of RAM, IO requires a VM Host to have approximately 82MB
of available memory (2% of 4GB). Therefore, any VM Host with at least 82MB 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
42 Installation and configuration