HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

NOTE: Storage pool entries can be created manually, or infrastructure orchestration can create
storage pool entries automatically. In both cases, the storage pool entries can be fulfilled through
SPM using pre-provisioned volumes or on-demand provisioning (based on customer need reflected
in the storage templates defined in SPM).
Auto-generated storage pool entries are created based on the logical disk storage needs defined
in a service template and follow certain conventions (for example, use of SPM, packing multiple
volumes into the same storage pool entry, and choices of SAN fabric). If your specific storage
configuration does not follow those conventions, a manually created storage pool entry is
appropriate. For example:
• SPM is not used
• Boot volume in a separate entry from other private data volumes
• Combinations of private and shared disks without NPIV
• Multiple non-redundant disks on different fabrics
• Redundant paths to disks across unusual fabric combinations
• Mix of redundant and non-redundant volumes
• A Virtual Connect module connected to more than one SAN fabric
When Matrix is in an environment with Virtual Connect modules whose uplink ports connect
to different SANs, the auto-generation of storage pool entries may not be sufficient. Matrix
OE infrastructure orchestration will choose one representative uplink for each VC module and
thus be aware of connectivity to that SAN (and not the SANs accessible through other uplinks
on that module). In those environments the storage pool entries should be created manually
(and can still be fulfilled manually or through SPM).
Following are the types of storage provisioning available in infrastructure orchestration. The overall
system may be used with any or all of the processes combined.
• On-demand storage provisioning
The storage administrator populates the SPM catalog with arrays and storage pools, then
defines storage templates with various policies, including access to those pools. New volumes
can be carved from existing pools (by an administrator or by infrastructure orchestration)
through the use of storage services. Provisioning policy is controlled by the storage architect
using template requirements.
On-demand provisioning is supported for HP EVA/P6000 and HP 3PAR Storage Systems,
and can include automated SAN zoning within Brocade SAN environments.
NOTE: On-demand storage provisioning is disabled by default. To enable on-demand
storage provisioning, see “Enabling on-demand storage provisioning in SPM” (page 154).
• Pre-provisioned storage provisioning
The storage administrator populates the SPM catalog with arrays, storage pools and all of
the volumes that will be used to fulfill storage services, then sets up access rights for those
volumes. Volume selection policy is controlled by the storage architect by means of template
requirements.
Pre-provisioned storage is supported for HP P6000/EVA, HP P9000/XP, and HP 3PAR Storage
Systems.
145