[Openstack-operators] How are people dealing with API rate limiting?

Russell Bryant rbryant at redhat.com
Tue Jun 14 20:58:25 UTC 2016


This is the most common approach I've heard of (doing rate limiting in your
load balancer).

On Tue, Jun 14, 2016 at 12:10 PM, Kingshott, Daniel <
Daniel.Kingshott at bestbuy.com> wrote:

> We use Haproxy to load balance API requests and applied rate limiting
> there.
>
>
>
> On Tue, Jun 14, 2016 at 9:02 AM, Matt Riedemann
> <mriedem at linux.vnet.ibm.com> wrote:
>
> A question came up in the nova IRC channel this morning about the
> api_rate_limit config option in nova which was only for the v2 API.
>
> Sean Dague explained that it never really worked because it was per API
> server so if you had more than one API server it was busted. There is no
> in-tree replacement in nova.
>
> So the open question here is, what are people doing as an alternative?
>
>
>
>
> When I was working at Rackspace, we used
> http://www.openrepose.org/ <http://www.openrepose.org/> to handle multi
> server rate-limiting for these cases.
>
> -Alex
>
>
> --
>
> Thanks,
>
> Matt Riedemann
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 
Russell Bryant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160614/d52ff5c9/attachment.html>


More information about the OpenStack-operators mailing list