|1 week ago|
|.zuul.d||1 week ago|
|doc||2 months ago|
|etc||1 week ago|
|rally||1 week ago|
|rally-jobs||1 week ago|
|samples||1 year ago|
|tests||1 week ago|
|.coveragerc||3 years ago|
|.dockerignore||1 week ago|
|.gitignore||2 years ago|
|.gitreview||11 months ago|
|CHANGELOG.rst||1 week ago|
|CONTRIBUTING.rst||3 years ago|
|DOCKER_README.md||1 week ago|
|Dockerfile||1 week ago|
|LICENSE||6 years ago|
|README.rst||11 months ago|
|bindep.txt||1 month ago|
|requirements.txt||1 month ago|
|setup.cfg||2 weeks ago|
|setup.py||4 weeks ago|
|test-requirements.txt||1 week ago|
|tox.ini||1 week ago|
|upper-constraints.txt||1 month ago|
Rally is tool & framework that allows one to write simple plugins and combine them in complex tests scenarios that allows to perform all kinds of testing!
Rally is intended to provide a testing framework that is capable to perform specific, complicated and reproducible test cases on real deployment scenarios.
Rally workflow can be visualized by the following diagram:
Rally documentation on ReadTheDocs is a perfect place to start learning about Rally. It provides you with an easy and illustrative guidance through this benchmarking tool.
For example, check out the Rally step-by-step tutorial that explains, in a series of lessons, how to explore the power of Rally in benchmarking your OpenStack clouds.
In terms of software architecture, Rally is built of 4 main components:
There are 3 major high level Rally Use Cases:
Typical cases where Rally aims to help are:
Investigate how different deployments affect the OS performance:
- Find the set of suitable OpenStack deployment architectures;
- Create deployment specifications for different loads (amount of controllers, swift nodes, etc.);
Automate the production cloud specification generation:
- Determine terminal loads for basic cloud operations: VM start & stop, Block Device create/destroy & various OpenStack API methods;
- Check performance of basic cloud operations in case of different loads.