HP Matrix Operating Environment Software - Manual (Page 148)

For instructions about how to change “Resource Existence” to enable on-demand provisioning for
all manually specified storage, see
“Enabling on-demand storage provisioning in SPM” (page 144) .
NOTE: Any edits made to the HP Matrix Default Storage Template will apply to all manually
specified storage.
If you select a storage template when configuring a service template in infrastructure orchestration
designer, the default requirements of the storage template define the desired attributes of the storage
you are configuring. You can modify these values and add additional values that were not defined
by the storage template.
When defining SPM storage templates, use the Description field to summarize the requirements
(for example, if the template supports only RAID 1 and RAID 5). That description is visible to the
architect in infrastructure orchestration designer. When using a specific SPM storage template in
IO, be aware of the storage template's capacity, RAID, and tag requirements (included in the
description field). Do not specify values that conflict with these requirements or the storage may
not be correctly provisioned.
The storage requirements that you can manually define are as follows:
•
Name of the disk.
•
Individual Disk Size is the size for the disk in gigabytes (GB). For physical (SAN) disks, this
attribute is used to find a SAN disk that is at least as large as the value specified. (For physical
storage, MB x 1000 = GB.)
•
Cost per GB is the estimated cost per gigabyte in numeric form.
•
RAID Level is a specific RAID level, or Any. If you specify a RAID level, the selection is matched
against Matrix OE storage volume properties during service allocation. Only SAN volumes
with a matching RAID level are used to satisfy a provisioning of that template.
•
Disk is bootable denotes that the disk will be the boot disk for a server group.
•
Redundant SAN paths to disk denotes that the disk will have redundant paths to the disk. If
the disk is a boot disk, the selected software must be an image with embedded multi-path
software.
•
Disk is shared across servers denotes that this disk is a data disk (non-boot disk) shared between
all servers in the group.
•
Tags allow you to select or enter one or more tags from the list of tags defined in Matrix OE
logical server management. Storage tags are used to match a corresponding SAN storage
volume in the Matrix OE inventory (or the SPM storage catalog). The tag set is not pre-defined
or limited by IO.
•
Additional Tags allows you to enter a comma-separated list of tags.
NOTE: During service allocation, any specified tags are used to find a suitable allocation
match with an existing Matrix OE storage pool entry or passed through to SPM for fulfillment
of a newly created storage pool entry. Only SAN volumes with matching tags (either
pre-provisioned or created on demand) are used to satisfy a provisioning of that IO template.
Leaving tag fields empty expands the provisioning options for that IO template.
Virtual storage provisioning
The infrastructure orchestration designer Virtual Storage component Config tab allows you to
configure a bootable disk or data disk for each server in the server group that is connected to the
virtual storage.
NOTE: All storage volumes for a virtual machine logical server must be part of the same datastore.
File volumes are created on the same disk as the virtual machine's configuration file.
148 Matrix infrastructure orchestration storage management