Open Stack

On 12/15/2016 09:00 AM, Matt Riedemann wrote:
> On 12/15/2016 3:11 AM, Andrey Volkov wrote:
>> Hi,
>>
>> 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
>> quotas).
>>
>> 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
> this spec:
>
> https://specs.openstack.org/openstack/nova-specs/specs/ocata/approved/cells-count-resources-to-check-quota-in-api.html
>
> 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
> that change.
>
>> - 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.

For problems with placing data like this as configuration options, see 
the hassle we went through in making the allocation_ratio options into 
fields stored in the DB...

Better long-term to have all this kind of configuration live in a data 
store (not a config file) and be exposed via an HTTP API.

Best,
-jay