QoSSIOC automation

The NetApp Element Plug-in for vCenter Server allows, as an optional setting, automatic quality of service (QoS) based on storage I/O control (SIOC) settings of all VMs on a standard datastore.

QoS and SIOC integration (QoSSIOC), which can be enabled for any standard datastore, runs a scan of all SIOC settings on all associated VMs. QoSSIOC adjusts QoS values on standard Element volumes when virtual machine events occur, such as power on or power off events, guest restarts or shutdown, or reconfiguration activity. The QoSSIOC service uses the sum of all SIOC reservations or shares and the sum of IOPS limits to determine minimum and maximum QoS for the underlying volume of each datastore. A configurable burst factor is also available.

The following items should be considered before using QoSSIOC automation:

The following dialog box appears during QoSSIOC configuration for a datastore:

Shows the QoSSIOC dialog box
Enable QoS & SIOC

Enables the automatic monitoring of SIOC values for each VMDK on a datastore and sets QoS values for the underlying volume according to those values.

Burst Factor

Multiplier of the sum of SIOC IOPS limit values from each VDMK that determines the burst IOPS contribution for the underlying volume.

Override Default QoS
Enables the use of Shares and Limit IOPS values. These values can be used when SIOC settings for each VM are set to default.
The contribution of minimum IOPS from each VDMK if the SIOC settings are set to default.
Limit IOPS
The contribution of maximum IOPS from each VDMK if the SIOC settings are set to default.
When SIOC settings for a VMDK are at the default shares level of Normal and the default IOPS limit of Unlimited, the Shares and Limit IOPS values contribute toward the total QoS for the underlying volume. If the SIOC settings for the VMDK are not at default levels, SIOC shares contribute to Min QoS and SIOC IOPS limit values contribute to Max QoS for the underlying volume.
Note: It is possible to set a reservation value through vSphere API. If a reservation value is set for a VMDK, shares are ignored and the reservation value is used instead.