HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

8. Change the level from Required to Recommended. Verify that Use existing volume is selected.
9. Click OK to exit the Edit Requirement – Resource Existence dialog.
10. Click OK (or Apply).
Physical storage provisioning
Matrix infrastructure orchestration displays the storage volumes available for provisioning on the
infrastructure orchestration console Storage tab. The volumes that are also storage pool entries are
also visible on the Matrix OE visualization – Modify Logical Server Storage Pools page.
During service provisioning, infrastructure orchestration searches for an appropriate storage pool
entry and can create one if none is found. The auto-generated storage pool entries are fulfilled
through SPM using either pre-provisioned catalog storage pool entries or on-demand provisioned
storage.
For each physical logical server, infrastructure orchestration supports up to 16 data disks.
Service template defines storage by “Selecting a storage template”
HP Storage Provisioning Manager (SPM) allows storage architects to create storage templates,
which are used for all storage provisioning requests. Using SPM, storage architects can encapsulate
their policies in storage template definitions, specifying various requirements (for example, a specific
RAID level, a capacity constraint, or the recommended or required use of thin provisioning).
These storage templates can be viewed and selected in infrastructure orchestration designer when
defining a logical disk in a service template, or you can define logical disk attributes manually. In
either case, the storage fulfilling the request might be pre-provisioned or newly created on-demand
through SPM.
The selected storage template requirements are combined with any user modified or added
requirements to formulate the goal that the provisioning process meets.
NOTE: The storage template specification is used to fulfill storage through SPM only if there are
no existing storage pool entries that match the requirements.
To force infrastructure orchestration to use SPM for storage instead of an existing storage pool
entry, ensure that there are no available matching storage pool entries. One way to do so is to
select a tag for the storage that is not associated with any storage pool entry, but is associated
with volumes or storage pools in SPM.
In SPM, storage architects create a set of storage templates representing their policies with required
degrees of protection (for example, Windows boot disks, HP-UX boot disks, LUNs for transaction
logs, LUNs for various applications). SPM can create storage volumes on-demand and perform
appropriate presentation and zoning steps. Storage architects determine the extent by which they
want to use on-demand provisioning capabilities by defining the “Resource Existence” requirement
as a template read-only requirement. If “Resource Existence” is set to required and “Use Existing
Volume” is selected and required, then on-demand provisioning is not used, and only existing
volumes are used to satisfy the request.
156 Matrix infrastructure orchestration storage management