Am curious,
Any reason why swift got in the business of ratelimiting in the first place?
-Josh
John Dickinson wrote:
> 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
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators