On Fri, Apr 4, 2014 at 10:51 AM, Kurt Griffiths
kurt.griffi...@rackspace.com wrote:
It appears the current version of oslo.cache is going to bring in quite
a few oslo libraries that we would not want keystone client to depend on
[1]. Moving the middleware to a separate library would solve
On Fri, Apr 4, 2014 at 12:22 PM, Dean Troyer dtro...@gmail.com wrote:
On Fri, Apr 4, 2014 at 10:51 AM, Kurt Griffiths
kurt.griffi...@rackspace.com wrote:
It appears the current version of oslo.cache is going to bring in quite
a few oslo libraries that we would not want keystone client to
Hi folks, has there been any discussion on using oslo.cache within the
auth_token middleware to allow for using other cache backends besides
memcached? I didn’t find a Keystone blueprint for it, and was considering
registering one for Juno if the team thinks this feature makes sense. I’d be
On Mon, Mar 31, 2014 at 12:18 PM, Kurt Griffiths
kurt.griffi...@rackspace.com wrote:
Hi folks, has there been any discussion on using oslo.cache within the
auth_token middleware to allow for using other cache backends besides
memcached? I didn't find a Keystone blueprint for it, and was
dogpile.cache would be substantially lighter on the client-side as it only
has a hard dependency on dogpile.core. It supports plenty of backends
beyond memcached and we already use it in keystone quite heavily.
http://dogpilecache.readthedocs.org/en/latest/
On Mon, Mar 31, 2014 at 11:35 AM,
I’ve been working on (albeit slowly) getting the keystone implementation of
dogpile.cache into oslo.cache. It’s been slow due to other demands, but I’m
hoping to get back to it in the near future here so we can make moves like this
more easily.
—
Morgan Fainberg
Principal Software Engineer
Core
