HP Matrix Operating Environment 7.3 and 7.3 Update 1 Infrastructure Orchestration User Guide

• oo.custom.server.action.display.name.2= Enable VPN
• oo.custom.server.action.display.name.3= Sync database
NOTE: The workflows you specify must be valid, existing OO workflows. If they are not, the
menu options will not appear. For more information, see “Custom OO workflow menu items do
not appear on Server Actions menu” (page 227).
Execute custom server actions by selecting Run custom server action from the Server Actions menu,
and then selecting the desired action. The Server Actions menu is available in infrastructure
orchestration console, infrastructure orchestration self service portal, or the infrastructure orchestration
organization portal. You can also execute custom server actions using the API/CLI.
NOTE: For more information about using API/CLI, see the HP CloudSystem Matrix/Matrix
Operating Environment Integration Interfaces API and CLI Operations Reference Guide available
at http://www.hp.com/go/matrixoe/docs
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 increased scalability for service catalog-based auto-provisioning (up to 12,000 ProLiant
virtual machines and 6,000 HP Integrity 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 a secondary CMSs)
A federation can contain up to five CMSs. The recommended configuration is:
• One primary CMS with up to 2,000 managed nodes
• Up to four secondary CMSs with up to 2,500 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 on the following website:
http://www.hp.com/go/matrixoe/docs
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.
24 Installation and configuration