summaryrefslogtreecommitdiffstats
path: root/docs/sample_config.yaml
diff options
context:
space:
mode:
authorzhifeng.jiang <jiang.zhifeng@zte.com.cn>2016-05-14 04:39:09 -0400
committerzhifeng.jiang <jiang.zhifeng@zte.com.cn>2016-05-14 04:57:40 -0400
commita9a6ab08260d63388aa55bd016267bf30d880b3b (patch)
treeb1b2b3b1e49cc198d3bee1eb8d96ac580b64ab76 /docs/sample_config.yaml
parent5017e823b109621729b69e9fde251f3eb66db298 (diff)
Correct some spelling mistakes.
Change-Id: I990684afba696775abe07e8d4dd3ac4ade77cb61 Signed-off-by: zhifeng.jiang <jiang.zhifeng@zte.com.cn>
Diffstat (limited to 'docs/sample_config.yaml')
-rw-r--r--docs/sample_config.yaml16
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/sample_config.yaml b/docs/sample_config.yaml
index 3bfca80d..eae9ea20 100644
--- a/docs/sample_config.yaml
+++ b/docs/sample_config.yaml
@@ -1,18 +1,18 @@
- ## This is a sample Config.yaml file
+ ## This is a sample Config.yaml file
#Scenario would define the test case scenario.
#The benchmark key contains the benchmark to run such as dhrystone,whetstone,dpi,ssh etc.
-# Host and server list he differnet machines on which the benchmark would run.
-# On machines lised within hosts, the benchmarks would run in parallel.
+# Host and server list the different machines on which the benchmark would run.
+# On machines listed within hosts, the benchmarks would run in parallel.
# On machines listed within server, the benchmarks would run when the benechmarks running on hosts have been completed.
# This has been used to control the folow of the testcase. For example, running the testcases on a vm vs hostmachin, we would like to run the test case serially. It should run first on the host machine and then on the vm. This testcase flow control could be used for other testcases to be developed such as those for networking.
-Scenario:
+Scenario:
benchmark: dhrystone
host: machine_1, machine_2, virtualmachine_1
- server:
+ server:
-#Context would define the enviironment on wichic to run:
+#Context would define the environment on which to run:
#Host Machine keys would contain Host_Machines/ Baremetal machines to run the benchmarks on
#e.g in Host Machine , machine_1 and machine_2 are the bare metal machines. For each baremetal machine its IP(which should be reachable from the location on which you run QTIP), passwords and its role(host or server)
Context:
@@ -21,7 +21,7 @@ Context:
ip: 172.18.0.16
pw: Op3nStack
role: host
- Virtual_Machines:
+ Virtual_Machines:
virtualmachine_1:
availability_zone: nova
public_network: 'net04_ext'
@@ -29,7 +29,7 @@ Context:
flavor: m1.large
role: server
-# A geeral description of the testcase. Could be used later for reports.
+# A general description of the testcase. Could be used later for reports.
Test_Description:
Test_category: "Compute"
Benchmark: "dhrystone"