HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

Default memory setting

The default minimum memory setting for templates that use the SA server to deploy software is 512

MB. This value can be changed in the ..\Program Files\HP\Matrix infrastructure

orchestration\conf\hpio.properties file. Search for the following lines:

# Template Config minimum MB "Memory size:" for SA agent install

sa.minimum.memory=512

Configuring an environment for virtual provisioning

Virtual provisioning requires a correctly configured and licensed virtual machine host that is

discovered and visible in Systems Insight Manager. Run either ESX or Hyper-V on the virtual machine

host. You can also manage Integrity VM using infrastructure orchestration (see “Setting up an

Integrity virtual machine network” (page 41)).

For more information, see the HP BladeSystem Matrix How-To Guide: ESX Host Provisioning at the

following website:

http://www.hp.com/go/matrixoe/docs

For virtual logical server provisioning to perform correctly, infrastructure orchestration limits the

number of virtual logical servers that are sent concurrently to hypervisors for provisioning. The limit

is determined by the value of the corresponding hypervisor max.concurrent.requests attribute

in the hpio.properties file located in ..\Program Files\HP\Matrix infrastructure

orchestration\conf.

The following table shows the default values for each hypervisor type. Increasing the default values

for ESX and Integrity VM might cause virtual logical server provisioning to fail unexpectedly.

Can this value be safely increased?Default number of virtual maximum concurrent requestsHypervisor

Noesx.max.concurrent.requests=10ESX

Yes, if SCVMM is not used.

Increase this value to 10 to improve

performance.

hyperv.max.concurrent.requests=5Hyper-V

Nointegrityvm.max.concurrent.requests=2Integrity VM

If Microsoft SCVMM templates are used to provision operating systems to Hyper-V VMs, this default value should remain

at 5.

For each virtual logical server, infrastructure orchestration supports up to 14 private disks or 15

shared disks.

Provisioning a Linux VM on Hyper-V

Matrix infrastructure orchestration supports provisioning a Linux VM on Hyper-V, but IO does not

personalize the VM. IO does not set the host name, or configure the NICs for DHCP or static IP.

After provisioning, you must personalize the Linux VM.

To enable provisioning Linux VMs on Hyper-V, perform the following steps:

1. Set the following line to true in the hpio.properties file located in ..\Program Files\

HP\Matrix infrastructure orchestration\conf. The property is set to false by

default.

skip.linux.on.hyperv.template.personalization=true

2. After provisioning, personalize the Linux VM. To do so, you can write Operations Orchestration

workflows, or you can use open source PowerShell scripts.

If you provision a Linux VM on Hyper-V and do not personalize it, and the base template is

configured with a static IP address, duplicate IP addresses may result. Without personalization,

if you configured the base OS VM with DHCP, you will not get an expected static IP address.

40 Installation and configuration