HP Matrix Operating Environment Software - Manual (Page 22)

wrapper.java.additional.15=-Dfed.cms.name=CMS-blue.hp.com
6. Verify hostname and primary CMS FQDN
a.
On the primary CMS, open a prompt dialog
b. Enter mxgethostname and note the hostname that is returned
c. In Systems Insight Manager, select Options
→Federated CMS Configuration…. The name
of the primary CMS should be the same as the one returned by mxgethostname.
Support for a rolling upgrade of a CMS federation
Matrix OE infrastructure orchestration 7.1 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.
During a rolling upgrade, a CMS running Matrix OE 7.1 supports basic operations against a
secondary CMS running 7.0. Not all 7.1 features are expected to work against a 7.0 CMS.
IMPORTANT: The primary CMS must be upgraded first.
The following new features in 7.1 are not supported during a rolling upgrade:
•
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)
Create user groups on secondary CMSs
On all secondary CMSs, manually create the IO user groups.
1.
Select Start
→Administrative Tools→Computer Management.
2. Expand Local Users and Groups.
3. Add the following user groups using steps a through c.
a.
Right-click Groups.
b. Select New Group and create the HPIO_Administrators group.
c. Repeat steps a and b to create the groups: HPIO_Architects and HPIO_Users.
NOTE: Ensure that all CMSs in a federated CMS environment have their user accounts
synchronized by creating the same user accounts on primary and secondary CMSs.
Configuring resources on the secondary CMSs
Matrix infrastructure orchestration provisioning is managed through the primary CMS and executed
across all CMSs in the federated CMS environment. The IO console is run on the primary CMS
and manages resources on the primary CMS. All cloud capacity pools must be configured only
on the primary CMS.
There are two types of resources that must be configured on the secondary CMSs:
•
Every CMS in a federated CMS environment manages its own storage pool. You must create
storage pool entries on each CMS for the portability groups the CMS is managing.
•
For IO to deploy a service with Hyper-V virtual machines, you must create Insight Control
virtual machine management templates for the Hyper-V virtual machine. This configuration
must be done on the CMS that manages the Hyper-V VM Hosts. If the Hyper-V VM Hosts are
managed by a secondary CMS, you must create the virtual machine management templates
on the secondary CMS.
In the federated CMS environment, IO service templates and services are created and managed
on the primary CMS.
22 Installation and configuration