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

Skipping automated OS customization
By default, after infrastructure orchestration deploys an OS to a server, it automatically customizes
(personalizes) the OS by setting the host name, IP addresses, netmask, default gateway, and other
attributes as appropriate. Automatic OS customization can be skipped by performing the actions
noted below. These actions allow the service template architect to design service templates that
use OS images intended to be customized outside of Matrix OE, such as when deploying Linux
VMs onto Hyper-V. When the skip customization feature is used, customization of the deployed
VM is no longer performed by Matrix, and becomes the responsibility of the architect to ensure
that the VM is configured properly (perhaps via an Operations Orchestration workflow attached
to the template).
1. Enable the Skip OS Customization check box. Set allow.skip.os.customization =
true in the hpio.properties file. This enables a per-server-group Skip OS Customization
check box to appear in infrastructure orchestration designer.
2. Select the Skip OS Customization check box. In Designer, navigate to Configure Server
Group→Software→1. Select Operating System. Select the Skip OS Customization check box.
3. After provisioning, personalize the deployed VM. To do so, you can write Operations
Orchestration workflows, or you can use PowerShell scripts.
If you provision a server and do not personalize the OS, you might experience duplicate,
unexpected, or unknown hostnames or IP addresses. For example, if you provision a Linux
VM on Hyper-V, and the base template is configured with a static IP address, duplicate IP
addresses can result. Without personalization, if you configured the base OS VM with DHCP,
you will not get an expected static IP address.
For supported operating systems, see the HP Insight Management Support Matrix at http://
www.hp.com/go/matrixoe/docs.
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.
Using static IPv6 addresses
Matrix infrastructure orchestration supports managing IPv6 addresses. An administrator can use
IPv4, IPv6, and dual stack address assignment types to create addresses for a service. Matrix
infrastructure orchestration can manage one IPv4 and one IPv6 address for each network interface
in a created service. Matrix OE must use IPv4 to communicate with the VM host or vCenter; however,
a guest server can use IPv6 addressing.
Configuring an environment for virtual provisioning 45