Are you happy with your logging solution? Would you help us out by taking a 30-second survey? Click here


Rally provides a framework for performance analysis and benchmarking of individual OpenStack components as well as full production OpenStack cloud deployments

Subscribe to updates I use rally

Statistics on rally

Number of watchers on Github 236
Number of open issues 0
Main language Python
Open pull requests 0+
Closed pull requests 26+
Last commit over 1 year ago
Repo Created about 6 years ago
Repo Last Updated over 1 year ago
Size 52.7 MB
Organization / Authoropenstack
Page Updated
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

Subscribe to our mailing list

Evaluating rally for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)



Team and repository tags

.. image:: :target:

.. image:: :target: :alt: Latest Version

.. image:: :target: :alt: Gitter Chat

.. image:: :target: :alt: Trello Board

.. image:: :target: :alt: Apache License, Version 2.0

What is Rally

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 what, why and 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

Who Is Using Rally

.. image:: doc/source/images/Rally_who_is_using.png :alt: Who is Using Rally


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:

  1. Server Providers - provide servers (virtual servers), with ssh access, in one L3 network.
  2. Deploy Engines - deploy OpenStack cloud on servers that are presented by Server Providers
  3. Verification - component that runs tempest (or another specific set of tests) against a deployed cloud, collects results & presents them in human readable form.
  4. Benchmark engine - allows to write parameterized benchmark scenarios & run them against the cloud.

Use Cases

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:

  • Automate measuring & profiling focused on how new code changes affect the OS performance;
  • Using Rally profiler to detect scaling & performance issues;
  • 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 search for hardware best suited for particular OpenStack cloud;
  • 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.


  • Free software: Apache license
  • Documentation:
  • Source:
  • Bugs:
  • Step-by-step tutorial:
  • RoadMap:
  • Launchpad page:
  • Gitter chat:
  • Trello board:
rally questions on Stackoverflow (View All Questions)
  • How to show sum of total test case count at portfolioitem/feature level in rally tree grid
  • How to export "Steps" , "Input" and "ExpectedResult" from Rally testcase using API?
  • 403 Forbidden issue using Rally rest api for java
  • Rally SDK 2.0 Get data for random list of features
  • How to query User stories without a Task in Rally Custom Grid?
  • Unable to create loginKey via Rally Encoder page
  • Query for List of user stories in rally that are not in the feature's Release
  • Currently am using Rally 2.1 and i want to get to UserPermissions of specific users. Can somebody help me how to get it?
  • Rally WSAPI query for latest revision
  • How can I download attachments from a Rally workitem using JAVA Rest API?
  • where is the code for all the rally charts given on "View Reports and Charts? "
  • code for rally Defect Arrival And Kill Rate Chart?
  • Handling null exceptions form a Rally Data store
  • Publishing Links to Rally Dashboards
  • Rally: Load same tasks into multiple stories
  • Can I masquerade as another user when creating/updating Rally artifact using Rally WSAPI?
  • OpenStack Rally - is it possible to check nova console logs?
  • Feature deep copy in rally
  • Rally SDK 1.32 - Efficiently determine "active" projects
  • Rally inline edit grid from custom data store
  • Rally Query in the SDK 1 vs Store in the SDK 2
  • Rally API: where can I find DETAILS on EXACTLY what is available?
  • specifying "From" to "Time" drop down calendar in Rally for a chart
  • Rally rest API - updating task estimate fails
  • How to retrieve certain user fields using Rally REST API?
  • what information does exactly Standard Report in Rally conveys?
  • Disparity between outputs that Rally loopback API returns and what is seen on the Rally GUI
  • How to locally develop Rally Apps using the API key so that I don't have to use the JSONP request for subscription
  • Fetching all the Project Name for a Project Cumulative Flow Chart in Rally
  • how do I get the "Name" of a "Release" in Rally?
rally list of languages used
Other projects in Python