Bug 1042424

Summary:	[RFE][neutron]: Rate limiting for Quantum API
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/api-rate-limiting
Whiteboard:	upstream_milestone_none upstream_status_not-started upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:29:24 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:14:14 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/api-rate-limiting.

Description:

The goal of this blueprint is to implement rate limits for the Quantum API in a way similar to what has been done for the Openstack API. 

From the Openstack API developer guide:
"Rate limits are specified in terms of both a human-readable wild-card URI and a machine-processable regular expression. The human-readable limit is intended for displaying in graphical user interfaces. The machine-processable form is intended to be used directly by client applications."

Rate Limiting will be implemented as a separate module in the Quantum pipeline. We will explore whether work in the Openstack-commons project can be reused (or alternatively volunteer for rate limiting in Openstack-commons and use it in Quantum)



Specification URL (additional information):

None