Rally provides a framework for performance analysis and benchmarking of individual OpenStack components as well as full production OpenStack cloud deployments
Go to file
Andriy Kurilin 094f0188fc Propose 4.1.0 release
Change-Id: I26eb0723f3d3442554bfe1c40181c06e6d1b8f70
2024-04-29 19:45:24 +00:00
.zuul.d Add support for SQLAlchemy 2.0 2024-04-23 15:38:52 -04:00
doc Merge "Replace deprecated inspect.getargspec" 2023-05-19 18:41:57 +00:00
etc Moving IRC network reference to OFTC 2021-07-06 17:49:31 -05:00
rally Add support for SQLAlchemy 2.0 2024-04-23 15:38:52 -04:00
rally-jobs [ci] Remove redundant rally task job files 2020-03-22 21:23:28 +02:00
samples [evil] Remove OpenStack related plugins 2018-06-20 19:01:47 +03:00
tests Use unittest.TestCase instead of testtools.TestCase 2024-04-29 11:54:45 -07:00
.coveragerc [CI] Fix coverage job 2016-06-27 15:39:13 +03:00
.dockerignore Rework docker build 2020-03-21 15:37:33 +02:00
.gitignore [ci] Start fixing CLI job 2017-10-12 12:13:18 +03:00
.gitreview OpenDev Migration Patch 2019-04-19 19:32:06 +00:00
CHANGELOG.rst Propose 4.1.0 release 2024-04-29 19:45:24 +00:00
CONTRIBUTING.rst Fix contribute page 2021-06-16 18:31:48 +03:00
DOCKER_README.md Propose 4.1.0 release 2024-04-29 19:45:24 +00:00
Dockerfile [docker] use python3.11-slim as base image 2023-12-04 16:53:15 +01:00
LICENSE Initial commit 2013-08-03 09:17:25 -07:00
README.rst update git.openstack.org to opendev 2019-04-25 23:59:52 +00:00
bindep.txt Pin SQLAlchemy to <2.0.0 2023-01-30 17:24:02 +05:30
requirements.txt Add support for SQLAlchemy 2.0 2024-04-23 15:38:52 -04:00
setup.cfg Update u-c file 2024-01-19 14:58:05 +01:00
setup.py Stop checking installation on ubuntu-xenial nodes 2020-03-03 13:45:55 +02:00
test-requirements.txt Use unittest.TestCase instead of testtools.TestCase 2024-04-29 11:54:45 -07:00
tox.ini Remove redundant db ignore warnings 2024-04-29 19:45:15 +00:00
upper-constraints.txt Add support for SQLAlchemy 2.0 2024-04-23 15:38:52 -04:00

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.