Operating Environment Software Owner manual

example, a Network Capability requirement with a value of “Automated Zoning” matches
only networks that are capable of performing automated zoning.
RAID Level requirement
The RAID Level requirement specifies the RAID level of volumes matching this requirement. The
RAID level values represent the general concepts of each RAID level, such as the redundancy and
space efficiency characteristics. The actual RAID level chosen on the device is determined from a
mapping of the general concepts to the implementation of RAID on the array.
Resource Existence requirement
The Resource Existence requirement is a provisioning time only requirement that matches
resources which already exist, rather than ones which could be created. The Volume resource class
is the only resource class recognized because it is the only resource type creatable in SPM at this
time. Using this requirement with “Must not” enforcement specifies that matching volumes must be
created via on-demand provisioning and will not be pre-existing (pre-provisioned) resources.
Service Deactivation Policy requirement
The Service Deactivation Policy requirement specifies the actions to be taken on
deactivating the service. The available policies are:
• No Action—On service deactivation, nothing is done. All SAN zoning, volume data, and
volume presentation are left as it was. The server consuming the storage is still be able to
access it after the service is deleted.
• Quarantine Resources—On service deactivation, the volume within the service is
quarantined from server access, ensuring servers can no longer read or write the data, but
the volume and data are preserved on the array. Volume mapping and masking is removed,
and any SAN zoning is deleted from the SAN. The storage volume is put into a quarantined
state in which it is not provisionable by future requests in SPM. It is the responsibility of the
storage administrator to move the data to a suitable archive before returning the volume to
an enabled state or deleting it manually.
• Destroy Data—On service deactivation, the storage volume is deleted, destroying the data
it contains and makes the capacity available for future data services to provision. Any SAN
zoning that was performed is also removed. Use this policy only in situations where archiving
processes are in place and have saved all necessary data before deleting the service.
• Recycle—On service deactivation, if the storage volume's presentation was changed, the
volume is unpresented. If the storage volume was created, the storage volume is deleted,
destroying the data it contains, and the capacity is returned to its containing pool for future
service provisioning requests. Any SAN zoning that was performed is also removed. Use this
policy only in situations where archiving processes are in place and you have saved all
necessary data before deleting the service.
NOTE: In a Matrix OE environment, the policy should always be recycle. Other policies
can cause unexpected behavior.
Storage Capability requirement
The Storage Capability requirement specifies the capabilities that a matching service must
be able to perform after it is provisioned, subject to available capacity. If a capability is not
specified as required, it is optional whether a provisioned service is able to perform the operation
after it is provisioned. For example, a Storage Capability requirement with a value of “Thin
Provisioning” matches only arrays that are capable of creating thinly-provisioned volumes.
28 Storage service policy