os-used-limits API extension should optionally include the reserved count
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Eoghan Glynn |
Bug Description
By omitting the reserved count from the total<Resource>Used elements in the response, the os-used-limits API extension prevents the caller from gaining the most accurate picture of the actual headroom.
For example, if the current instances quota is 10, the in_use count is 9 and an instance creation is in-flight, then the values for maxTotalInstances and totalInstanceUsed will imply that there is headroom to create a further resource. In fact this will not be the case, as the single reserved instance will prevent a new instance being spun up.
We should support a query param to control whether the reserved count is included:
GET /v2/<TENANT_
GET /v2/<TENANT_
GET /v2/<TENANT_
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
Fix proposed to branch: master /review. openstack. org/17805
Review: https:/