Rally provides a framework for performance analysis and benchmarking of individual OpenStack components as well as full production OpenStack cloud deployments
Go to file
Zuul 6dea050274 Merge "Allow plugins to return config options as list of tuples" 2019-09-10 11:59:56 +00:00
.zuul.d Migrate rally-database-migration to Ubuntu Bionic 2019-04-03 18:02:42 +00:00
devstack Replace openstack.org git:// URLs with https:// 2019-03-24 20:35:59 +00:00
doc Fix building docs 2019-09-02 16:36:06 +03:00
etc Propose 1.6.0 release 2019-06-19 15:13:19 +00:00
rally Merge "Allow plugins to return config options as list of tuples" 2019-09-10 11:59:56 +00:00
rally-jobs [evil] Remove OpenStack related plugins 2018-06-20 19:01:47 +03:00
samples [evil] Remove OpenStack related plugins 2018-06-20 19:01:47 +03:00
tests Support to verify https url 2019-08-22 19:15:28 +08:00
.coveragerc [CI] Fix coverage job 2016-06-27 15:39:13 +03:00
.dockerignore Fix docker build command 2015-11-10 16:33:29 -08: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 1.6.0 release 2019-06-19 15:13:19 +00:00
CONTRIBUTING.rst [docs][6] Re-design docs to cover all user-groups 2017-01-10 11:25:00 -08: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 bindep.txt: 2019-03-08 15:13:24 -07:00
install_rally.sh install_rally.sh: moved zypper pkg manager up to handle case when 2019-06-03 14:43:11 -06:00
optional-requirements.txt Fixing docker-check jenkins job 2016-09-20 16:56:00 +03:00
requirements.txt Upgrade jsonschema upper version 2019-09-09 15:41:06 +00:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-04 08:36:06 +00:00
setup.py Updated from global requirements 2015-09-22 10:45:07 +00:00
test-requirements.txt Sync Sphinx requirement 2019-06-20 20:52:11 +08:00
tox.ini [ci] Add job to run functional tests over py3 env 2019-02-04 18:01:13 +00:00
upper-constraints.txt Upgrade jsonschema upper version 2019-09-09 15:41:06 +00: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.