From ebd771478e57e905e7108e43e3e27e4f225101e6 Mon Sep 17 00:00:00 2001 From: gengchc2 Date: Wed, 28 Sep 2016 18:02:58 +0800 Subject: [PATCH] Fix a typo in tcp.yaml,etc TrivialFix Change-Id: Iaa5308198a791f5d03f2e60ae73aa4e8fc8373cd --- doc/source/catalog.rst | 6 +++--- shaker/scenarios/spot/ping.yaml | 2 +- shaker/scenarios/spot/tcp.yaml | 2 +- shaker/scenarios/spot/udp.yaml | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/source/catalog.rst b/doc/source/catalog.rst index 0550b6f..cdb832e 100644 --- a/doc/source/catalog.rst +++ b/doc/source/catalog.rst @@ -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 diff --git a/shaker/scenarios/spot/ping.yaml b/shaker/scenarios/spot/ping.yaml index 199961b..09ab563 100644 --- a/shaker/scenarios/spot/ping.yaml +++ b/shaker/scenarios/spot/ping.yaml @@ -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: diff --git a/shaker/scenarios/spot/tcp.yaml b/shaker/scenarios/spot/tcp.yaml index 2841e25..cad3cd2 100644 --- a/shaker/scenarios/spot/tcp.yaml +++ b/shaker/scenarios/spot/tcp.yaml @@ -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: diff --git a/shaker/scenarios/spot/udp.yaml b/shaker/scenarios/spot/udp.yaml index 9a663d9..1af57de 100644 --- a/shaker/scenarios/spot/udp.yaml +++ b/shaker/scenarios/spot/udp.yaml @@ -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: