HP Matrix Operating Environment Software - Manual (Page 21)

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. 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.
IMPORTANT: If you configured secondary CMSs for use in a federated CMS environment, ensure
that each SAN storage array in the federation is managed by only one HP Storage Provisioning
Manager.
HP recommends that you select the HP Matrix Default Storage Template, and optionally define
additional attributes, when configuring physical storage in a service template.
Each CMS contains its own HP Matrix Default Storage Template, and these templates are
independent of each other. The default storage template shown in infrastructure orchestration
designer is the default storage template on the primary CMS. However, storage auto-provisioning
is based on the template found on the CMS that deploys the template.
If you do not select the HP Matrix Default Storage Template and instead select a user-defined
storage template, the same SPM Server is used for all volume definitions. If a SAN storage array
is managed by multiple SPMs or CMSs, unpredictable results can occur.
Configuring HP Operations Orchestration
The HP Operations Orchestration engine is embedded in Matrix Operating Environment. Using
HP Operations Orchestration Studio, you can create custom workflow processes and attach them
to
infrastructure service templates at well defined points in the IO provisioning process, such as
during pre- and post-provisioning of infrastructure components.
Matrix infrastructure orchestration defines integration points for Operations Orchestration workflows
that run each time a specific operation is invoked, regardless of the template or infrastructure
service involved in the operation. Matrix infrastructure orchestration provides basic or sample
Operations Orchestration workflows for some of these operations; however, it also allows for the
modification or creation of new workflows for these operations to allow the integration of
infrastructure orchestration into the business processes.
Template architects can associate one or more Operations Orchestration workflows with a particular
template. These workflows can run before or after a particular lifecycle operation allowing the
corresponding adjustment of the target server.
For more information on Operations Orchestration, see the HP Operations Orchestration Software
Guide at
Matrix Operating Environment Information Library .
Configuring Operations Orchestration system properties
Operations Orchestration is installed automatically during new installations of Insight Management.
If you are upgrading Insight Management, including infrastructure orchestration, you must perform
manual steps to upgrade Operations Orchestration.
Configuring HP Operations Orchestration 21