Hello, I am requesting an exception for the Horizon "Cinder QOS Specs" blueprint[1]. The blueprint addresses adding QOS Spec management in Horizon and completely covers the Cinder QOS CLI commands. There are 4 patches that implement this blueprint, the first of which has already landed in Juno. The remaining 3 patches are functionally complete and have had several positive reviews from both Horizon and Cinder team members. Here is what is covered in the 4 patches: Patch 1 [2] - Displays a table of all defined QOS Specs. Patch 2 [3] - Adds ability to edit values of already defined QOS Specs. Patch 3 [4] - Adds ability to create and delete QOS Specs, as well as create and delete values associated with a QOS Spec. Patch 4 [5] - Adds ability to associate a QOS Spec with a Volume Type. My feeling is that all of the patches need to be implemented in order for this to be truly useful. Without all of the patches, the user will still be forced to use the Cinder CLI. Are there any Horizon core members who would be willing to sponsor this exception? Thanks for your consideration, Richard Hagarty, Developer at Hewlett-Packard IRC handle: rhagarty [1]: https://blueprints.launchpad.net/horizon/+spec/cinder-qos-specs [2]: https://review.openstack.org/#/c/111408 [3]: https://review.openstack.org/#/c/112369/ [4]: https://review.openstack.org/#/c/113038/ [5]: https://review.openstack.org/#/c/113571/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140905/2e8a1fb8/attachment.html>