Excerpts from Fox, Kevin M's message of 2015-12-16 16:05:29 -0800: > Yeah, as an op, I've run into a few things that need quota's that just have > basically hardcoded values. heat stacks for example. its a single global in > /etc/heat/heat.conf:max_stacks_per_tenant=100. Instead of being able to tweak > it for just our one project that legitimately has to create over 200 stacks, > I had to set it cloud wide and I had to bounce services to do it. Please > don't do that. > > Ideally, it would be nice if the quota stuff could be pulled out into its own > shared lib (oslo?) and shared amongst projects so that they don't have to > spend much effort implementing quota's. Maybe then things that need quota's > that don't currently can more easily get them. >
You had to change a config value, once, and that's worse than the added code complexity and server load that would come from tracking quotas for a distributed service? __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
