openstack/tempest
Code Issues Proposed changes

Make README.rst consistent

Browse Source 
The command samples represent with "$" in most places.
So this patch adds it to some places.
And this patch changes the url to the official one.

Change-Id: I6f7a70e4e4b2fb74e08999cc1c8cf2f6d16fa43e
This commit is contained in:
Ken'ichi Ohmichi 2016-04-22 18:24:15 -07:00
parent d1c4d60457
commit 9883ff2777
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.rst
View File

@ -58,7 +58,7 @@ as it is simpler, and quicker to work with.
#. You first need to install Tempest. This is done with pip after you check out #. You first need to install Tempest. This is done with pip after you check out
the Tempest repo:: the Tempest repo::
$ git clone https://github.com/openstack/tempest/ $ git clone http://git.openstack.org/openstack/tempest
$ pip install tempest/ $ pip install tempest/
This can be done within a venv, but the assumption for this guide is that This can be done within a venv, but the assumption for this guide is that
@ -71,14 +71,14 @@ as it is simpler, and quicker to work with.
it's recommended that you copy or rename tempest.conf.sample to tempest.conf it's recommended that you copy or rename tempest.conf.sample to tempest.conf
and make those changes to that file in /etc/tempest and make those changes to that file in /etc/tempest
#. Setup a local working Tempest dir. This is done using the tempest init #. Setup a local working Tempest dir. This is done by using the tempest init
command:: command::
tempest init cloud-01 $ tempest init cloud-01
works the same as:: works the same as::
mkdir cloud-01 && cd cloud-01 && tempest init $ mkdir cloud-01 && cd cloud-01 && tempest init
This will create a new directory for running a single Tempest configuration. This will create a new directory for running a single Tempest configuration.
If you'd like to run Tempest against multiple OpenStack deployments the idea If you'd like to run Tempest against multiple OpenStack deployments the idea