openstack
/
tempest
Code Issues Proposed changes

Update quickstart for revised temepst init setup 

This commit updates the quickstart to reflect reality when using
tempest init. The quickstart documented our original ideal expectation
of how things worked, but because of python packaging limitations we
had to adjust it's behavior. However, the quickstart was never updated
to reflect this change.

Change-Id: Icbc0c005a344c25b7ab7d3fd059a9401747eca3f
Closes-Bug: #1598882
This commit is contained in:
Matthew Treinish 2016-07-05 10:22:52 -04:00
parent 0b2c35e3d7
commit 531b01c017
No known key found for this signature in database
GPG Key ID: FD12A0F214C9E177
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.rst
View File

@ -63,12 +63,14 @@ as it is simpler, and quicker to work with.
This can be done within a venv, but the assumption for this guide is that
the Tempest cli entry point will be in your shell's PATH.
#. Installing Tempest will create a /etc/tempest dir which will contain the
sample config file packaged with Tempest. The contents of /etc/tempest will
be copied to all local working dirs, so if there is any common configuration
you'd like to be shared between anyone setting up local Tempest working dirs
it's recommended that you copy or rename tempest.conf.sample to tempest.conf
and make those changes to that file in /etc/tempest
#. Installing Tempest may create a /etc/tempest dir, however if one isn't
created you can create one or use ~/.tempest/etc or ~/.config/tempest in
place of /etc/tempest. If none of these dirs are created tempest will create
~/.tempest/etc when it's needed. The contents of this dir will always
automatically be copied to all etc/ dirs in local workspaces as an initial
setup step. So if there is any common configuration you'd like to be shared
between local Tempest workspaces it's recommended that you pre-populate it
before running ``tempest init``.
#. Setup a local Tempest workspace. This is done by using the tempest init
command::