Another feature provided by Cinder is the ability to define and manage classes of service for volumes. Like volume encryption, Quality of Service (QoS) in Cinder is configured by volume type. By default, you can define values for minimum, maximum, and burst IOPS.
To configure volume QoS, you will need the following information:
openrc
file with appropriate credentials for the environment (you need to be an administrator)openstack
command-line clientFor our example, these will be as follows:
High IOPS
both
500
For Cinder volumes to use QoS, an administrator needs to perform two steps: first, define the specification, and second, to associate the specification with a volume type.
To create and assign a QoS specification, use the following steps:
openstack volume qos list --print-empty
We currently don't have any QoS defined:
openstack volume qos create --consumer both --property maxIOPS=500 "High IOPS"
This will bring back the following output:
openstack volume qos list -c Name -c Consumer -c Properties -f table
This will bring back the following output:
openstack volume qos associate "High IOPS" "High IOPS"
QoS specifications are defined within Cinder using the openstack volume qos
set of commands. When creating a QoS specification, you can specify where QoS is applied as well as the value to set it at. Currently, you can specify a static set of minimum, maximum, and burst IOPS, and a scaling set of IOPS.
The static values break down as follows:
Scaling IOPs then, define the amount to change the static values for each additional gigabyte of volume size.
3.147.78.137