[openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached
eric.larson at rackspace.com
Fri May 13 16:38:23 UTC 2016
Monty Taylor writes:
> On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote:
>> On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote:
>>> What's wrong with pymemcache, that we picked for tooz and are
>>> using for 2 years now?
>> Looks like a good alternative.
> Honestly, nobody should be using pymemcache or python-memcached
> or pylibmc for anything caching related in OpenStack. People
> should be using oslo.cache - however, if that needs work before
> it's usable, people should be using dogpile.cache, which is what
> oslo.cache uses on the backend.
> dogpile is pluggable, so it means that the backend used for
> caching can be chosen in a much broader manner. As morgan
> mentions elsewhere, that means that people who want to use a
> different memcache library just need to write a dogpile driver.
> Please don't anybody directly use memcache libraries for caching
> in OpenStack. Please.
Using dogpile doesn't remove the decision of what caching backend
is used. Dogpile has support (I think) for all the libraries
Oslo cache would need to be the one making decision as to what
backend is used if we need to have something consistent.
With that said, it is important that we understand what projects
have specific requirements or have experienced issues, otherwise
there is a good chance teams will hit an issue down the line and
have to work around it.
> OpenStack Development Mailing List (not for usage questions)
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Eric Larson | eric.larson at rackspace.com Software Developer
| Cloud DNS | OpenStack Designate Rackspace Hosting | Austin,
More information about the OpenStack-dev