Open Stack

On Aug 13, 2012, at 3:47 AM, Chmouel Boudjnah wrote:

> On Sat, Aug 11, 2012 at 7:51 AM, Michael Basnight <mbasnight at gmail.com> wrote:
>> Yup the last thing i want to do is add a module to _every_ project. I agree with the "as is" approach to a certain extent. If memcache_servers conf value is defined it attempts to import the memcache module. Im sure we can disable cache by default and do the same conditional importation :) sound like that would fit the bill?
> 
> Well currently to get caching with the current auth_token
> implementation you just need to apt-get/yum install python-memcache
> which is much easier than if we had to  curl -O
> http://url/openstack-common/common_caching_module.py to a PYTHON_PATH.

I see what you are getting at. I guess the question is now code extensibility vs ease of installation. Given the fact that this middleware is useless outside of a project that is using it (nova, glance,…) a operator has already understood and installed pieces of openstack-common, right? And more so, nova will already be using this common cache layer since there is some python-memcache stuff in it already. It seems to me that it would not be a ton of extra work to make this work, but i could be wrong. 

Maybe this begs the question, why isint the middleware its own library… At that point it could use the common stuff a bit easier. Are we still doing the copy job for openstack-common?