Supported volume type extra-specs

Edit online

The extra_specs that PowerVC supports when you are creating or updating volume types by using OpenStack APIs for supported storage providers. PowerVC uses the term storage template instead of volume type.

Volume type options when creating a Hitachi provider

Table 1. Options for volume type to be used to create a Hitachi volume
Option Key name Description Values

Host name

capabilities:volume_ backend_name

Name of the host where volume is created.

The user-defined name for the host.

Storage Pool

drivers:storage_pool

Storage pool where volume is created.

Name of the storage pool.

Display Name

drivers:display_name

The display name for the volume type.

  

Target ports

hbsd:target_ports

The ports on the array that should be used to connect volumes to virtual machines.

Comma separated list of port names. For example, CL5-B,CL6-B.

Volume type options when creating an IBM® System Storage DS8000 provider

Table 2. Options for volume type to be used to create a DS8000 volume
Option Key name Description Values

Host name

capabilities:volume_ backend_name

Name of the host where volume is created.

The user-defined name for the host.

Port Group

drivers:port_group:<port_group_name>

The port group and list of ports to include in the port group.

Comma separated list of storage port WWPNs to include in this port group. This list overrides any existing whitelists or blacklists. The values specified for port-group-name can be obtained from the values specified for drivers:target_port_groups.

Target Port Groups

drivers:target_port_groups

The list of port groups for the volume type.

Comma separated list of port group keys defined in drivers:port_group.

Storage Pool

drivers:storage_pool

Storage pool where volume is created.

Name of the storage pool.

Display Name

drivers:display_name

The display name for the volume type.

  

Storage Pool IDs

drivers:storage_pool_ids

Optional. Comma separated list of DS8000 pool IDs in which to create a volume. The volume is created in the storage pool that has the most free space and an available slot in an LSS. If this value is present in the extra spec, it takes precedence during volume creation.

A list of existing DS8000 pool IDs. For example: P0,P1,P2,P3

Storage Logical Subsystems

drivers:storage_lss_ids

Optional. Comma separated list of DS8000 logical subsystem IDs.

A list of DS8000 logical subsystem IDs. For example: 00,01,0A,0B
Target Whitelist drivers:target_whitelist Optional. Comma separated list of target WWPNs used for zoning during NPIV deploy. A list of target WWPNs. For example, 5005076802232abc,5005076802232abd

Volume type options when creating an IBM Storwize provider

Table 3. Options for volume type to be used to create a Storwize volume
Option Key name Description Values

Host name

capabilities:volume_ backend_name

Name of the host where volume is created.

The user-defined name for the host.

Port Group

drivers:port_group:<port_group_name>

The port group and list of ports to include in the port group.

Comma separated list of storage port WWPNs to include in this port group. This list overrides any existing whitelists or blacklists. The values specified for port-group-name can be obtained from the values specified for drivers:target_port_groups.

Target Port Groups

drivers:target_port_groups

The list of port groups for the volume type.

Comma separated list of port group keys defined in drivers:port_group.

Storage Pool

drivers:storage_pool

Storage pool where volume is created.

Name of the storage pool.

Display Name

drivers:display_name

The display name for the volume type.

  

I/O group

drivers:iogrp

Optional. The I/O group in which to allocate a volume.

A string that lists the name.

Mirror Pool

drivers:mirror_pool

Specifies the name of the pool to establish a mirror copy in. The value of mirror_pool can be either a local mirror or the stretch cluster mirror. When this property is set, volumes are created with a mirror copy in the pool specified by mirror_pool.

A string that lists the name.

Real

drivers:rsize

The capacity that is allocated to the volume copy.

For a thin-provisioned volume: Percent of virtual capacity for thin provisioning.

For all other volumes, specify -1. This tells PowerVC to create the volume without thin-provisioning.

Replication

No longer used.

No longer used.

No longer used.

Multipath

drivers:multipath

Specifies whether to enable multipath zoning. When enabled, the Storwize® volume driver uses all available WWPNs from all of the I/O groups in the storage controller to attach the volume to the virtual machine. Enabling multipath causes each WWPN that is visible on the fabric to be zoned to the virtual machine.

1: Enable multipath.

0: Do not enable multipath. This is the default setting.

Automatically expand

drivers:autoexpand

Supported only when creating a thin provisioned provider.

Specifies whether to automatically increase the real capacity of the volume.

1: Automatically expand.

0: Do not automatically expand.

Grain size

drivers:grainsize

Optional. Supported only when creating a thin provisioned provider.

Volume grain size.

Volume grain size, in KB.

Warning Threshold

drivers:warning

Supported only when creating a thin provisioned provider.

Generate volume capacity warnings for this volume when the specified threshold is met.

Percent of virtual capacity.

Compression

drivers:compression

Supported only when creating a thin provisioned provider.

Specifies whether to create a compressed volume.

1: Compress the volume.

0: Do not compress the volume.
Target Whitelist drivers:target_whitelist Optional. Comma separated list of target WWPNs used for zoning during NPIV deploy. A list of target WWPNs. For example, 5005076802232abc,5005076802232abd
I/O throttle qos:IOThrottling

When SVC volume_type or storage template is configured with this extra_specs, then I/O rate is configured on volumes that are created based on this template.

Optional. Positive integer value for I/O rate.

 For example, qos:IOThrottling= 50, to set the I/O rate.
qos:IOThrottling_unit

