HP Matrix Operating Environment 7.3 Update 1 Release Notes

whether the results are full or partial. Additionally, you can change the analysis interval

to a time period where all of the data is more likely to be available.

Matrix infrastructure orchestration

Matrix infrastructure orchestration runs on an x64 Windows CMS.

Enabling Matrix infrastructure orchestration provisioning support of Linux

VMs on Hyper-V

NOTE: The hpio.properties value

skip.linux.on.hyperv.template.personalization allows Linux VMs on

Hyper-V, but it is deprecated. See “Skipping automated OS customization” (page 18)

for information on allowing Linux VMs on Hyper-V.

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. As of the 7.3 release, 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.

1. Enable the Skip OS Customization check box

Set allow.skip.os.customization = true in hpio.properties. This

enables a per-server-group Skip OS Customization check box to appear in 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. Ensure appropriate OS customization is done (perhaps via an Operations

Orchestration workflow attached to the service template).

Choose fabrics when auto-generating storage pool entries through Matrix

infrastructure orchestration

When auto-generating storage pool entries from Matrix infrastructure orchestration, if

there is more than a single pair of fabrics to choose from, Matrix infrastructure

orchestration determines the pairs to use. To set the preferred list of fabrics to use during

the auto-generation of storage pool entries, add the SPM_AUTO_PREFERRED_FABRICS

property to the lsa.properties file.

Suggested action

Add the following property to the lsa.properties file:

SPM_AUTO_PREFERRED_FABRICS=FabricA,FabricB,FabricC:FabricD

Fabrics separated by ":" are redundant pairings.

For information on defining prefixes, see “Define prefix used for host names on the

storage array when provisioning storage” (page 19)

If the storage is not redundant, Matrix tries to find storage using the fabrics in the list

in the order that they appear. If the storage is redundant, then Matrix only tries the

redundant fabric pairings in the order that they appear.