yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53445
[Bug 1599488] [NEW] [RFE] Enhance Quota API calls to return resource usage per tenant
Public bug reported:
The existing Neutron Quota API call [1] misses the option to fetch
'in_use' values for each type of quotable resources, alongside with
their quota limits. Consequently, Horizon web app has to request a list
of every resource that is quotable [2], which is pretty inefficient. The
desired feature on the Neutron side would be to support 'in_use' return
values in call [1], so that it behaves similar to [3, 4]. Whether or not
the 'reserved' return values (again, see [3, 4]) should be supported in
the same call is out of the scope of this particular feature request,
but it certainly won't hurt if reserving quotable resources makes sense
for Neutron.
[1] http://developer.openstack.org/api-ref-networking-v2-ext.html#listQuotasForTenant
[2] https://github.com/openstack/horizon/blob/10.0.0.0b1/openstack_dashboard/usage/quotas.py#L313-L336
[3] http://developer.openstack.org/api-ref-blockstorage-v2.html#showQuota
[4] http://developer.openstack.org/api-ref-compute-v2.1.html#listDetailQuotas
** Affects: neutron
Importance: Undecided
Assignee: Sergey Belous (sbelous)
Status: New
** Tags: quotas rfe
** Tags added: quotas rfe
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1599488
Title:
[RFE] Enhance Quota API calls to return resource usage per tenant
Status in neutron:
New
Bug description:
The existing Neutron Quota API call [1] misses the option to fetch
'in_use' values for each type of quotable resources, alongside with
their quota limits. Consequently, Horizon web app has to request a
list of every resource that is quotable [2], which is pretty
inefficient. The desired feature on the Neutron side would be to
support 'in_use' return values in call [1], so that it behaves similar
to [3, 4]. Whether or not the 'reserved' return values (again, see [3,
4]) should be supported in the same call is out of the scope of this
particular feature request, but it certainly won't hurt if reserving
quotable resources makes sense for Neutron.
[1] http://developer.openstack.org/api-ref-networking-v2-ext.html#listQuotasForTenant
[2] https://github.com/openstack/horizon/blob/10.0.0.0b1/openstack_dashboard/usage/quotas.py#L313-L336
[3] http://developer.openstack.org/api-ref-blockstorage-v2.html#showQuota
[4] http://developer.openstack.org/api-ref-compute-v2.1.html#listDetailQuotas
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1599488/+subscriptions
Follow ups