openstack
/
tempest
Code Issues Proposed changes

Fix doc issue of lock test accounts 

When using the lock testing accounts, allow_tenant_isolation
should be set as False. Now it's missing in the document.
This patch will add it.

Closes-Bug: #1454001

Change-Id: I3e1e7a31ea4c1c8b25e821df545c8674a8de38da
This commit is contained in:
Fei Long Wang 2015-05-12 11:36:49 +12:00
parent f27769e302
commit 7fee78771a
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/configuration.rst
View File

@ -115,6 +115,8 @@ To enable and use locking test accounts you need do a few things:
#. Provide tempest with the location of you accounts.yaml file with the
test_accounts_file option in the auth section
#. Set allow_tenant_isolation = False in the auth group
It is worth pointing out that each set of credentials in the accounts.yaml
should have a unique tenant. This is required to provide proper isolation
to the tests using the credentials, and failure to do this will likely cause
@ -140,6 +142,11 @@ options in the identity section:
#. alt_password
#. alt_tenant_name
And in the auth secion:
#. allow_tenant_isolation = False
#. comment out 'test_accounts_file' or keep it as empty
It only makes sense to use it if parallel execution isn't needed, since tempest
won't be able to properly isolate tests using this. Additionally, using the
traditional config options for credentials is not able to provide credentials to