hi Duncan
Sorry for the long delay. IMHO, the purpose of this change is let the
cinder have ability to control admin's action. If admin only want to limit
the users not to create resources any more, fine, use the option argument
'skip_validation=False to update the quota limit and just equal the
The problem is, if you reject the request to lower quota unless the usage
is under the new quota, you've got an inherently racy process where the
admin needs to communicate with the tenant to say 'Stop using some of your
quota while I reduce it', which is no less complicated than 'I've reduced
Hi, Mike
I'm not sure we really don't need any change about this feature. At least,
some end users I faced to think there should be changed
IMHO, there is a main problem that some users whom I faced to can't
understand: What's the purpose that admin reduce quota lowner than existing
usage?
Ah, I apologise, I missed the but where it defaults to force=true. I
withdraw the objection.
I've no strung feelings about the change either way, in that case.
On 10 Jul 2015 10:58, Gorka Eguileor gegui...@redhat.com wrote:
On Fri, Jul 10, 2015 at 10:28:06AM +0300, Duncan Thomas wrote:
That
On Fri, Jul 10, 2015 at 10:28:06AM +0300, Duncan Thomas wrote:
That is a semantic change to the api that will break anybody who has
tooling expecting the current behavior. Since there are perfectly sensible
uses of the current behavior, that is not a good thing.
Hi Duncan,
I don't think that
That is a semantic change to the api that will break anybody who has
tooling expecting the current behavior. Since there are perfectly sensible
uses of the current behavior, that is not a good thing.
On 10 Jul 2015 07:33, hao wang sxmatch1...@gmail.com wrote:
Cinder now doesn't check the
Hi, Duncan
As Gorka said, we are trying not to impact default API behavior, just give
a choice to client that it can restrict cloud admin to update quota lower
than current usage.
2015-07-10 16:47 GMT+08:00 Duncan Thomas duncan.tho...@gmail.com:
Ah, I apologise, I missed the but where it
Cinder now doesn't check the existing resource when user lower the quota.
It's reasonable for admin can adjust the quota limit to lower level than
current usage.
But it also bring confusion that I have received to end user, they saw the
current usage
was more than limit, but they can't create
