Bug 1042413

Summary:	[RFE][neutron]: used resource count in tenant quotas
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-neutron	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:	Ofer Blaut <oblaut>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	chrisw, markmc, nyechiel, yeylon
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/tenant-used-quotas
Whiteboard:	upstream_milestone_next upstream_status_needs-code-review upstream_definition_superseded
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 10:29:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 22:11:44 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/tenant-used-quotas.

Description:

Add the used resource count when getting quotas information for a tenant.

Actually, there's no api call to get the information on used resources.
The goal is to return the count of used resources of a tenant.

There's already a way to show quotas of a tenant. And the payload contains these values:

* floatingip
* network
* port
* router
* security_group
* security_group_rule
* subnet

It is possible to count every resource. I propose to add these values to the quotas payload:

* used_floatingips
* used_networks
* used_ports
* used_routers
* used_security_group_rules
* used_security_groups
* used_subnets

It should then be easier to check for used resources.

Specification URL (additional information):

None

Comment 2 Nir Yechiel 2014-03-05 08:35:07 UTC

Updating based on upstream status

Comment 3 Nir Yechiel 2015-03-19 10:29:58 UTC

This RFE was automatically opened to track status of upstream development. At this point we see no reason to keep track of this in Red Hat bugzilla, thus closing it.