|Number of watchers on Github||236|
|Number of open issues||0|
|Open pull requests||0+|
|Closed pull requests||26+|
|Last commit||over 1 year ago|
|Repo Created||almost 6 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||openstack|
|Do you use rally? Leave a review!|
|View rally activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
.. image:: https://governance.openstack.org/tc/badges/rally.svg :target: https://governance.openstack.org/tc/reference/tags/index.html
.. image:: https://img.shields.io/pypi/v/rally.svg :target: https://pypi.python.org/pypi/rally/ :alt: Latest Version
.. image:: https://img.shields.io/badge/gitter-join_chat-ff69b4.svg :target: https://gitter.im/rally-dev/Lobby :alt: Gitter Chat
.. image:: https://img.shields.io/badge/tasks-trello_board-blue.svg :target: https://trello.com/b/DoD8aeZy/rally :alt: Trello Board
.. image:: https://img.shields.io/github/license/openstack/rally.svg :target: https://www.apache.org/licenses/LICENSE-2.0 :alt: Apache License, Version 2.0
Rally is a Benchmark-as-a-Service project for OpenStack.
Rally is intended to provide the community with a benchmarking tool that is capable of performing specific, complicated and reproducible test cases on real deployment scenarios.
If you are here, you are probably familiar with OpenStack and you also know that it's a really huge ecosystem of cooperative services. When something fails, performs slowly or doesn't scale, it's really hard to answer different questions on
where has happened. Another reason why you could be here is that you would like to build an OpenStack CI/CD system that will allow you to improve SLA, performance and stability of OpenStack continuously.
The OpenStack QA team mostly works on CI/CD that ensures that new patches don't break some specific single node installation of OpenStack. On the other hand it's clear that such CI/CD is only an indication and does not cover all cases (e.g. if a cloud works well on a single node installation it doesn't mean that it will continue to do so on a 1k servers installation under high load as well). Rally aims to fix this and help us to answer the question
How does OpenStack work at scale?. To make it possible, we are going to automate and unify all steps that are required for benchmarking OpenStack at scale: multi-node OS deployment, verification, benchmarking & profiling.
Rally workflow can be visualized by the following diagram:
.. image:: doc/source/images/Rally-Actions.png :alt: Rally Architecture
.. image:: doc/source/images/Rally_who_is_using.png :alt: Who is Using Rally
Rally documentation on ReadTheDocs <https://rally.readthedocs.org/en/latest/>_ 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 <https://rally.readthedocs.io/en/latest/quick_start/tutorial.html>_ 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:
.. image:: doc/source/images/Rally-UseCases.png :alt: Rally Use Cases
Typical cases where Rally aims to help are: