HP Matrix Operating Environment 7.3 Release Notes

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 51)
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.
In the above example, for non-redundant storage, Matrix tries FabricA, FabricB, FabricC and
FabricD in that order. For redundant storage, Matrix tries the FabricC & FabricD pairing.
NOTE: The fabrics listed in this property are used by all auto-generated storage pool entries from
Matrix infrastructure orchestration on that CMS. It cannot be set up to only be used by some users
or some organizations. If storage is not found after going through the fabrics defined in this list,
then all known fabrics are tried.
Define prefix used for host names on the storage array when provisioning storage
When provisioning storage through Matrix IO or Matrix OE, using SPM, a prefix can be defined
for the host names that are created on the storage array. This can be defined by adding or modifying
the property SPM_HOSTNAME_PREFIX within the lsa.properties file. This prefix can be 5
characters or less due to host name limitations on the storage arrays. If not selected, the default
prefix used is “LSM”. The rest of the host name will be the initiator WWN defined within the host
definition in order to guarantee name uniqueness.
Minor issues
Provisioning of HP Integrity VMs with NPIV data disk fails
HP Integrity VMs with NPIV disks can be created through Matrix infrastructure orchestration. But
the disks must be added after service creation through an Add disk operation. Any attempt to add
NPIV data disks before service creation will fail and display the error message on the IO Requests
screen:
Workflow execution failed for operation type EditLS: could not delete:
[com.hp.vse.lsa.datamodelV72.LsaFcConnection#44]
HP Matrix Operating Environment infrastructure orchestration 51