openstack
/
keystone
Code Issues Proposed changes

Update cache doc 

The cache backend in the doc is expired. This patch updated
it to keep the same with oslo.cache.

Change-Id: I7b0b93c33ed46c5f8338e921701cb0e8d0f7e4b3
Depends-on: Ia6993425408dd7cb172752a6b8b3aeef8eb0a97a
This commit is contained in:
wangxiyuan 2017-11-13 10:31:27 +08:00
parent 52bb8757e6
commit f3c5c9cdb9
1 changed files with 21 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/source/admin/identity-caching-layer.rst
View File

@ -50,6 +50,9 @@ So to enable only the token back end caching, set the values as follows:
Current functional back ends are:
``dogpile.cache.null``
A "null" backend that effectively disables all cache operations.(Default)
``dogpile.cache.memcached``
Memcached back end using the standard ``python-memcached`` library.
@ -71,8 +74,24 @@ Current functional back ends are:
between processes. This means that caching and cache invalidation will not
be consistent or reliable.
``dogpile.cache.mongo``
MongoDB as caching back end.
``dogpile.cache.memory_pickle``
In-memory cache, but serializes objects with pickle lib. It's not suitable
for use outside of testing. The reason is the same with
``dogpile.cache.memory``
``oslo_cache.mongo``
MongoDB as caching back end.
``oslo_cache.memcache_pool``
Memcached backend that does connection pooling.
``oslo_cache.etcd3gw``
Uses etcd 3.x for storage.
``oslo_cache.dict``
A DictCacheBackend based on dictionary, not suitable for use outside of
testing as it does not share cache between processes.This means that caching
and cache invalidation will not be consistent or reliable.
Caching for tokens and tokens validation
----------------------------------------