El 12/07/12 18:59, Jay Pipes escribió:
On 07/12/2012 12:26 PM, Rafael Durán Castañeda wrote:
Unless I'm missing something, nova_limits is not applicable to Keystone
since it takes the tenant_id from 'nova.context', which obiously is not
available for Keystone; thought adapt/extend it to keystone
On 07/12/2012 12:26 PM, Rafael Durán Castañeda wrote:
> Unless I'm missing something, nova_limits is not applicable to Keystone
> since it takes the tenant_id from 'nova.context', which obiously is not
> available for Keystone; thought adapt/extend it to keystone should be
> trivial and probably is
On Thu, 2012-07-12 at 18:26 +0200, Rafael Durán Castañeda wrote:
> Unless I'm missing something, nova_limits is not applicable to Keystone
> since it takes the tenant_id from 'nova.context', which obiously is not
> available for Keystone; thought adapt/extend it to keystone should be
> trivial a
On 07/12/2012 04:48 PM, Jay Pipes wrote:
On 07/11/2012 07:28 PM, Rafael Durán Castañeda wrote:
Thank you guys for the info, I didn't know about some of the projects.
However writing my "on-house" own stuff is not what I was considering
but adding a middleware into Keystone, nothing fancy but ext
On 07/11/2012 07:28 PM, Rafael Durán Castañeda wrote:
> Thank you guys for the info, I didn't know about some of the projects.
> However writing my "on-house" own stuff is not what I was considering
> but adding a middleware into Keystone, nothing fancy but extensible so
> it covers at least most b
El 11/07/12 19:23, Jorge Williams escribió:
More info on the Repose rate limiter here:
http://wiki.openrepose.org/display/REPOSE/Rate+Limiting+Filter
The rate limiter has the concept of limit groups -- you can specify
rate limits for a particular group -- then introspect the request to
see wh
More info on the Repose rate limiter here:
http://wiki.openrepose.org/display/REPOSE/Rate+Limiting+Filter
The rate limiter has the concept of limit groups -- you can specify rate limits
for a particular group -- then introspect the request to see which group
applies. Typically a user can be pl
REPOSE would be worth taking a look at, as well (includes rate limiting):
https://github.com/rackspace/repose
http://openrepose.org/documentation.html
-Dolph
On Wed, Jul 11, 2012 at 9:19 AM, Kevin L. Mitchell <
kevin.mitch...@rackspace.com> wrote:
> On Wed, 2012-07-11 at 01:50 +0200, Rafael
On Wed, 2012-07-11 at 01:50 +0200, Rafael Durán Castañeda wrote:
> I'm working on a blueprint [1] and implementation [2] doing rate limit
> middleware for Keystone; after discussing it at keystone's meeting
> today I was suggested to ask for some feedback from the community.
Have you taken a look
Hi,
I'm working on a blueprint [1] and implementation [2] doing rate limit
middleware for Keystone; after discussing it at keystone's meeting
today I was suggested to ask for some feedback from the community.
I think the most important thing is how to track the keystone usage
and thus it should b
10 matches
Mail list logo
