Ilya Shakhat 1119ec943f Add zuul job with integration testing
This patch introduces base integration test that verifies
messaging loop between agent and server, command execution
and report generation. Shaker in tested in standalone
mode, without intergration with OpenStack.

Change-Id: I8fdc63abdf0be0fc67c3b438bbfc1cf2f69c9f15
2018-10-22 15:03:38 +02:00
2016-08-04 15:36:41 +03:00
2018-07-06 10:33:13 +07:00
2015-10-17 22:38:47 +00:00
2018-07-06 10:33:13 +07:00
2015-01-28 18:56:01 +03:00
2018-04-21 13:54:24 +08:00
2016-12-14 12:51:10 +04:00
2018-01-03 03:15:03 +00:00
2015-11-12 14:05:16 +03:00
2018-07-06 10:33:13 +07:00
2018-10-22 15:03:38 +02:00

Shaker

The distributed data-plane testing tool built for OpenStack.

Shaker wraps around popular system network testing tools like iperf, iperf3 and netperf (with help of flent). Shaker is able to deploy OpenStack instances and networks in different topologies. Shaker scenario specifies the deployment and list of tests to execute. Additionally tests may be tuned dynamically in command-line.

Features

  • User-defined topology via Heat templates
  • Simultaneously test execution on multiple instances
  • Interactive report with stats and charts
  • Built-in SLA verification

Deployment Requirements

  • Shaker server routable from OpenStack cloud
  • Admin-user access to OpenStack API is preferable

Run in Python Environment

$ pip install pyshaker
$ . openrc
$ shaker-image-builder
$ shaker --server-endpoint <host:port> --scenario <scenario> --report <report.html>``
where:
  • host and port - host and port of machine where Shaker is deployed
  • scenario - the scenario to execute, e.g. openstack/perf_l2 ( catalog)
  • <report.html> - file to store the final report

Full list of parameters is available in documentation.

Shaker in Container

Shaker is available as container at Docker Hub at shakhat/shaker

$ docker run -p <port>:<port> -v <artifacts-dir>:/artifacts shakhat/shaker --scenario <scenario> --server-endpoint <host:port>
  --os-auth-url <os-auth-url> --os-username <os-username> --os-password <os-password> --os-project-name <os-project-name>
where:
  • host and port - host and port on machine where Shaker is deployed
  • artifacts-dir - where to store report and raw result
  • scenario - the scenario to execute, e.g. openstack/perf_l2 ( catalog)
  • os-XXX - OpenStack cloud credentials
Description
Distributed data-plane performance testing tool
Readme 3.5 MiB
Languages
Python 91%
HTML 8%
Shell 0.8%
Dockerfile 0.2%