Ilya Shakhat f5eb5bb6e4 Fix logging in shaker-all-in-one
Logging reconfiguration does not work in recent oslo.log versions.
Attempt to update config results in complete loss of logs (both in
stderr and file). With this patch all logs are written into 1 file
in artifacts dir.

Also improve logging when no auth url is provided (os-client-config
blindly tries to use the value resulting in AttributeError.

Change-Id: Icc1fc22cd6658d9b782c761ddf79f93e39c9b4be
2017-02-27 16:51:27 +04:00
2017-02-27 16:51:27 +04:00
2016-08-04 15:36:41 +03:00
2015-01-28 18:56:01 +03:00
2015-10-17 22:38:47 +00:00
2015-07-09 11:12:29 +03:00
2017-02-27 16:51:27 +04:00
2015-01-28 18:56:01 +03:00
2016-08-19 17:22:22 +03:00
2016-12-14 12:51:10 +04:00
2015-11-12 14:05:16 +03:00
2016-12-14 12:51:10 +04: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%