Rally provides a framework for performance analysis and benchmarking of individual OpenStack components as well as full production OpenStack cloud deployments
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Go to file
Andrey Kurilin e8613ffeb0 Propose rally 3.4.0 release
Change-Id: I2463227b1d4a114c0c5caa093f72b5b0b7c50d4e
2 weeks ago
.zuul.d Use official python docker images 2 weeks ago
doc Merge "Replace deprecated inspect.getargspec" 2 weeks ago
etc Moving IRC network reference to OFTC 2 years ago
rally Update requirements and upper-constraints.txt 2 weeks ago
rally-jobs [ci] Remove redundant rally task job files 3 years ago
samples [evil] Remove OpenStack related plugins 5 years ago
tests Merge "Update requirements and upper-constraints.txt" 2 weeks ago
.coveragerc [CI] Fix coverage job 7 years ago
.dockerignore Rework docker build 3 years ago
.gitignore [ci] Start fixing CLI job 6 years ago
.gitreview OpenDev Migration Patch 4 years ago
CHANGELOG.rst Propose rally 3.4.0 release 2 weeks ago
CONTRIBUTING.rst Fix contribute page 2 years ago
DOCKER_README.md Propose rally 3.4.0 release 2 weeks ago
Dockerfile Use official python docker images 2 weeks ago
LICENSE Initial commit 10 years ago
README.rst update git.openstack.org to opendev 4 years ago
bindep.txt Pin SQLAlchemy to <2.0.0 4 months ago
requirements.txt Update requirements and upper-constraints.txt 2 weeks ago
setup.cfg Keep CI up-to-date 2 weeks ago
setup.py Stop checking installation on ubuntu-xenial nodes 3 years ago
test-requirements.txt Update requirements and upper-constraints.txt 2 weeks ago
tox.ini Keep CI up-to-date 2 weeks ago
upper-constraints.txt Update requirements and upper-constraints.txt 2 weeks ago

README.rst

Rally

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!

Team and repository tags

image

Latest Version

Gitter Chat

Trello Board

Apache License, Version 2.0

What is Rally

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 Architecture

Who Is Using Rally

Who is Using Rally

Documentation

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.

Architecture

In terms of software architecture, Rally is built of 4 main components:

  1. Environment - one of key component in Rally. It manages and stores information about tested platforms. Env manager is using platform plugins to: create, delete, cleanup, check health, obtain information about platforms.
  2. Task component is responsible for executing tests defined in task specs, persisting and reporting results.
  3. Verification component allows to wrap subunit-based testing tools and provide complete tool on top of them with allow to do pre configuration, post cleanup as well process and persist results to Rally DB for future use like reporting and results comparing.

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 OpenStack 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.