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

John Dickinson me at not.mn
Tue Jun 14 21:51:16 UTC 2016


Swift does rate limiting across the proxy servers ("api servers" in nava parlance) as described at http://docs.openstack.org/developer/swift/ratelimit.html. It uses a memcache pool to coordinate the rate limiting across proxy processes (local or across machines).

Code's at https://github.com/openstack/swift/blob/master/swift/common/middleware/ratelimit.py

--John



On 14 Jun 2016, at 8:02, Matt Riedemann 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?
>
> -- 
>
> Thanks,
>
> Matt Riedemann
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160614/3c779094/attachment.pgp>


More information about the OpenStack-operators mailing list