HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

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.
At service creation, infrastructure orchestration selects one or more storage pool entries from the
storage pool. Existing storage pool entries visible to infrastructure orchestration are already
associated with storage volumes (through manual fulfillment, or fulfillment though SPM). If there is
no suitable storage pool entry and SPM is being used, infrastructure orchestration will create a
storage pool entry and attempt to fulfill through SPM. If SPM fulfillment fails, infrastructure
orchestration indicates the need for manual storage provisioning. Given a storage pool entry,
infrastructure orchestration examines the initiator WWNs associated with each of the storage pool
entries and performs the required assignment to the server in order to enable server visibility within
the SAN to the set of SAN volume targets defined by the storage pool entries.
This process has the advantage of the ability to separate the boot and data storage visibility to the
server during OS provisioning without requiring any access to the existing SAN management
interfaces. The approach is limited to Virtual Connect managed servers only.
NOTE: For non-Integrity servers, NPIV is enabled by default.
Manually enable NPIV for Integrity servers that use both private and shared disks for storage auto
provisioning. Set npiv.integrity.enabled=true in ..\Program Files\HP\Matrix
infrastructure orchestration\conf\hpio.properties to enable NPIV support on
Integrity servers. (The npiv.integrity.enabled property is set to false by default.)
Dynamic SAN volume automation
In a more dynamic environment, pre-provisioned SAN volumes can have their LUN masking adjusted
appropriately, or SAN volumes can be provisioned on-demand with suitable LUN masking.
146 Matrix infrastructure orchestration storage management