When SVC volume_type or storage template is configured with this extra_specs, then I/O rate is configured with the unit as specified on the volume.

Optional. Values can be iops or mbps. Default value is iops.

For example, qos:IOThrottling_unit=iops or mbps, to set the I/O rate as I/Os or MBps respectively.

Volume type options when creating an IBM XIV provider

Table 4. Options for volume type to be used to create an IBM XIV volume
Option Key name Description Values

Host name

capabilities:volume_ backend_name

Name of the host where volume is created.

The user-defined name for the host.

Port Group

drivers:port_group:<port_group_name>

The port group and list of ports to include in the port group.

Comma separated list of storage port WWPNs to include in this port group. This list overrides any existing whitelists or blacklists. The values specified for port-group-name can be obtained from the values specified for drivers:target_port_groups.

Target Port Groups

drivers:target_port_groups

The list of port groups for the volume type.

Comma separated list of port group keys defined in drivers:port_group.

Storage Pool

drivers:storage_pool

Storage pool where volume is created.

Name of the storage pool.

Display Name

drivers:display_name

The display name for the volume type.

  
Target Whitelist drivers:target_whitelist Optional. Comma separated list of target WWPNs used for zoning during NPIV deploy. A list of target WWPNs. For example, 5005076802232abc,5005076802232abd

Volume type options when creating an EMC VNX provider

Table 5. Options for EMC VNX providers
Option Key name Description Values

Provisioning

storagetype:provisioning

Provisioning method to use for the volume
thick (default)
Allocates storage space when initially provisioning it. The allocated storage space is guaranteed. Therefore, the logical unit will not fail at a later time due to a lack of available storage.
thin
Allocates space in the underlying storage pool to the logical unit as it is required.
deduplicated
Removes duplicate copies of data. The system-level settings must be configured on the VNX system.
compressed
Data is compressed as it is written to disk. Provides only the space needed. The system-level settings must be configured on the VNX system.

Port Group

drivers:port_group:<port_group_name>

The port group and list of ports to include in the port group.

Comma separated list of storage port WWPNs to include in this port group. This list overrides any existing whitelists or blacklists. The values specified for port-group-name can be obtained from the values specified for drivers:target_port_groups.

Target Port Groups

drivers:target_port_groups

The list of port groups for the volume type.

Comma separated list of port group keys defined in drivers:port_group.

Tiering

storagetype:tiering

Tiering method to use. This cannot be set for deduplicated volumes.
StartHighThenAuto (default)
Initially, data is placed on the highest available tier. Subsequently, data movement depends on its activity level.
Auto
Volume slices are relocated solely based on their activity level after all slices with Highest available tier or Lowest available tier are relocated.
HighestAvailable
FAST VP prioritizes volume slices with this setting above all other settings.
LowestAvailable
Slices of these volumes are kept on the lowest storage tier available, regardless of activity level.
NoMovement
FAST VP still relocates within a tier, but does not move volumes up or down from their current position.
Target Whitelist drivers:target_whitelist Optional. Comma separated list of target WWPNs used for zoning during NPIV deploy. A list of target WWPNs. For example, 5005076802232abc,5005076802232abd

Volume type options when creating an EMC VMAX provider

Table 6. Options for EMC VMAX providers
Option Key name Description Values

Striped member count

storagetype:stripecount

The number of storage blocks to stripe data across.

This option applies to VMAX2 devices only. VMAX2 support is deprecated and will be removed in a later release.
Integers 1 and higher. The default is 1, which means that volumes are made of concatenated members, beginning with a single member. A value of 2 or higher results in striped composite volumes being created.
Note: If the volume size might be increased later, specify 1. You cannot increase the size of striped composite volumes.

FAST policy name

drivers:fastpolicy

Optional. The Fully Automated Storage Tiering (FAST) policy name to associate with the template, if any. Volumes created with a FAST policy are controlled by that policy and their data might be moved between storage tiers for better performance.

This option applies to VMAX2 devices only. VMAX2 support is deprecated and will be removed in a later release.

String containing the name of the pre-defined FAST policy on the VMAX array.

Service Level Objective

drivers:slo

Optional. Only available on SMI-S managed VMAX3 series arrays that support Service Level. It is not supported for REST-based VMAX providers. Volumes will be created with the specified service level. Service levels are associated with maximal and average response times that can be expected for various workload storage I/O operations.

Valid values are: 'Bronze', 'Silver', 'Gold', 'Platinum', 'Diamond', and 'Optimized.'
Target Whitelist drivers:target_whitelist Optional. Comma separated list of target WWPNs used for zoning during NPIV deploy. A list of target WWPNs. For example, 5005076802232abc,5005076802232abd

Workload type

drivers:workload

Optional. Only available on SMI-S managed VMAX3 series arrays, and only applicable if drivers:slo is also specified. It is not supported for REST-based VMAX providers. This workload type string further qualifies the workload to specify the type of I/O expected for it and whether it is replicated (mirrored).

Valid values are: 'DSS_REP', 'DSS', 'OLTP', 'OLTP_REP', and 'NONE'.

Example: update a volume type so that volumes are not automatically expanded

This operation updates a volume type so that volumes are not auto-expanded.

Request URI and body
PUT 
/v3/{tenant_id}/types/{volume_type_id}/extra_specs/drivers:autoexpand

{
 "drivers:autoexpand":"0"
}