From 101da047d5fbefb10000fbc6efec815c0e5deaa9 Mon Sep 17 00:00:00 2001 From: Brant Knudson Date: Sun, 29 Mar 2015 11:37:13 -0500 Subject: [PATCH] Update identity service management for keystone-all deprecation Using keystone-all to start the Identity service is deprecated in favor of the keystone WSGI services. Change-Id: Ia71a0d01816f3f7354c508fc4fd7c9a0cfe4f5ad --- ...ion_keystone-concepts-service-management.xml | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/doc/common/section_keystone-concepts-service-management.xml b/doc/common/section_keystone-concepts-service-management.xml index 1c955de8e7..f14f3a8d0b 100644 --- a/doc/common/section_keystone-concepts-service-management.xml +++ b/doc/common/section_keystone-concepts-service-management.xml @@ -10,10 +10,12 @@ It consists of: - keystone-all. - Starts both the service and administrative APIs in a - single process to provide Catalog, Authorization, and - Authentication services for OpenStack. + keystone Web Server Gateway + Interface (WSGI) service. Can be run in a + WSGI-capable web server such as Apache httpd to provide the + Identity Service. The service and administrative APIs are run as + separate instances of the WSGI service. + Identity Service functions. Each has a pluggable back @@ -21,6 +23,13 @@ service. Most support standard back ends like LDAP or SQL. + + keystone-all. + Starts both the service and administrative APIs in a + single process. Using federation with keystone-all is not + supported. keystone-all is deprecated in favor of the WSGI + service. + The Identity Service also maintains a user that corresponds to each service, such as, a user named