HP Matrix Operating Environment 7.2 Infrastructure Orchestration User Guide

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.
See the HP Insight Management Support Matrix at http://www.hp.com/go/matrixoe/docs for
supported Linux guest operating systems.
Setting up virtual machine networks
Network names are correlated across hypervisor and Virtual Connect technologies to allow an
infrastructure service to be provisioned with logical servers of different types configured on the
same network.
VMware vDS (vNetwork Distributed Switch) is supported in infrastructure orchestration.
• IO can provision logical servers to ESX hosts that are preconfigured with connectivity to a vDS
switch.
• Port groups configured on the vDS switch are visible on the infrastructure orchestration console
Networks tab as virtual networks.
• When vDS networks are discovered into the IO inventory, they can be selected and used
when provisioning a service with one or more virtual servers.
All additional configuration of vDS occurs outside of IO using vCenter, including configuring virtual
machine rate limiting, security, and monitoring of the port runtime states.
NOTE: Do not rename a network that is in use by IO services. If a network is renamed using a
tool outside of IO, services shown by IO will appear to be using the old network. The old network
will remain in the network inventory, but will no longer have a physical or virtual source and cannot
be used to provision new services.
Setting up an ESX virtual machine network
To add a network for use by the virtual machines provisioned through infrastructure orchestration:
1. Open VMware Infrastructure Client, enter the IP and credentials of the vCenter Server, and
then click Login.
2. For each ESX/ESXi virtual machine host in the ESX cluster, do the following:
a. In the left navigation pane, select the virtual machine host.
b. Select the Configuration tab.
c. Click Networking.
d. Click Add Networking.
e. For connection type, select Virtual Machine, then click Next.
f. Depending on the network configuration of the virtual machine host, either select an
existing virtual switch or select Create a virtual switch, and then click Next.
g. In Port group properties, enter a name for the network in Network Label, and depending
on the network configuration of the virtual machine host, enter a VLAN ID.
h. Click Next.
3. Click Finish.
Repeat the process for each network.
Configuring an environment for virtual provisioning 41