From 1d161d9c3059f0e316b7c65402eac2c6b4f172a8 Mon Sep 17 00:00:00 2001 From: Xin Date: Thu, 10 Sep 2015 10:38:22 -0700 Subject: [PATCH] correct --external-host Change-Id: Id5c35cc5fa7a205c58809147af964657475737be --- doc/source/usage.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/usage.rst b/doc/source/usage.rst index a3d694c..1e6facb 100644 --- a/doc/source/usage.rst +++ b/doc/source/usage.rst @@ -217,12 +217,12 @@ Example 2: Cloud upload/download performance measurement Run VMTP on an OpenStack cloud with a specified configuration file (mycfg.yaml), and saved the result to a JSON file:: - python vmtp.py -c mycfg.yaml -r admin-openrc.sh -p admin --external_host localadmin@172.29.87.29 --json res.json + python vmtp.py -c mycfg.yaml -r admin-openrc.sh -p admin --external-host localadmin@172.29.87.29 --json res.json This run will generate 8 sets of performance data, the standard 6 sets mentioned above, plus two sets of upload/download performance data for both TCP and UDP. If you do not have ssh password-less access to the external host (public key) you must specify a password:: - python vmtp.py -c mycfg.yaml -r admin-openrc.sh -p admin --external_host localadmin@172.29.87.29:secret --json res.json + python vmtp.py -c mycfg.yaml -r admin-openrc.sh -p admin --external-host localadmin@172.29.87.29:secret --json res.json Example 3: Store the OpenStack deployment details """"""""""""""""""""""""""""""""""""""""""""""""" @@ -233,7 +233,7 @@ Run VMTP on an OpenStack cloud, fetch the defails of the deployment and store it In addition, VMTP also supports to store the results to a MongoDB server:: - python vmtp.py -r admin-openrc.sh -p admin --json res.json --mongod_server 172.29.87.29 --controller-node root@192.168.12.34:admin + python vmtp.py -r admin-openrc.sh -p admin --json res.json --mongod-server 172.29.87.29 --controller-node root@192.168.12.34:admin Before storing info into MongoDB, some configurations are needed to change to fit in your environment. By default, VMTP will store to database "client_db" with collection name "pns_web_entry", and of course these can be changed in the configuration file. Below are the fields which are related to accessing MongoDB::