From 5af2e680f7ede390288c77912a45c98c08baa655 Mon Sep 17 00:00:00 2001 From: Steve Martinelli Date: Wed, 27 Aug 2014 13:17:03 -0400 Subject: [PATCH] Add bash code style to some portions of configuration.rst Some bash commands were not being formatted correctly, or did not have a leading $. Change-Id: I3939521ce1119f3957adf02004c16ded9fe13f96 --- doc/source/configuration.rst | 36 ++++++++++++++++++++++-------------- 1 file changed, 22 insertions(+), 14 deletions(-) diff --git a/doc/source/configuration.rst b/doc/source/configuration.rst index 6f0d551b2..d0842fc0d 100644 --- a/doc/source/configuration.rst +++ b/doc/source/configuration.rst @@ -159,6 +159,8 @@ continue to carry stale identity mappings in its table. While benign, keystone provides an ability for operators to purge the mapping table of such stale entries using the keystone-manage command, for example: +.. code-block:: bash + $ keystone-manage mapping_purge --domain-name DOMAINA --local-id abc@de.com A typical usage would be for an operator to obtain a list of those entries @@ -172,11 +174,15 @@ implementation**, then, if the details of those entries that have been deleted are not available, then it is safe to simply bulk purge identity mappings periodically, for example: +.. code-block:: bash + $ keystone-manage mapping_purge --domain-name DOMAINA will purge all the mappings for DOMAINA. The entire mapping table can be purged with the following command: +.. code-block:: bash + $ keystone-manage mapping_purge --all Public ID Generators @@ -1089,28 +1095,30 @@ Example usage ``keystone`` is set up to expect commands in the general form of ``keystone`` ``command`` ``argument``, followed by flag-like keyword arguments to provide additional (often optional) information. For example, the command -``user-list`` and ``tenant-create`` can be invoked as follows:: +``user-list`` and ``tenant-create`` can be invoked as follows: + +.. code-block:: bash # Using token auth env variables - export OS_SERVICE_ENDPOINT=http://127.0.0.1:35357/v2.0/ - export OS_SERVICE_TOKEN=secrete_token - keystone user-list - keystone tenant-create --name=demo + $ export OS_SERVICE_ENDPOINT=http://127.0.0.1:35357/v2.0/ + $ export OS_SERVICE_TOKEN=secrete_token + $ keystone user-list + $ keystone tenant-create --name=demo # Using token auth flags - keystone --os-token=secrete --os-endpoint=http://127.0.0.1:35357/v2.0/ user-list - keystone --os-token=secrete --os-endpoint=http://127.0.0.1:35357/v2.0/ tenant-create --name=demo + $ keystone --os-token=secrete --os-endpoint=http://127.0.0.1:35357/v2.0/ user-list + $ keystone --os-token=secrete --os-endpoint=http://127.0.0.1:35357/v2.0/ tenant-create --name=demo # Using user + password + tenant_name env variables - export OS_USERNAME=admin - export OS_PASSWORD=secrete - export OS_TENANT_NAME=admin - keystone user-list - keystone tenant-create --name=demo + $ export OS_USERNAME=admin + $ export OS_PASSWORD=secrete + $ export OS_TENANT_NAME=admin + $ keystone user-list + $ keystone tenant-create --name=demo # Using user + password + tenant_name flags - keystone --os_username=admin --os_password=secrete --os_tenant_name=admin user-list - keystone --os_username=admin --os_password=secrete --os_tenant_name=admin tenant-create --name=demo + $ keystone --os_username=admin --os_password=secrete --os_tenant_name=admin user-list + $ keystone --os_username=admin --os_password=secrete --os_tenant_name=admin tenant-create --name=demo Tenants -------