HP Matrix Operating Environment 7.3 Release Notes

Support for a rolling upgrade of a CMS federation
To decrease federation downtime, Matrix OE infrastructure orchestration 7.3 includes support for
a rolling upgrade of a federated CMS environment. A rolling upgrade temporarily allows a
federation containing CMSs running different versions of Matrix OE during the upgrade process.
IMPORTANT: The primary CMS must be upgraded first.
During a rolling upgrade, a CMS running Matrix OE 7.3 supports basic operations against a
secondary CMS running 7.2. Not all 7.3 features are expected to work against a 7.2 CMS.
The following operations are not supported on a primary CMS running Matrix OE 7.3 with
secondary CMSs running 7.2:
• Manual operating system provisioning of VM guests using resources discovered on a secondary
CMS
• Provisioning a physical server group with auto-provisioned SPM volumes on a secondary CMS
• Changing the memory size or number of CPUs of an existing virtual machine
• Some chargeback operations, including detection of changes made outside of Matrix OE
(and directly in VMware, Hyper-V, OA, and so on)
Hyper-V VM hosts are moved to the IO unassigned pool after upgrade from 6.3
After an upgrade from Matrix OE 6.3 to 7.2 or later, all Hyper-V VM hosts are automatically
moved to the infrastructure orchestration Unassigned server pool. This issue does not occur after
an upgrade from Matrix OE 7.0 to 7.2 or later.
Manually move the Hyper-V VM hosts back to their original server pool in order to provision virtual
servers to Hyper-V VM hosts.
Updating IO files on a remote OO server
If you are updating from one IO version to the next (for example 7.2 to 7.2.1), and OO (Operations
Orchestration) is on a remote server, the following IO files will need to be manually updated on
the remote server:
• hpio-common.jar
• hpio-model.jar
To update these files:
1. Open Windows Explorer in the CMS and navigate to the Program Files\HP\Matrix
infrastructure orchestration\work folder.
2. Locate the folder that contains hpio-controller and open it.
3. Navigate to the webapp\WEB-INF\lib folder.
4. Locate the hpio-common.jar and hpio-model.jar files.
5. Copy these files to the desktop of the CMS.
NOTE: Do not delete or move these files, just make a copy.
6. Stop the OO RSJRAS and RSCentral services in the OO server.
7. Open Windows Explorer and navigate to the Program Files\HP\Operations
Orchestration\RAS\Java\Default\repository\lib folder.
8. Locate the hpio-loadbalancer-f5, hpio-loadbalancer-haproxy and hpio-oo
folders.
Each folder contains an old version of hpio-common.jar and hpio-model.jar that needs
to be updated.
12 Description