HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

IMPORTANT: If you configured secondary CMSs for use in a federated CMS environment, ensure
that each SAN storage volume is managed by only one HP Storage Provisioning Manager. (A
storage array can be shared by multiple SPMs.)
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 volume
is managed by multiple SPMs or CMSs, unpredictable results can occur.
NOTE: Physical storage volumes attached to a virtual server group (RDM volumes) cannot be
provisioned through SPM. They are represented in Matrix OE by manually created storage pool
entries, not using the SPM storage catalog.
Service template defines storage by “Specifying desired attributes”
During service provisioning, infrastructure orchestration attempts to find a suitable storage pool
entry using the attributes specified on the Config tab. If one cannot be found and SPM is in use, a
storage pool entry can be auto-generated and fulfilled (using the SPM storage template selected
by the architect in infrastructure orchestration designer, or the HP Matrix default storage template
if the architect specified disk attributes). The desired attributes specified in the Config tab are
combined with any requirements that are defined in the template chosen in infrastructure
orchestration designer. The desired attributes specified in the service template are combined with
any requirements that are defined in the HP Matrix Default Storage Template.
The predefined HP Matrix Default Storage Template contains minimal constraints, allowing any
capacity, RAID level, presentation requirement, or tags, and requires pre-provisioned storage.
Using SPM, the HP Matrix Default Storage Template can be edited or copied to make additional
templates.
By default, “Resource Existence” is set to required in the HP Matrix Default Storage Template, so
only existing volumes (pre-provisioned storage) are used to satisfy all manually defined storage
requests. This includes specifying the logical disk information for a service template (by selecting
Specify desired attributes) or manually creating a storage pool entry in Matrix OE visualization
logical server management and fulfilling it through SPM.
For instructions about how to change “Resource Existence” to enable on-demand provisioning for
all manually specified storage, see “Enabling on-demand storage provisioning in SPM” (page 154).
NOTE: Any edits made to the HP Matrix Default Storage Template will apply to all manually
specified storage.
If you select a storage template when configuring a service template in infrastructure orchestration
designer, the default requirements of the storage template define the desired attributes of the storage
you are configuring. You can modify these values and add additional values that were not defined
by the storage template.
When defining SPM storage templates, use the Description field to summarize the requirements
(for example, if the template supports only RAID 1 and RAID 5). That description is visible to the
architect in infrastructure orchestration designer. When using a specific SPM storage template in
IO, be aware of the storage template's capacity, RAID, and tag requirements (included in the
description field). Do not specify values that conflict with these requirements or the storage may
not be correctly provisioned.
Physical storage provisioning 157