4.7. Disassociating a QoS specification from volume types
You can disassociate a Quality of Service (QoS) specification from a volume type when you no longer want the QoS limits to be applied to volumes of that volume type.
You can either disassociate a specific volume type, or all the volumes types when more than one volume type is associated to the same QoS specification.
If a volume is already attached to an instance, then the QoS limits are only removed from this volume when the volume is detached and then reattached to this instance.
Prerequisites
- You must be a project administrator to create, configure, associate, and disassociate QoS specifications.
Procedure
Access the remote shell for the
openstackclientpod from your workstation:$ oc rsh -n openstack openstackclientDisassociate the volume types associated with the QoS specification:
To disassociate a specific volume type associated with the QoS specification:
$ openstack volume qos disassociate <qos_spec_name> --volume-type <volume_type>-
Replace
<qos_spec_name>with the name or ID of the QoS specification. You can run theopenstack volume qos listcommand to list the name and ID of all the QoS specifications. -
Replace
<volume_type>with the name or ID of the volume type associated with this QoS specification. You can run thecinder type-listcommand to list the name and ID of all the volume types.
-
Replace
To disassociate all volume types associated with the QoS specification:
$ openstack volume qos disassociate <qos_spec_name> --all
Verify that the QoS specification has been disassociated:
$ openstack volume qos listThe Associations column of this QoS specification should either not contain the specified volume type or should be empty when all the volume types were disassociated.
Exit the
openstackclientpod:$ exit