summaryrefslogtreecommitdiffstats
path: root/samples/ping-ext-stimuli.yaml
diff options
context:
space:
mode:
authorHans Feldt <hans.feldt@ericsson.com>2015-06-29 15:27:55 +0200
committerHans Feldt <hans.feldt@ericsson.com>2015-07-08 07:02:45 +0000
commitd71e101ac1420ed03fa2dbecb76fc8156a16761a (patch)
treef6d62c25ac79268626a6a5d3d6e2c14b153e5abf /samples/ping-ext-stimuli.yaml
parent6b667910909b332e78105ccdf17e39e4b286ed39 (diff)
Add support for action hooks in runner config
pre-start and post-stop intention is to be used to gather information about the target system. single-shot and periodic-action intention is to perform actions on the infrastructure or cloud resources. For example server live migration or network interface down. Example of what can be added in the runner section: pre-start-action: command: "heat stack-show demo" periodic-action: interval: 10 command: "ifconfig vboxnet1" single-shot-action: after: 30 command: "nova show goofy.demo" post-stop-action: command: "nova list" pre-start and post-stop data are added into the output file. periodic and single-shot are not because that would interfere with the actual sampled data. Besides the intention is not to log statistics but do things with the infrastructure such as server live migration. TODO: add sections to the output file, something like pre, data & post JIRA: YARDSTICK-46 Change-Id: Ia059813fb74733f86368aea9c7a20e5afb71d228 Signed-off-by: Hans Feldt <hans.feldt@ericsson.com>
Diffstat (limited to 'samples/ping-ext-stimuli.yaml')
-rw-r--r--samples/ping-ext-stimuli.yaml49
1 files changed, 49 insertions, 0 deletions
diff --git a/samples/ping-ext-stimuli.yaml b/samples/ping-ext-stimuli.yaml
new file mode 100644
index 000000000..cfe791567
--- /dev/null
+++ b/samples/ping-ext-stimuli.yaml
@@ -0,0 +1,49 @@
+---
+# Sample benchmark task config file
+# Measure network latency using ping, destination is an external server
+# Make sure servers have internet access before running this test.
+# For example using virtual MOS do something this on the host:
+# sudo iptables -t nat -A POSTROUTING -s 172.16.0.0/24 \! -d 172.16.0.0/24 -j MASQUERADE
+#
+# This sample demonstrates the use of runner actions - hooks inserted in
+# diffrent places of the runner execution.
+#
+
+schema: "yardstick:task:0.1"
+
+scenarios:
+-
+ type: Ping
+ host: goofy.demo
+ target: 8.8.8.8
+ runner:
+ type: Duration
+ duration: 60
+ interval: 1
+ pre-start-action:
+ command: "heat stack-show demo"
+ periodic-action:
+ interval: 10
+ command: "ifconfig vboxnet1"
+ single-shot-action:
+ after: 30
+ command: "nova show goofy.demo"
+ post-stop-action:
+ command: "nova list"
+ sla:
+ max_rtt: 10
+ action: monitor
+
+context:
+ name: demo
+ image: cirros-0.3.3
+ flavor: m1.tiny
+ user: cirros
+ servers:
+ goofy:
+ floating_ip: true
+ networks:
+ test:
+ cidr: '10.0.1.0/24'
+ external_network: "net04_ext"
+