HP Matrix Operating Environment Software - Manual (Page 125)

On-demand provisioning is supported for HP EVA/P6000 and HP 3PAR Storage Systems,
and can include automated SAN zoning within 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 134) .
•
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. Users then request storage though storage services, and SPM returns a list of service
candidates corresponding to existing volumes. Volume selection policy is controlled by the
storage architect by means of template requirements.
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
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 already have
volumes from SPM, while new storage pool entries are fulfilled through SPM (falling back to manual
provisioning if there are no suitable volumes, either pre-provisioned or created on-demand). 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.
At service creation, infrastructure orchestration is able to choose one or more storage pool entries
from the storage pool. It then 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.
Static SAN volume automation through multi-initiator NPIV 125