Rally
Rally is a tool for testing how a system behaves under load. You describe what to do, how hard to push and what counts as success in a task file. Rally runs it, measures every iteration, keeps the results and turns them into reports.
The Rally core has no code for any particular system; plugins connect it to one. OpenStack support comes from the rally-openstack package, a few generic plugins (for example, HTTP requests) ship with Rally itself, and you can write plugins for your own services.
Features
Load tests with clear pass or fail criteria (SLA), so a task can gate a CI pipeline.
Verification: runs an existing test suite such as Tempest against an environment and compares the results with earlier runs.
History: every result is kept in a database.
Reports: interactive HTML, trends across many runs, JSON, JUnit XML and Elasticsearch export.
Plugins for everything: platforms, scenarios, runners, contexts, SLA criteria, hooks, exporters and verifiers. Write your own or install a plugin package.
Quick start
No cloud needed: this task sends HTTP requests to a website and checks that every response is successful and fast enough.
$ pip install rally
$ rally db create
$ rally env create --name local
$ cat > task.yaml << EOF
---
version: 2
title: My first task
subtasks:
- title: Check that example.com responds
scenario:
HttpRequests.check_request:
url: https://www.example.com
method: GET
status_code: 200
runner:
constant:
times: 20
concurrency: 4
sla:
failure_rate:
max: 0
max_seconds_per_iteration: 2
EOF
$ rally task start task.yaml
$ rally task report --out report.html
To test an OpenStack cloud, install rally-openstack and follow the tutorial.
Links
Documentation: https://rally.readthedocs.io/latest/ (also published at https://docs.openstack.org/rally/latest/)
Release notes: https://opendev.org/openstack/rally/src/branch/master/CHANGELOG.rst
Contributing: https://opendev.org/openstack/rally/src/branch/master/CONTRIBUTING.rst
OpenStack plugins: https://opendev.org/openstack/rally-openstack
License: Apache License, Version 2.0
Metadata
Release files for rally 5.2.0
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 |
|---|---|---|---|---|
| rally-5.2.0.tar.gz | 4.1 MB | Without provenance | Details for rally-5.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rally-5.2.0-py3-none-any.whl | Python 3 | none | any | Details for rally-5.2.0-py3-none-any.whl |
Total release size: 4.6 MB
Release files / rally-5.2.0.tar.gz
| Download URL | rally-5.2.0.tar.gz |
|---|---|
| Size | 4.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
134a2082a0e00e1bc89114b7fbb7945ec65a60f8107d0cafdc73735bb9af5e0b
|
|
BLAKE2b-256 checksum How to use checksums |
92f8a7f5785bfc83db92828ea7806a1aeaa3a94e327177a85e7c46a9db4ee104
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.9
|
Release files / rally-5.2.0-py3-none-any.whl
| Download URL | rally-5.2.0-py3-none-any.whl |
|---|---|
| Size | 529.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3cb103827270c2b2cbcc23e08383152b8ec96c5d9a0e20627ee27f2dfab775c
|
|
BLAKE2b-256 checksum How to use checksums |
893392728bd7109551554fcf87809784967a1e964c118cd7430c5d086b5c3ccb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.9
|
Security for rally 5.2.0
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.