The QoS Specs Implementation
Associate qos_specs with volume type.
Associate target qos specs with specific volume type.
specs_id – qos specs ID to associate with
type_id – volume type ID to associate with
VolumeTypeNotFound – if volume type doesn’t exist
QoSSpecsNotFound – if qos specs doesn’t exist
InvalidVolumeType – if volume type is already associated with qos specs other than given one.
QoSSpecsAssociateFailed – if there was general DB error
Creates qos_specs.
specs – Dictionary that contains specifications for QoS
Expected format of the input parameter:
{ 'consumer': 'front-end', 'total_iops_sec': 1000, 'total_bytes_sec': 1024000 }
Marks qos specs as deleted.
‘force’ parameter is a flag to determine whether should destroy should continue when there were entities associated with the qos specs. force=True indicates caller would like to mark qos specs as deleted even if there was entities associate with target qos specs. Trying to delete a qos specs still associated with entities will cause QoSSpecsInUse exception if force=False (default).
Marks specified key of target qos specs as deleted.
Disassociate qos_specs from all entities.
Disassociate qos_specs from volume type.
Get all non-deleted qos specs.
Get all associations of given qos specs.
Retrieves single qos specs by id.
Update qos specs.
specs –
existing specs.
’total_iops_sec’: 500, ‘total_bytes_sec’: 512000,}
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.