Re: [openstack-dev] [keystone] [oslo] Using oslo.cache in keystoneclient.middleware.auth_token
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 that. +++ I think it makes a lot of sense to separate out the middleware. Would this be a new project under Identity or would it go to Oslo since it would be a shared library among the other programs? I think it really just needs to be a separate repo, similar to how keystoneclient is a separate repo but still part of the Keystone project. The primary problem being addressed is dependencies and packaging, not governance. dt -- Dean Troyer dtro...@gmail.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [keystone] [oslo] Using oslo.cache in keystoneclient.middleware.auth_token
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 depend on [1]. Moving the middleware to a separate library would solve that. +++ I think it makes a lot of sense to separate out the middleware. Would this be a new project under Identity or would it go to Oslo since it would be a shared library among the other programs? I think it really just needs to be a separate repo, similar to how keystoneclient is a separate repo but still part of the Keystone project. The primary problem being addressed is dependencies and packaging, not governance. Right, that's what I meant. Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [keystone] [oslo] Using oslo.cache in keystoneclient.middleware.auth_token
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 happy to put some time into the implementation. Kurt G. | @kgriffs ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [keystone] [oslo] Using oslo.cache in keystoneclient.middleware.auth_token
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 considering registering one for Juno if the team thinks this feature makes sense. I'd be happy to put some time into the implementation. That does make sense. We need to look at the dependency graph between the keystoneclient and oslo.cache, though. It appears the current version of oslo.cache is going to bring in quite a few oslo libraries that we would not want keystoneclient to depend on [1]. Moving the middleware to a separate library would solve that. [1] https://wiki.openstack.org/wiki/Oslo/Dependencies Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [keystone] [oslo] Using oslo.cache in keystoneclient.middleware.auth_token
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, Doug Hellmann doug.hellm...@dreamhost.com wrote: 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 considering registering one for Juno if the team thinks this feature makes sense. I’d be happy to put some time into the implementation. That does make sense. We need to look at the dependency graph between the keystoneclient and oslo.cache, though. It appears the current version of oslo.cache is going to bring in quite a few oslo libraries that we would not want keystoneclient to depend on [1]. Moving the middleware to a separate library would solve that. [1] https://wiki.openstack.org/wiki/Oslo/Dependencies Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [keystone] [oslo] Using oslo.cache in keystoneclient.middleware.auth_token
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 Developer, Keystone m...@metacloud.com On March 31, 2014 at 10:11:21, Dolph Mathews (dolph.math...@gmail.com) wrote: 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, Doug Hellmann doug.hellm...@dreamhost.com wrote: 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 considering registering one for Juno if the team thinks this feature makes sense. I’d be happy to put some time into the implementation. That does make sense. We need to look at the dependency graph between the keystoneclient and oslo.cache, though. It appears the current version of oslo.cache is going to bring in quite a few oslo libraries that we would not want keystoneclient to depend on [1]. Moving the middleware to a separate library would solve that. [1] https://wiki.openstack.org/wiki/Oslo/Dependencies Doug ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
