Add section to the config guide on lock_path
This commit adds a section to the tempest configuration guide on
configuring the lock_path for running tempest and explains why it
is needed.
Change-Id: I73913797d96f9f833e02e5b37be9c0c85b3ae959
diff --git a/doc/source/configuration.rst b/doc/source/configuration.rst
index f772aa3..5b13619 100644
--- a/doc/source/configuration.rst
+++ b/doc/source/configuration.rst
@@ -1,6 +1,21 @@
Tempest Configuration Guide
===========================
+This guide is a starting point for configuring tempest. It aims to elaborate
+on and explain some of the mandatory and common configuration settings and how
+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.
+
+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
----------------