HP Matrix Operating Environment 7.1 Release Notes

Global Workload Manager (gWLM)
Minor issues
Using gWLM 7.1 to manage shared Integrity VM guests on HPVM 6.x can fail when the entitlements
are being set by gWLM. The failure can cause critical gWLM events in HP SIM.
Suggested action
Install the patch PHSS_43165 on the managed node (only on the HPVM host) to be managed by
gWLM. The patch can be downloaded from the website http://itrc.hp.com. After downloading
the patch, stop gwlmagent on the node, install the downloaded patch depot and restart gwlmagent.
Infrastructure orchestration
Infrastructure orchestration runs on an x86/x64 Windows CMS.
Limitations
Import VM technology preview
Matrix OE infrastructure orchestration includes a technology preview of a new feature that allows
you to import an existing VMware ESX/ESXi virtual machine into a newly created IO service
containing a single server group. The technology preview allows early access use in non-production
configurations; future releases will contain full support.
To enable this feature, set the property show.importvm.button=true and set cost values (if
applicable) in the hpio.properties file, installed in the default location at C:\Program
Files\HP\Matrix infrastructure orchestration\conf\hpio.properties. With
this property enabled, the Import button is displayed on the infrastructure orchestration console
Services tab.
NOTE: Deleting the IO service created from an imported VM also deletes the backing VM.
Following are the limitations of the import VM feature.
• Allows the import of a VMware ESX or ESXi virtual machine
• Does not allow the import of Hyper-V and Integrity VM virtual machines
• Does not allow the import of cloud servers or physical servers
• Does not allow the import of linked clone VMs, VMs with RDM disks, or VMs with multiple
datastores
• The Import VM operation is accessible through the user interface, and not through the API or
CLI
• The Add Server and Edit Server operations are not enabled for the imported VM service
• The imported VM service cannot be DR protected
• The imported VM service cannot have Operations Orchestration workflows assigned to it
Cross-technology logical servers are not supported by infrastructure orchestration
Cross-technology logical servers are not supported by Matrix OE infrastructure orchestration. Only
logical servers created or imported in Matrix OE logical server management, using Create→Logical
Server or Tools→Logical Servers→Import, can be moved from physical to virtual or virtual to
physical. A logical server created in infrastructure orchestration (by deploying a service template)
cannot be managed as a cross-technology logical server. For example, if a physical logical server
is created in infrastructure orchestration, it cannot be moved to a virtual machine using logical
server management. Similarly, if a virtual logical server is created in infrastructure orchestration,
it cannot be moved to a server with Virtual Connect using logical server management.
Global Workload Manager (gWLM) 19