Migrate Horizon to use Quotas API

Registered by Eric Peterson on 2016-04-20

Horizon has a few areas which use a "limits" api. Examples include the overview page with the pie charts.

The limits API was originally used because Nova always supported limits, and quotas was viewed as an optional extension. And in most cases, the data returned was the same. This period of time was in 2013-2014, if not earlier.

Now there are more robust apis, such as cinder supporting multiple backends. When these underlying services expand their features they are using the quotas API to have the richest support of features. So in cinder's case - you can have a quota for HDD storage and another one for SSD (as an example). The limits api is old and does not contain this type of granularity.

I propose that we move our code to using quotas, and possibly have some backwards / fallback method to use the old limits method of retrieving data. This would support end users seeing more relevant info on the summary page, and admins can set more specific quotas, etc.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Eric Peterson
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Good progress
Milestone target:
None
Started by
Eric Peterson on 2016-04-21
Completed by
Rob Cresswell on 2017-02-21

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/horizon-use-quotas-api,n,z

Addressed by: https://review.openstack.org/309204
    Switch cinder to usage quotas

I think that we can get away with a smaller change, to support the new features in cinder. This still leaves some more questions around other quota apis, and also the ability for admins to set these new variable quotas from cinder.

[robcresswell 2017-02-21]
Moved to wishlist https://blueprints.launchpad.net/horizon/+spec/wishlist

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.