diff options
| author | Jenkins <jenkins@review.openstack.org> | 2015-04-27 14:17:48 +0000 |
|---|---|---|
| committer | Gerrit Code Review <review@openstack.org> | 2015-04-27 14:17:48 +0000 |
| commit | 238bf121cfc2d2e1173efdf447ce24b69b192320 (patch) | |
| tree | aac94f92718433f38da7f80389226e6244182690 | |
| parent | 9c95882542acd47779066f46bd9b771dc06678f6 (diff) | |
| parent | 4fae4723dfb38eaf9d212919115381442a9bd819 (diff) | |
| download | tempest-238bf121cfc2d2e1173efdf447ce24b69b192320.tar.gz | |
Merge "Add a paragraph on the use of tempest_roles option"
| -rw-r--r-- | doc/source/configuration.rst | 8 |
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 |