performa
/
shaker
Code Issues Proposed changes

Fix a typo in tcp.yaml,etc 

TrivialFix

Change-Id: Iaa5308198a791f5d03f2e60ae73aa4e8fc8373cd
This commit is contained in:
gengchc2 2016-09-28 18:02:58 +08:00
parent 61181bd0c3
commit ebd771478e
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/catalog.rst
View File

@ -391,7 +391,7 @@ Ping
This scenario uses ping to measure the latency between the local host and the
remote. The remote host can be provided via command-line, it defaults to
8.8.8.8. The scenario verifies SLA and expects the latency to be at most 30ms.
The destination host can be overriden by command-line parameter, e.g.
The destination host can be overridden by command-line parameter, e.g.
``--matrix "{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario spot/ping``.
@ -404,7 +404,7 @@ TCP bandwidth
This scenario uses iperf3 to measure TCP throughput between local host and
ping.online.net (or against hosts provided via CLI). SLA check is verified and
expects the speed to be at least 90Mbit and at most 20 retransmitts. The
destination host can be overriden by command-line parameter, e.g. ``--matrix
destination host can be overridden by command-line parameter, e.g. ``--matrix
"{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario spot/tcp``.
@ -417,7 +417,7 @@ UDP bandwidth
This scenario uses iperf3 to measure UDP throughput between local host and
ping.online.net (or against hosts provided via CLI). SLA check is verified and
requires at least 10 000 packets per second. The destination host can be
overriden by command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``.
overridden by command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario spot/udp``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/spot/udp.yaml

2
shaker/scenarios/spot/ping.yaml
View File

@ -5,7 +5,7 @@ description: >
the remote. The remote host can be provided via command-line, it defaults
to 8.8.8.8. The scenario verifies SLA and expects the latency to be at most
30ms.
The destination host can be overriden by command-line parameter,
The destination host can be overridden by command-line parameter,
e.g. ``--matrix "{host: 172.10.1.2}"``.
execution:

2
shaker/scenarios/spot/tcp.yaml
View File

@ -4,7 +4,7 @@ description: >
This scenario uses iperf3 to measure TCP throughput between local host and
ping.online.net (or against hosts provided via CLI). SLA check is verified
and expects the speed to be at least 90Mbit and at most 20 retransmitts.
The destination host can be overriden by command-line parameter,
The destination host can be overridden by command-line parameter,
e.g. ``--matrix "{host: 172.10.1.2}"``.
execution:

2
shaker/scenarios/spot/udp.yaml
View File

@ -4,7 +4,7 @@ description: >
This scenario uses iperf3 to measure UDP throughput between local host and
ping.online.net (or against hosts provided via CLI). SLA check is verified
and requires at least 10 000 packets per second.
The destination host can be overriden by command-line parameter,
The destination host can be overridden by command-line parameter,
e.g. ``--matrix "{host: 172.10.1.2}"``.
execution: