Add support for qos_specs feature to 3PAR drivers

Registered by Kurt Martin on 2014-02-06

We've added a new qos_specs object to Cinder that allows creation and management of qos settings separate from volume-types. Now instead of embedding the qos info in the extra-specs of the volume-type we associate the desired qos-spec to a volume-type.

The capability to check for this and use it needs to be added to the 3PAR drivers. The default method of the reading extra-specs will still work and be a valid mode of setting QoS, however if the association is present it will override any settings in the extra-specs.

Additional 3PAR QOS capabilities will also be added as part of this blueprint, they include:
minIOPS - minimum IOPs per second
minBWS - minimum bandwidth per second
latency - The QOS I/O target latency
priority - the QOS scheduling priority (high, normal, low)

Blueprint information

Status:
Complete
Approver:
John Griffith
Priority:
Low
Drafter:
Kurt Martin
Direction:
Approved
Assignee:
Kurt Martin
Definition:
Approved
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
Kurt Martin on 2014-02-06
Completed by
Kurt Martin on 2014-02-21

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/add-qosspec-support-to-3par-drivers,n,z

Addressed by: https://review.openstack.org/72481
    Update 3PAR drivers to pass cert test

Addressed by: https://review.openstack.org/72811
    Add support for qos_specs feature to 3PAR drivers

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.