[openstack-dev] [openstack][cinder]A discussion about quota update lower than current usage.
duncan.thomas at gmail.com
Fri Jul 10 07:28:06 UTC 2015
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" <sxmatch1986 at gmail.com> wrote:
> 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 resources any more.
> So there have been 'bug' reported and code patch committed, I knew
> it may be
> inappropriate as 'bug fix', but just want to optimize this API of
> updating quota.
> We are proposing to add an option argument which is named 'force' in
> request body.
> Of course the default value is True that means admin can adjust the quota
> lower then
> current usage as same as what we did now. When the force is False, that
> will occur
> a Validation and return 400 Bad Request if the update value is lower than
> current usage.
> I wonder to know folks' opinions and suggestions about this change to see
> if this is value to merge this patch.
> Best Wishes For You!
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev