openstack
/
keystone
Code Issues Proposed changes

Merge "Reference dogpile.cache.memcached backend properly"

This commit is contained in:
Jenkins 2014-02-13 03:33:57 +00:00 committed by Gerrit Code Review
parent f543cb1e4a f2309df098
commit 541de98301
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/configuration.rst
View File

@ -243,7 +243,7 @@ behavior is that subsystem caching is enabled, but the global toggle is set to d
* ``enabled`` - enables/disables caching across all of keystone
* ``debug_cache_backend`` - enables more in-depth logging from the cache backend (get, set, delete, etc)
* ``backend`` - the caching backend module to use e.g. ``dogpile.cache.memcache``
* ``backend`` - the caching backend module to use e.g. ``dogpile.cache.memcached``
.. NOTE::
A given ``backend`` must be registered with ``dogpile.cache`` before it

2
etc/keystone.conf.sample
View File

@ -308,7 +308,7 @@
# expiration_time = 600
# Dogpile.cache backend module. It is recommended that Memcache
# (dogpile.cache.memcache) or Redis (dogpile.cache.redis) be used in production
# (dogpile.cache.memcached) or Redis (dogpile.cache.redis) be used in production
# deployments. Small workloads (single process) like devstack can use the
# dogpile.cache.memory backend.
# backend = keystone.common.cache.noop

2
keystone/common/kvs/backends/memcached.py
View File

@ -76,7 +76,7 @@ class MemcachedLock(object):
class MemcachedBackend(manager.Manager):
"""Pivot point to leverage the various dogpile.cache memcache backends.
"""Pivot point to leverage the various dogpile.cache memcached backends.
To specify a specific dogpile.cache memcached backend, pass the region
backend argument `dogpile_memcache_backend` set to one of the known dogpile