nova/releasenotes/notes/recheck-quota-conf-043a5d6057b33282.yaml
Dan Smith eab1d4b5cc Count server groups to check quota
This changes server groups from a ReservableResource to a
CountableResource and replaces quota reserve/commit/rollback with
check_deltas accordingly.

A new configuration option [quota]/recheck_quota has also been added
to control whether quota should be checked a second time after
resources have been created, to prevent allowing quota to be exceeded
as a result of racing requests.

Co-Authored-By: melanie witt <melwittt@gmail.com>

Part of blueprint cells-count-resources-to-check-quota-in-api

Change-Id: If87c84001673e5e463136435327044cc06f87a17
2017-06-08 00:35:37 +00:00

13 lines
729 B
YAML

features:
- |
A new configuration option ``[quota]/recheck_quota`` has been added to
recheck quota after resource creation to prevent allowing quota to be
exceeded as a result of racing requests. It defaults to True, which makes
it impossible for a user to exceed their quota. However, it will be
possible for a REST API user to be rejected with an over quota 403 error
response in the event of a collision close to reaching their quota limit,
even if the user has enough quota available when they made the request.
Operators may want to set the option to False to avoid additional load on
the system if allowing quota to be exceeded because of racing requests is
considered acceptable.