HP Matrix Operating Environment 7.3 Release Notes

NOTE: For Matrix OE API enhancement details, see “Matrix OE API change details”
(page 61).
Create and configure a Matrix infrastructure orchestration network (createSubnet,
deleteSubnet).
Creating and deleting subnets (createSubnet, removeSubnet)
Adding and removing network interfaces
(addNetworkInterfaceToLogicalServerGroup,
removeNetworkInterfaceFromLogicalServerGroup)
Modifying the costs of provisioned services (modifyService)
Controlling and listing the provisioning type (thin, thick, or unspecified) for virtual
disks (addNewDiskToLogicalServerGroup, getService,
getLogicalServerGroup)
Controlling whether a server reboot is allowed to occur when adding a disk, changing
memory, or adding CPUs (editLogicalServers)
a new EXTERNAL IPAddressAssignmentType to direct Matrix infrastructure
orchestration to not assign an IP address to a network interface.
Unregistering vacant VM hosts (unregisterVmHost).
HP Capacity Advisor adds a new “Systems with a possible infinite loop query. For detailed
information about this query, see “HP Capacity Advisor enhancement details” (page 67).
HP Integrity Virtual Server Manager version 6.3 enhancements include:
Enabled offline vPar migration
Enabled Guest type conversion (VM to vPar and VPar to VM).
HP Global Workload Manager (gWLM) ) support for resource management of mixed mode
Virtualization Services Platform (VSP) simultaneously running vPars and Integrity virtual
machines.
Matrix OE support in VMware VXLAN environments
Matrix OE supports VMware VXLAN environments (since the Matrix OE 7.2 Update 2 release)
with specific prerequisites and considerations as outlined below. Correctly configured and used,
Matrix OE can provision and import VMs in an environment using VMware VXLAN. Specifically,
Matrix OE is able to provision infrastructure using virtual networks from vShield Manager, configured
under dvSwitches. Customers can use IO to display networks from vCenter, configure those networks
in IO, assign networks to organizations, and provision infrastructure using service templates.
Prerequisites to configure the VMware VXLAN environment
1. Ensure that all of the ESX clusters which need to be part of the VXLAN are in the same VMware
vSphere datacenter. Add all the clusters of the datacenter to VXLAN Networking.
2. All hosts in a cluster must be connected to a distributed switch to enable VXLAN networking
(same VDS name).
3. Use vShield Manager to configure the VXLAN scope, networking, and port groups; create a
single scope with all the clusters defined to a datacenter. Consult the VMware documentation
for details.
4. When adding an ESX host to vCenter, HP recommends that you configure it using the FQDN
and not the IP address.
Enhancements 9