Operating Environment Software Instruction Manual

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 144).
• 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.
Pre-provisioned storage provisioning cannot be used if:
◦ SPM is not configured
◦ the environment contains a combination of private and shared disks without NPIV
◦ boot disks and other private disks are contained in separate storage pool entries
Storage requests can be created manually by the user or automatically by Matrix infrastructure
orchestration and submitted to SPM for storage service fulfillment. SPM can fulfill with either
on-demand or pre-provisioned storage (allowing the user to select from returned candidates, or IO
will choose the best candidate).
See the HP Storage Provisioning Manager (SPM) User Guide at http://www.hp.com/go/matrixoe/
docs for details on specific storage solution models and software versions.
After SAN volumes have been pre-provisioned, infrastructure orchestration can automate the LUN
presentation process to a server using two different approaches.
• Static SAN volume automation through multi-initiator NPIV
• Dynamic SAN volume automation
Pre-provisioned storage provisioning
by IO using SPM
Manual storage provisioning using
logical server management
✓Static (NPIV)
✓✓Dynamic (SPM)
Static SAN volume automation through multi-initiator NPIV
Using this process, SAN volumes are pre-masked to one or more initiator WWNs within the SAN,
and logical servers can support more than one initiator on each physical HBA port (multi-initiator
NPIV). Zoning is also pre-configured. The SAN volumes are then made available within Matrix
OE visualization’s storage pool as storage pool entries.
136 Matrix infrastructure orchestration storage management