From f3c5c9cdb96150613300113280556b713c309805 Mon Sep 17 00:00:00 2001
From: wangxiyuan <wangxiyuan@huawei.com>
Date: Mon, 13 Nov 2017 10:31:27 +0800
Subject: [PATCH] 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
---
doc/source/admin/identity-caching-layer.rst | 23 +++++++++++++++++++--
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/doc/source/admin/identity-caching-layer.rst b/doc/source/admin/identity-caching-layer.rst
index a776d1c641..36744f47e5 100644
--- a/doc/source/admin/identity-caching-layer.rst
+++ b/doc/source/admin/identity-caching-layer.rst
@@ -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
----------------------------------------