639760a0fa
This commit is to address an issue that can cause Shaker to get stuck indefinately waiting for a zeroMQ message that will never arrive. To reproduce set server_endpoint to 10.0.0.1:8080 (assuming nothing is listening and/or this address is unreachable). Shaker will go through launching the heartbeat thread, and creating the heat stack, but then will be stuck at: Waiting for quorum of agents: If debug is turned on, there are no heartbeats coming through. In order to fix this situation this commit sends 3 "tcp pings" to the server_endpoint in order to test it's response before the heartbeat thread and heat stack are created. Change-Id: Ifcfacfb383e7553b53c5b2a20ad39ceccb833c8f |
||
---|---|---|
doc/source | ||
etc | ||
shaker | ||
tools | ||
.dockerignore | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
Dockerfile | ||
LICENSE | ||
README.rst | ||
config-generator.conf | ||
openstack-common.conf | ||
readthedocs.yml | ||
requirements.txt | ||
rtd-requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
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
andport
- 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:
-
host
andport
- 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 - https://pyshaker.readthedocs.io/
- Bugtracker - https://launchpad.net/shaker