Open Stack

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 and probably is the way to go.

You are correct, you would not take nova_limits and use it with
Keystone.  What you likely would do is use nova_limits as a model to
develop your own shim with the additional capabilities you need.  I
expect that you would not need much of what nova_limits does, by the
way…
-- 
Kevin L. Mitchell <kevin.mitchell at rackspace.com>