Clean-up quotas/limits usages
Bug #1227169 reported by
Julie Pichon
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
When we moved from quotas to limits, we moved from a centralised "all quotas-related operations should be in openstack_
Additionally, quotas are still in use in places, sometimes both limits and quotas are used in the same class (e.g. BaseUsage) and it's unclear whether the quotas code is now redundant and should be removed, or if it makes sense to use it in some case. The return output from quotas and limits are different (dictionary vs list).
To post a comment you must log in.
this might be helpful refernce:
nova sample limits results....
{"limits": {"rate": [], "absolute": {"maxServerMeta": 50, "maxPersonality": 5, "maxImageMeta": 50, "maxPersonality Size": 10240, "maxSecurityGro upRules" : 20, "maxTotalKeypairs": 100, "totalRAMUsed": 8192, "totalInstances Used": 8, "maxSecurityGro ups": 10, "totalFloatingI psUsed" : 0, "maxTotalCores": -1, "totalSecurityG roupsUsed" : 0, "maxTotalFloati ngIps": 10, "maxTotalInstan ces": 40, "totalCoresUsed": 8, "maxTotalRAMSize": 204800}}}
sample results for volumes.....
{"limits": {"rate": [], "absolute": {"maxTotalVolum eGigabytes" : 3000, "maxTotalVolumes": 20}}}