[Openstack-operators] Rate limit an max_count
jean-daniel.bonnetot at ovh.net
Thu Sep 10 08:38:34 UTC 2015
The use case is a crossing of two
1. As user, I want to use X,000 instances, in order to accept the load increment during my activity (long period). So the boot rate for instances is low.
2. As operator, I need to be able to set high quota (thousands of instances to cover the first use case) AND prevent users to start too many of instances at a time. In other word, force my client to use a boot rate « low ».
> Le 9 sept. 2015 à 18:36, David Medberry <openstack at medberry.net> a écrit :
> Your users should also have reasonable quotas set. If they can boot thousands of instances, you may have a quota issue to address. (No problem with the blueprint or need to set an overall limit though--just that you should be able to address this without waiting for that to land.)
> On Mon, Sep 7, 2015 at 8:48 AM, Jean-Daniel Bonnetot <jean-daniel.bonnetot at ovh.net <mailto:jean-daniel.bonnetot at ovh.net>> wrote:
> I try to limit the max instances a user can create per minute.
> With rate limit, we can limit the number of call/min on POST */servers for example.
> But the user can still use the max_count paramteter in his API call to boot dozen of thousand of instances and make the scheduler crazy.
> I’m pretty sure that there is a possiblity to limit the max_count and so define a max instances/min.
> Do you know something to do it?
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org <mailto:OpenStack-operators at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators