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> wrote: > Hi, > > 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? > > -- > Jean-Daniel > @pilgrimstack > > > > > > _______________________________________________ > 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/20150909/5c7034f1/attachment.html>