Configuring a federated cms environment – HP Matrix Operating Environment Software User Manual
Page 18
The preceding are hpio.properties entries that infrastructure orchestration self service portal,
organization administrator portal, designer, and console read directly.
Configuring a federated CMS environment
A Matrix infrastructure orchestration federated CMS environment is an environment in which multiple
management servers cooperatively share the responsibility for managing a larger number of
resources than can be managed by a single server.
A new infrastructure orchestration installation is configured as a primary CMS, and is ready to
control a federated CMS environment when secondary CMSs are installed and configured.
An infrastructure orchestration federated CMS environment:
•
allows up to four times increased scalability for service catalog-based auto-provisioning (up
to 10,000 virtual machines), over the current single-CMS limitation of 2500 managed virtual
machines
•
contains one primary CMS running infrastructure orchestration, and one or more secondary
CMSs running Matrix Operating Environment (infrastructure orchestration cannot be installed
on secondary CMSs)
A federation can contain up to five CMSs. The recommended configuration is:
•
one primary CMS with up to 1200 managed nodes
•
up to four secondary CMSs with up to 2200 managed nodes each
The primary CMS manages the aggregated resources of all CMSs. Matrix infrastructure orchestration
must be installed only on this server. A secondary CMS is a CMS that participates in the federation,
where resources exist and provisioning from infrastructure orchestration may occur, but infrastructure
orchestration does not run directly on secondary CMSs.
To execute infrastructure orchestration provisioning across multiple CMSs, infrastructure orchestration
on the primary CMS uses the secondary CMSs logical server management, virtual machine
management, and other supporting software layers.
For more information, see the HP Matrix Operating Environment Federated CMS Overview white
paper at
.
Manually enabling federated CMS in new installations
Federated CMS is enabled by default in new installations. However, during the installation
procedure, if the CMS IP address is not resolved to the Fully Qualified Domain Name (FQDN),
one of the following errors is displayed:
Failed to enable HP Insight Orchestration Federated mode.
HP Matrix OE infrastructure orchestration was successfully installed but the federated CMS feature was not
enabled.
If you performed a new installation of Insight Management 7.0, and federated CMS was not
successfully enabled during the installation, perform the following steps to configure a federated
CMS environment.
WARNING!
Do not manually enable federated CMS if you are upgrading to Insight Management
7.0 from an earlier release. If your environment contains existing infrastructure orchestration
services, enabling federated CMS after an upgrade will cause these existing services to fail.
Contact HP for information about enabling federated CMS after an upgrade to 7.0.
1.
Set up and verify DNS on primary CMS and secondary CMSs
In a federated environment, Domain Name Service (DNS) is used to resolve CMS hostnames
to IP addresses.
•
On the primary CMS, forward and reverse DNS lookups must resolve for each secondary
CMS using the FQDN of each system.
18
Installation and configuration