HP Matrix Operating Environment 7.3 Release Notes

IPv4 for dual stack. For more information, see the IPv6 Support in Insight Management
white paper.
◦ Thin provisioning can be specified when defining disks for a virtual server or adding a
new disk to an existing service.
◦ Support for hiding unused FlexNICs from the OS is enabled by default (assuming the VC
Domain Group supports it, requiring VC 4.10 or later). It can be controlled for individual
logical servers in Matrix OE visualization or disabled entirely using the
hpio.properties file (hide.unused.flexnics).
◦ Support remote use of an external OO 10.01 server in addition to the 9.07 version; the
bundled OO version is 9.07. For more information, see the Upgrading HP Operations
Orchestration included with Matrix OE to HP Operations Orchestration 10.01 white
paper.
◦ Ability to skip OS customization via a new check box in Matrix infrastructure orchestration
designer (useful when customization is being performed by an OO workflow).
◦ Virtual Machine provisioning and lifecycle
VMware and Hyper-V VMs can use multiple data stores (boot and data disks on
different storage volumes). Microsoft doesn’t support VM Linked Clone using multiple
data stores.
–
– Support for VMware and Hyper-V VMs with thin provisioning through new
Provisioning Type choice for disks (Thick, Thin, Unspecified). Not supported for
shared disks, raw devices, or Hyper-V VMs using Server Automation, IC server
provisioning, or manual OS deployment
– Ability to change VMware and Hyper-V VM CPU and memory without reboot (given
hypervisor/OS support)
– Ability to add disks to an activated logical server using Matrix OE visualization (to
be seen at next activation), supported for VMware, Hyper-V, and Integrity VMs
– Ability to add disks to a VMware VM in a Matrix IO service without reboot (given
hypervisor/OS support)
– Ability to add or remove VM network interfaces from Matrix IO services.
Administrators and users with permission can add and remove network interfaces
to server groups of already provisioned services. Permissions can be controlled
through the hpio.properties file. The primary network interface cannot be
removed and there are implications for removing the boot or deployment network.
(Compromised ability for compliance tracking and erase disk job on service delete
cannot run. )
– Matrix IO support for the creation and management of Integrity vPar guests (the HP
Integrity VM and VPars virtualization supports the guest types of “Integrity VM” and
“Integrity vPar”).
– Matrix IO support for Direct I/O (DIO) networks for Integrity VM and vPars (Integrity
only feature).
– Matrix support for online memory addition or deletion for Integrity vPars (specification
of Base Memory and Float Memory fields in service templates or when manually
creating logical servers).
◦ Additional administrator customization capabilities for Matrix infrastructure orchestration
graphical user interfaces:
– The administrator can require acceptance of license terms to provision services
(specifying a URL for the license terms, the name of the link label, and wording for
Enhancements 7