Open Stack

This doesn't particularly hit our main quota issue. IMO templates could
easily be implemented with a script. Also, the more I think about it, they
probably should be implemented that way, since this kind of policy often
gets overly complex when you try to implement a general solution, and the
script solution is just fine for us.

If you're interested in quotas, we have a completely different problem with
quotas that is a real showstopper for us. We have a really large dynamic
range in resource quantities for our different instance types. (for
example, we have 3 orders of magnitudes in the range of memory
configurations). This makes quotas pretty useless for us as they are
currently implemented, since you can't represent limits for these different
kinds of resources in the same quota. Something like per-instance-type
quotas would at least allow us to restrict users to a fixed number of
instances of a given type, bypassing the current quota mechanism.

Just my 2c.
 -nld


On Fri, Apr 4, 2014 at 2:57 PM, Cazzolato, Sergio J <
sergio.j.cazzolato at intel.com> wrote:

>  Hi all,
>
> I'd like to know your thoughts regarding Quota Management... do you think
> that would be useful for operators to have quota templates? For instance,
> as an operator you could define templates with quota values based on the
> kind of users you usually manage and then to use these templates to set up
> the user quotas in one step.
>
> Thanks
>
>
>
> *Sergio Juan Cazzolato*
>
> *Intel Software Argentina *
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140404/0dc1a57b/attachment.html>