Nova's API has the ability to create "quota classes", which are
basically limits for a set of resource types. There is something called
the "default quota class" which corresponds to the limits in the
CONF.quota section. Quota classes are basically templates of limits to
be applied if the calling project doesn't have any stored
project-specific limits.
Has anyone ever created a quota class that is different from "default"?
I'd like to propose deprecating this API and getting rid of this
functionality since it conflicts with the new Keystone /limits endpoint,
is highly coupled with RAX's turnstile middleware and I can't seem to
find anyone who has ever used it. Deprecating this API and functionality
would make the transition to a saner quota management system much easier
and straightforward.
Also, I'm apparently blocked now from the operators ML so could someone
please forward this there?
Thanks,
-jay
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
