Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Morgan Fainberg
On Fri, May 13, 2016 at 1:12 PM, Adam Young wrote: > On 05/13/2016 12:52 PM, Monty Taylor wrote: > >> On 05/13/2016 11:38 AM, Eric Larson wrote: >> >>> Monty Taylor writes: >>> >>> On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote: > On Fri, May 13, 2016 at 02:58:08PM

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Adam Young
On 05/13/2016 12:52 PM, Monty Taylor wrote: On 05/13/2016 11:38 AM, Eric Larson wrote: 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

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Monty Taylor
On 05/13/2016 11:38 AM, Eric Larson wrote: > > 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?

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Eric Larson
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? https://github.com/pinterest/pymemcache Looks like a good alternative.

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Monty Taylor
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? >> >> https://github.com/pinterest/pymemcache > > Looks like a good alternative. Honestly,

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Morgan Fainberg
On Fri, May 13, 2016 at 6: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? >> >> https://github.com/pinterest/pymemcache >> > > Looks like

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread John Dickinson
On 13 May 2016, at 1:14, Steve Martinelli wrote: > /me gets the ball rolling > > Just when python3 support for keystone was looking like a reality, we've > hit another snag. Apparently there are several issues with python-memcached > in py3, putting it simply: it loads, but doesn't actually

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Mehdi Abaakouk
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? https://github.com/pinterest/pymemcache Looks like a good alternative. -- Mehdi Abaakouk mail: sil...@sileht.net irc: sileht

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Julien Danjou
On Fri, May 13 2016, Steve Martinelli wrote: > /me gets the ball rolling > > Just when python3 support for keystone was looking like a reality, we've > hit another snag. Apparently there are several issues with python-memcached > in py3, putting it simply: it loads, but doesn't actually work.

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Morgan Fainberg
On May 13, 2016 05:32, "Kiall Mac Innes" wrote: > > Hey Dims, > > From what I remember, oslo.cache seemed unnecessarily complex to use > vs memcache's simplicity, and didn't have any usage docs[1] to help folks > get started using it. > > I can see there is some docs under the

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Kiall Mac Innes
Hey Dims, >From what I remember, oslo.cache seemed unnecessarily complex to use vs memcache's simplicity, and didn't have any usage docs[1] to help folks get started using it. I can see there is some docs under the module index, but at a glance they seem somewhat disconnected and incomplete.

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Morgan Fainberg
On May 13, 2016 05:25, "Mehdi Abaakouk" wrote: >>> >>> - Is anyone interested in using pylibmc in their project instead of >>> python-memcached? > > > This is not a real drop-in replacement, pylibmc.Client is not threadsafe > like python-memcached [1]. Aos it's written in C, it

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Mehdi Abaakouk
- Is anyone interested in using pylibmc in their project instead of python-memcached? This is not a real drop-in replacement, pylibmc.Client is not threadsafe like python-memcached [1]. Aos it's written in C, it shouldn't be a problem for keystone because you don't use eventlet anymore, but for

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Morgan Fainberg
On May 13, 2016 04:36, "Davanum Srinivas" wrote: > > Steve, > > Couple of points: > > * We can add pylibmc to g-r and phase out python-memcached over a time period. > * If folks are using python-memcached, we should switch then over to > oslo.cache, then only oslo.cache will

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Davanum Srinivas
Steve, Couple of points: * We can add pylibmc to g-r and phase out python-memcached over a time period. * If folks are using python-memcached, we should switch then over to oslo.cache, then only oslo.cache will reference either python-memcached or pylibmc which will make the situation easier to

[openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

2016-05-13 Thread Steve Martinelli
/me gets the ball rolling Just when python3 support for keystone was looking like a reality, we've hit another snag. Apparently there are several issues with python-memcached in py3, putting it simply: it loads, but doesn't actually work. I've included projects in the subject line that use