Enhanced KVM Storage QoS¶
This blueprint proposes to add support for these additonal settings to QoS specs for connected volumes.
At the moment, the Nova libvirt driver does not support setting storage IOPS limits. For this reason, some instances might exhaust storage resources, impacting other tenants.
Associate burst IOPs and bandwidth front-end QoS specs for volumes exported through Cinder, which will be handled on the hypervisor side. This is in addition to the existing IOPs and bandwidth caps.
Set block IO size for IOPs to volumes exported through Cinder.
Set IOPs and bandwidth burst limits and block IO sizes for instance attached disks by using Cinder extra specs
Cinder attached volumes can have additional QoS specs assigned. Front-end QoS specs should be applied by Nova when the volume is attached. These are applied per volume.
This blueprint proposes additional per volume QoS specs that will be specified using Cinder volume extra specs. The libvirt driver will apply those IOPS and bandwidth caps to the instance disks on a per volume basis.
Additionally, this blueprint proposes adding the block IO size control using cinder volume extra specs to cinder attached volumes on a per volume basis.
Front-end volume specs will be supported only in case of volumes exported through Cinder. No QoS specs are provided for local drives provided directly by Nova.
Use case examples:
- Admin sets front-end QoS specs on a specific volume type
- cinder qos-create my-qos consumer=front-end
cinder qos-associate my-qos <volume_type_id>
cinder create <size> –volume-type <volume_type_id>
# Those QoS specs are applied when the volume is # attached to a KVM instance nova volume-attach <instance_id> <volume_id>
Available additional QoS specs, where each will add an extra line into the libvirt XML definition, specifically in the <iotune> section for each device, are:
- total_bytes_sec_max - includes read/writes
- total_iops_sec_max - includes read/writes
Data model impact¶
REST API impact¶
Other end user impact¶
As Nova supports N-1 version computes, if these new qoS specs are applied to a compute node running Queens, these new specs will be ignored. No error message will be provided from the Queens node.
Existing Cinder QoS specs are documented in the Cinder Administration documentation set. 8
Allowing burst IOPs and bandwidth for certain volumes will allow some applications to better perform when required.
Other deployer impact¶
- Primary assignee:
Add burst and IO size QoS specs support in the libvirt volume driver by extending the nova/virt/libvirt/volumes/ block volume drivers to pass the new properties of a volume to LibvirtConfigGuestDisk via the qos_specs’ in the `connection_info dict.
Extend the LibvirtConfigGuestDisk class to add the disk burst limits of a disk device 2
Existing tests will ensure that the quest XML is formatted correctly assuming the required versions of libvirt and QEMU are present.
The additional QoS features are described in the libvirt driver documentation 1.
Will update the Cinder Administrators Guide to add these new front-end QoS storage parameters.