Rally provides a framework for performance analysis and benchmarking of individual OpenStack components as well as full production OpenStack cloud deployments
Python HTML Shell Other
Latest commit 2de0820 Feb 23, 2017 Jenkins committed with openstack-gerrit Merge "removed extra 'can' from description"
Failed to load latest commit information.
certification/openstack [CI] Fix image regexp and version Feb 16, 2017
devstack [docs][2] Re-design docs to cover all user-groups Dec 1, 2016
doc removed extra 'can' from description Feb 16, 2017
etc [CI] Fix image regexp and version Feb 16, 2017
rally-jobs [CI] Increase SLA values to improve stability of CI Feb 16, 2017
rally Merge "[FIX] fix params in creating floating-ip" Feb 20, 2017
samples [CI] Fix image regexp and version Feb 16, 2017
tests Merge "[FIX] fix params in creating floating-ip" Feb 20, 2017
.coveragerc [CI] Fix coverage job Jun 27, 2016
.dockerignore Fix docker build command Nov 11, 2015
.gitignore Put in more propriate place test results Aug 22, 2016
.gitreview Update git review + hosting/mirroring links Apr 18, 2015
CONTRIBUTING.rst [docs][6] Re-design docs to cover all user-groups Jan 10, 2017
Dockerfile [Bindep]Use bindep lib to install system packages Dec 24, 2016
LICENSE Initial commit Aug 3, 2013
README.rst add more badges Jan 30, 2017
babel.cfg Add rally.sample.conf to project Aug 14, 2013
bindep.txt [install] Add iputils to bindep Dec 30, 2016
install_rally.sh [install bug]Fix directory changed when installing env Jan 25, 2017
optional-requirements.txt Fixing docker-check jenkins job Sep 20, 2016
requirements.txt Fix novaclient requirement Jan 27, 2017
setup.cfg Merge "Add Python 3.5 classifier and venv" Jul 31, 2016
setup.py Updated from global requirements Sep 22, 2015
test-requirements.txt Sync requirements Jan 24, 2017
tox.ini [Bindep]Use bindep lib to install system packages Dec 24, 2016



Team and repository tags

Latest Version Gitter Chat Trello Board 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:

Rally Architecture

Who Is Using Rally

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:

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.