On 12/16/2016 4:00 PM, Jay Pipes wrote:
So, we could do that, we already have the quota_classes table and the
os-quota-class-sets REST API, and as mentioned the only usable thing
that goes in there is overriding global default quota.
Would you suggest we drop the global quota limit configuration options
and simply populate the quota_classes table with a 'default' quota class
and the limits from the config in a DB migration, then drop the config
options?
Yeah, I think that's the best long-term strategerization.
-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
OK, I've noted your point in the spec review, maybe we can discuss the
options at the PTG while we're all in the same room. I think we have
good options either way going forward so I'm happy.
--
Thanks,
Matt Riedemann
__________________________________________________________________________
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
