HP Matrix Operating Environment Software - Manual (Page 150)

4. If the boot disk reservation still cannot be satisfied, Matrix OE attempts to automatically create
an SPE that will be automatically fulfilled though SPM, containing the boot disk and the private
data disks.
Result: If the boot disk is not fulfilled, the request pauses and raises an email alert (using an
Operations Orchestration workflow) requesting manual storage provisioning for the boot and
data disks. If the service contains shared data disks, Matrix OE will create separate SPEs as
appropriate and attempt to fulfill though SPM.
If the boot/data disk requests are fulfilled, but SPM has indicated the need for manual zoning,
the request pauses and raises an email alert (using an Operations Orchestration workflow)
requesting manual storage zoning for the appropriate disks. The storage administrator zones
the storage and edits the XML files for SPM. The request can then be resumed. At that time,
Matrix OE uses the appropriate SPEs (and does not repeat the algorithm above).
5. If the boot disk has been reserved, but the data disk reservation still cannot be satisfied, Matrix
OE attempts to automatically create an SPE for the data disk(s) that will be fulfilled through
SPM.
Result: If data disk(s) are still not fulfilled, pause the request and raise an email alert (using
an Operations Orchestration workflow) requesting manual storage provisioning for the data
disks.
If the boot/data disk requests are fulfilled, but SPM has indicated the need for manual zoning,
the request pauses and raises an email alert (using an Operations Orchestration workflow)
requesting manual storage zoning for the appropriate disks. The storage administrator zones
the storage and edits the XML files for SPM. The request can then be resumed. At that time,
Matrix OE uses the appropriate SPEs (and does not repeat the algorithm above).
6. For all paused requests for storage provisioning, the administrator can manually create the
storage pool entry and try to fulfill it manually or through SPM (which could match the request
to pre-provisioned storage or use on-demand provisioning, if enabled). Requests paused for
storage zoning can be resumed once the storage administrator has manually zoned the storage
and edited the SPM XML files to reflect that zoning.
NOTE: When a request that was paused for manual storage provisioning is continued,
infrastructure orchestration re-enters the reservation algorithm, applying the same logic to satisfy
both the boot and data disk requirements for the logical server.
When the fulfillment is through SPM, IO monitors the job status. When complete, it uses that storage
in the service request. When a request that was paused for manual storage zoning is continued,
the infrastructure orchestration algorithm uses the appropriate SPEs already fulfilled through SPM
(which are now zoned and suitable for use).
Using the preceding steps, the following priority is observed when trying to satisfy the storage
requirements:
1.
Try: Static SAN volume automation through multi-initiator NPIV (each volume in a separate
SPE)
2. Fall back to: Dynamic SAN volume automation via LUN masking (combine volumes in SPEs)
a.
Search for existing SPEs
b. If none are found, auto-generate SPEs and attempt to fulfill through SPM
3. Fall back to: Manual storage provisioning
150 Matrix infrastructure orchestration storage management