Description of problem: Cinder currently provides on per volume maximums per volume type. Instead operators should be able to set a maximum for the upper limit, and a limit derived from the size of the provisioned volume. Expected results: Operators having the ability to specify maximum rates per volume type, or apply lower limits based on a ratio of iops/bw per unit of storage. Additional info: https://blueprints.launchpad.net/cinder/+spec/capacity-based-qos
*** This bug has been marked as a duplicate of bug 1334545 ***