Merge "Removes KVS references from the documentation"

doc/source/architecture.rst

@@ -131,16 +131,6 @@ expected to subclass from these classes. The default response for the defined
 apis in these Drivers is to raise a :mod:`keystone.service.TokenController`.
 
 
-KVS Backend
------------
-
-A simple backend interface meant to be further backended on anything that can
-support primary key lookups, the most trivial implementation being an in-memory
-dict.
-
-Supports all features of the general data model.
-
-
 SQL Backend
 -----------
 

doc/source/configuration.rst

@@ -1105,8 +1105,8 @@ example::
 Removing Expired Tokens
 ===========================================================
 
-In the SQL and KVS token stores expired tokens are not automatically
-removed. These tokens can be removed with::
+In the SQL backend expired tokens are not automatically removed. These tokens
+can be removed with::
 
     $ keystone-manage token_flush
 

doc/source/developing.rst

@@ -48,8 +48,7 @@ To run the keystone Admin and API server instances, use::
 
 this runs keystone with the configuration the etc/ directory of the project.
 See :doc:`configuration` for details on how Keystone is configured. By default,
-keystone is configured with KVS backends, so any data entered into keystone run
-in this fashion will not persist across restarts.
+keystone is configured with SQL backends.
 
 
 Interacting with Keystone

keystone/token/providers/uuid.py

@@ -274,7 +274,6 @@ class V3TokenDataHelper(object):
             try:
                 service_catalog = self.catalog_api.get_v3_catalog(
                     user_id, project_id)
-            # TODO(ayoung): KVS backend needs a sample implementation
             except exception.NotImplemented:
                 service_catalog = {}
             # TODO(gyee): v3 service catalog is not quite completed yet