yahoo-eng-team team mailing list archive

[Morgan Fainberg <morgan.fainberg@xxxxxxxxx>]

Was incomplete ages ago, inactive and generally not needed now with
oslo_cache etc.

** Changed in: keystone
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1360553

Title:
  Add memcached_backend option in keystone.conf

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  If we choose memcached as the token backend driver, we should set
  proper servers in '[memcache]' section of keystone.conf.

  For the memcache backend, there are 3  memcached client supported by dogpile,
  ---------------------------------------------------
  # pydoc dogpile.cache.backends.memcached

     dogpile.cache.api.CacheBackend(__builtin__.object)
          GenericMemcachedBackend
              BMemcachedBackend
              MemcachedBackend(MemcacheArgs, GenericMemcachedBackend)
              PylibmcBackend(MemcacheArgs, GenericMemcachedBackend)

  ----------------------------------------------------

  In keystone, they are listed in
  keystone/common/kvs/backends/memcached.py:

  VALID_DOGPILE_BACKENDS = dict(pylibmc=memcached.PylibmcBackend,
                                bmemcached=memcached.BMemcachedBackend,
                                memcached=memcached.MemcachedBackend)

  By default, memcached will be used. The "memcached_backend" option will determine which backend to use.
  But there is no simple to pass the "memcached_backend" option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1360553/+subscriptions