Consolidate service-catalog.rst

Consolidate from configuration.rst into admin/service-catalog.rst.

Change-Id: I3446f5e8ac7dc5ea2db180b0039b9f66d3f703e7
This commit is contained in:
Suramya Shah 2018-02-23 12:46:38 +05:30 committed by Colleen Murphy
parent a32c596980
commit 53f0b62e8e
3 changed files with 56 additions and 54 deletions

View File

@ -41,3 +41,4 @@ command-line client.
endpoint-filtering.rst
health-check-middleware.rst
oauth1.rst
service-catalog.rst

View File

@ -0,0 +1,55 @@
Service Catalog
===============
Keystone provides two configuration options for managing a service catalog.
SQL-based Service Catalog (``sql.Catalog``)
-------------------------------------------
A dynamic database-backed driver fully supporting persistent configuration.
``keystone.conf`` example:
.. code-block:: ini
[catalog]
driver = sql
.. NOTE::
A `template_file` does not need to be defined for the sql based catalog.
To build your service catalog using this driver, see the built-in help:
.. code-block:: bash
$ openstack --help
$ openstack service create --help
$ openstack endpoint create --help
File-based Service Catalog (``templated.Catalog``)
--------------------------------------------------
The templated catalog is an in-memory backend initialized from a read-only
``template_file``. Choose this option only if you know that your service
catalog will not change very much over time.
.. NOTE::
Attempting to change your service catalog against this driver will result
in ``HTTP 501 Not Implemented`` errors. This is the expected behavior. If
you want to use these commands, you must instead use the SQL-based Service
Catalog driver.
``keystone.conf`` example:
.. code-block:: ini
[catalog]
driver = templated
template_file = /opt/stack/keystone/etc/default_catalog.templates
The value of ``template_file`` is expected to be an absolute path to your
service catalog configuration. An example ``template_file`` is included in
keystone, however you should create your own to reflect your deployment.

View File

@ -313,60 +313,6 @@ following property:
invalid, so typically the generator selection should be considered
immutable for a given installation.
Service Catalog
===============
Keystone provides two configuration options for managing a service catalog.
SQL-based Service Catalog (``sql.Catalog``)
-------------------------------------------
A dynamic database-backed driver fully supporting persistent configuration.
``keystone.conf`` example:
.. code-block:: ini
[catalog]
driver = sql
.. NOTE::
A `template_file` does not need to be defined for the sql based catalog.
To build your service catalog using this driver, see the built-in help:
.. code-block:: bash
$ openstack --help
$ openstack service create --help
$ openstack endpoint create --help
File-based Service Catalog (``templated.Catalog``)
--------------------------------------------------
The templated catalog is an in-memory backend initialized from a read-only
``template_file``. Choose this option only if you know that your service
catalog will not change very much over time.
.. NOTE::
Attempting to change your service catalog against this driver will result
in ``HTTP 501 Not Implemented`` errors. This is the expected behavior. If
you want to use these commands, you must instead use the SQL-based Service
Catalog driver.
``keystone.conf`` example:
.. code-block:: ini
[catalog]
driver = templated
template_file = /opt/stack/keystone/etc/default_catalog.templates
The value of ``template_file`` is expected to be an absolute path to your
service catalog configuration. An example ``template_file`` is included in
keystone, however you should create your own to reflect your deployment.
Endpoint Policy
===============