From abc37694c6b0d1d80fa5942386d41f69d1bc085a Mon Sep 17 00:00:00 2001 From: JingLu5 Date: Fri, 23 Jun 2017 03:13:04 +0000 Subject: Improve Yardstick user-guide This patch adds a short description on how to use the "yardstick env prepare" command in a Non-OPNFV installer environtment. Change-Id: Idf54bf5318499d2b129a1445e0758e351945e755 Signed-off-by: JingLu5 --- docs/testing/user/userguide/04-installation.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'docs/testing/user') diff --git a/docs/testing/user/userguide/04-installation.rst b/docs/testing/user/userguide/04-installation.rst index 0c2bb58cf..660f3b5a8 100644 --- a/docs/testing/user/userguide/04-installation.rst +++ b/docs/testing/user/userguide/04-installation.rst @@ -149,7 +149,12 @@ In the Yardstick container, the Yardstick repository is located in the ``/home/o yardstick env prepare -**NOTE**: The above command just works for four OPNFV installers -- **Apex**, **Compass**, **Fuel** and **Joid**. +**NOTE**: The above command works for four OPNFV installers -- **Apex**, **Compass**, **Fuel** and **Joid**. +For Non-OPNFV installer OpenStack environment, the above command can also be used to configure the environment. +But before running the above command in a Non-OPNFV installer environment, it is necessary to create the /etc/yardstick/openstack.creds file and +save OpenStack environment variables in it. For details of the required OpenStack environment variables please refer to +section **Export OpenStack environment variables** + The env prepare command may take up to 6-8 minutes to finish building yardstick-image and other environment preparation. Meanwhile if you wish to monitor the env prepare process, you can enter the Yardstick container in a new @@ -506,3 +511,4 @@ yaml file and add test cases, constraint or task arguments if necessary. Proxy Support (**Todo**) --------------------------- + -- cgit 1.2.3-korg