[openstack-dev] [nova] Let's kill quota classes (again)
mriedem at linux.vnet.ibm.com
Thu Dec 15 14:00:00 UTC 2016
On 12/15/2016 3:11 AM, Andrey Volkov wrote:
> I totally agree with Matt than `os-quota-class-sets` is inconsistent.
> It has that hardcoded default class can't be changed.
> API call is documented neither Nova nor Cinder (has the same API for
> With defaults in the configuration I have some concerns:
> - As it was mentioned before, possibly we need to update configs in
> several places.
We're moving quotas to the API and we're going to stop doing the
reservation/commit/rollback race dance between API and compute nodes per
So that would mean you really only need the default quota configuration
on the API node, so I don't think this is as much of a problem after
> - To make changes be applied we need to restart service, possibly SIGHUP
> can help
> but I'm not sure.
I'd think we could make these mutable config options so we could pickup
the changes without restarting the service.
> Alternatives I see are:
> - Update `os-quota-sets` and give it possibility to work with defaults.
> - Use external centralized quota service on which the work's doing actively.
> Please see  spec for limits in keystone and doc  having information
> how it can be applied in Nova and Cinder.
>  https://review.openstack.org/#/c/363765/
More information about the OpenStack-dev