3d1d37b96a
Adds a new accommodation instruction 'best_effort' that allows the deployment to proceed even if the number of available compute nodes is less than what was requested. For example, this will create a single pair of agents on separate compute nodes if possible, but will fall back to creating them on the same compute node if only one is available: accommodation: pair, single_room, best_effort, compute_nodes: 2 Change-Id: I1986f550ac0dc934bfa5db84b40a6419d6608c7e Closes-Bug: 1807630
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:
-
hostandport- host and port of machine where Shaker is deployedscenario- 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 performa/shaker
$ docker run -p <port>:<port> -v <artifacts-dir>:/artifacts performa/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:
-
hostandport- host and port on machine where Shaker is deployedartifacts-dir- where to store report and raw resultscenario- the scenario to execute, e.g. openstack/perf_l2 ( catalog)os-XXX- OpenStack cloud credentials
Links
- PyPi - https://pypi.org/project/pyshaker/
- Docker - https://hub.docker.com/r/performa/shaker/
- Docs - http://pyshaker.readthedocs.io/
- Bugtracker - https://launchpad.net/shaker/