A collection of plugins for Rally framework designed for the OpenStack platform.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Andrey Kurilin 0913743b43 [ci] Start fixing CLI job 4 years ago
devstack Switch everything to `rally db` 4 years ago
doc Use rally.plugins.openstack.osclients import everywhere 4 years ago
etc Update Rally config sample 4 years ago
rally Merge "Add glance.DownloadImageData scenario" 4 years ago
rally-jobs Add glance.DownloadImageData scenario 4 years ago
samples Add glance.DownloadImageData scenario 4 years ago
tasks Rename certification/ to tasks/ 4 years ago
tests [ci] Start fixing CLI job 4 years ago
.coveragerc [CI] Fix coverage job 5 years ago
.dockerignore Fix docker build command 6 years ago
.gitignore [ci] Start fixing CLI job 4 years ago
.gitreview Update .gitreview file to reflect repo rename 6 years ago
CONTRIBUTING.rst [docs][6] Re-design docs to cover all user-groups 5 years ago
Dockerfile Rename certification/ to tasks/ 4 years ago
LICENSE Initial commit 8 years ago
README.rst Fixup Rally Tutorial Page Link in README 4 years ago
bindep.txt [install] Add iputils to bindep 5 years ago
requirements.txt Remove oslo.serialization dependency 4 years ago
setup.cfg Reword samples and setup.cfg 4 years ago
setup.py Updated from global requirements 6 years ago
test-requirements.txt Update requirements 4 years ago
tox.ini [ci] Start fixing CLI job 4 years ago



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.