I would personally like it off, since it appears to me to offer a false sense of security for the reasons mentioned in that review (doesn't stop DOS, doesn't work across processes/API nodes). Even though, I would recommend/think before its turned off that there should be a detailed document on what to replace it with since even though it does provide a minimal rate limiting capabilities, it does provide more than zero. So there should be some docs or thought put into a replacement and explanation on how to use said replacement/s. -josh Sent from my really tiny device... On Jul 24, 2013, at 3:42 PM, "Joe Gordon" <joe.gordon0 at gmail.com<mailto:joe.gordon0 at gmail.com>> wrote: Hi all I have proposed a patch to disable per-user rate limiting by default: https://review.openstack.org/#/c/34821/. And on Russell's request does anyone care or prefer this to be enabled by default? Here is some more context: Earlier rate limiting discussion: http://www.gossamer-threads.com/lists/openstack/operators/28599 Related bug: https://bugs.launchpad.net/tripleo/+bug/1178529 rate limiting is per process, and doesn't act as expected in a multi-process environment: https://review.openstack.org/#/c/36516/ best, Joe Gordon _______________________________________________ OpenStack-dev mailing list OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130725/4fee54ee/attachment.html>