HP Matrix Operating Environment Software - Manual (Page 147)

These storage templates can be viewed and selected in infrastructure orchestration designer when
defining a logical disk in a service template, or you can define logical disk attributes manually. In
either case, the storage fulfilling the request might be pre-provisioned or newly created on-demand
through SPM.
The selected storage template requirements are combined with any user modified or added
requirements to formulate the goal that the provisioning process meets.
NOTE: The storage template specification is used to fulfill storage through SPM only if there are
no existing storage pool entries that match the requirements.
To force infrastructure orchestration to use SPM for storage instead of an existing storage pool
entry, ensure that there are no available matching storage pool entries. One way to do so is to
select a tag for the storage that is not associated with any storage pool entry, but is associated
with volumes or storage pools in SPM.
In SPM, storage architects create a set of storage templates representing their policies with required
degrees of protection (for example, Windows boot disks, HP-UX boot disks, LUNs for transaction
logs, LUNs for various applications). SPM can create storage volumes on-demand and perform
appropriate presentation and zoning steps. Storage architects determine the extent by which they
want to use on-demand provisioning capabilities by defining the “Resource Existence” requirement
as a template read-only requirement. If “Resource Existence” is set to required and “Use Existing
Volume” is selected and required, then on-demand provisioning is not used, and only existing
volumes are used to satisfy the request.
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.
Service template defines storage by “Specifying desired attributes”
During service provisioning, infrastructure orchestration uses the SPM storage template specified
in the service template definition or, if logical disk properties were manually specified, the HP
Matrix Default Storage Template that is predefined in SPM and integrated in Matrix OE. 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.
Physical storage provisioning 147