summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatthew Treinish <mtreinish@kortar.org>2015-04-16 21:03:54 -0400
committerMatthew Treinish <mtreinish@kortar.org>2015-04-21 23:41:12 +0000
commit4fae4723dfb38eaf9d212919115381442a9bd819 (patch)
tree25bed4d8505745a6819ab78d1769af77bc062584
parentf96ab3a861df9de507d614919c932364479d28bc (diff)
downloadtempest-4fae4723dfb38eaf9d212919115381442a9bd819.tar.gz
Add a paragraph on the use of tempest_roles option
This commit adds a paragraph to the tempest configuration guide on how to use the tempest_roles option. This was previously missing from the tenant isolation section. Change-Id: I1ef1649186edbeb51e1ced1bbb361b78eaef3721
-rw-r--r--doc/source/configuration.rst8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/source/configuration.rst b/doc/source/configuration.rst
index e21deeae8..0b4ec9830 100644
--- a/doc/source/configuration.rst
+++ b/doc/source/configuration.rst
@@ -83,6 +83,14 @@ To enable and use tenant isolation you only need to configure 2 things:
This is also the currently the default credential provider enabled by tempest,
due to it's common use and ease of configuration.
+It is worth pointing out that depending on your cloud configuration you might
+need to assign a role to each of the users created Tempest's tenant isolation.
+This can be set using the *tempest_roles* option. It takes in a list of role
+names each of which will be assigned to each of the users created by tenant
+isolation. This option will not have any effect when set and tempest is not
+configured to use tenant isolation.
+
+
Locking Test Accounts
"""""""""""""""""""""
For a long time using tenant isolation was the only method available if you