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 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 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
Links
Bugtracker - https://launchpad.net/shaker
2 maintainers
Metadata
2 maintainers
Release files for pyshaker 1.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyshaker-1.4.2.tar.gz | 1.2 MB | Without provenance | Details for pyshaker-1.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyshaker-1.4.2-py3-none-any.whl | Python 3 | none | any | Details for pyshaker-1.4.2-py3-none-any.whl |
Total release size: 1.4 MB
Release files / pyshaker-1.4.2.tar.gz
| Download URL | pyshaker-1.4.2.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
762da1ff92bf789d5cd2f1f8b20d5d917bd3f00b394f692a23e5ce8ab454b72b
|
|
BLAKE2b-256 checksum How to use checksums |
c3b6ef44cd4afbda9bb08d105457202c06b190aab8a4e767a4d01f4571e5ba02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.0 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.8.6
|
Release files / pyshaker-1.4.2-py3-none-any.whl
| Download URL | pyshaker-1.4.2-py3-none-any.whl |
|---|---|
| Size | 140.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3fc20ba0e17a91cc763d76de39da9aa46350ee858104c9cd5c236ac7621aacd5
|
|
BLAKE2b-256 checksum How to use checksums |
ecbf16d376efdc61bf09b59cb8fe8e71cab5e98f709f5dd026553fba968933ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.0 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.8.6
|
Security for pyshaker 1.4.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
