openstack
/
tempest
Code Issues Proposed changes

Drop lock_path section from config guide 

This commit drops the lock_path section from the tempest config guide.
Previously setting this was required there was no default value from
the oslo lib. However, tempest recently switched to overriding the
default to use the system temp dir. So additional configuration by the
end user should not be required here anymore.

Change-Id: Ia594745ad4d8e6b701c799cbf5ac5e555c598e3f
This commit is contained in:
Matthew Treinish 2015-04-27 17:33:38 -04:00
parent aa29c7e071
commit 7715a38e3e
1 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/configuration.rst
View File

@ -9,16 +9,6 @@ they are used in conjunction. The source of truth on each option is the sample
config file which explains the purpose of each individual option. You can see
the sample config file here: :ref:`tempest-sampleconf`
Lock Path
---------
There are some tests and operations inside of tempest that need to be
externally locked when running in parallel to prevent them from running at
the same time. This is a mandatory step for configuring tempest and is still
needed even when running serially. All that is needed to do this is:
#. Set the lock_path option in the oslo_concurrency group
Auth/Credentials
----------------