openstack/neutron
Code Issues Proposed changes

Merge "doc for quota details extension"

Browse Source
This commit is contained in:
Jenkins 2017-09-19 16:04:34 +00:00 committed by Gerrit Code Review
commit 917063a0ce
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/contributor/internals/quota.rst
View File

@ -55,7 +55,7 @@ High Level View
There are two main components in the Neutron quota system: There are two main components in the Neutron quota system:
* The Quota API extension; * The Quota API extensions.
* The Quota Engine. * The Quota Engine.
Both components rely on a quota driver. The neutron codebase currently defines Both components rely on a quota driver. The neutron codebase currently defines
@ -76,6 +76,11 @@ Please note that the current behaviour when deleting a project quota is to reset
quota limits for that project to configuration defaults. The API quota limits for that project to configuration defaults. The API
extension does not validate the project identifier with the identity service. extension does not validate the project identifier with the identity service.
In addition, the Quota Detail API extension complements the Quota API extension
by allowing users (typically admins) the ability to retrieve details about
quotas per project. Quota details include the used/limit/reserved
count for the project's resources (networks, ports, etc.).
Performing quota enforcement is the responsibility of the Quota Engine. Performing quota enforcement is the responsibility of the Quota Engine.
RESTful API controllers, before sending a request to the plugin, try to obtain RESTful API controllers, before sending a request to the plugin, try to obtain
a reservation from the quota engine for the resources specified in the client a reservation from the quota engine for the resources specified in the client