openstack/rally
Code Issues Proposed changes
Rally provides a framework for performance analysis and benchmarking of individual OpenStack components as well as full production OpenStack cloud deployments
4,086 Commits 1 Branch 21 Tags 123 MiB
Python 96.2%
HTML 3%
JavaScript 0.4%
Shell 0.3%
8a1672f293
Go to file
Alexander Maretskiy 8a1672f293 [Plugins] Rename workload dammy.failure -> Dummy.failure 
`dummy.failure' was the first class-based workload so
it got specific name started with lowercase `dummy'.
But other dummy scenarios have become class-based recently,
so dummy.failure is a kind of white crow now.

This patch simply renames the workload, without keeping
backward compatibility, because this is not critical.

Change-Id: I9ddeb0368adc7e517a74e6d25144b8e88ee4cd44
2016-09-01 18:51:54 +03:00
certification/openstack Fix certification task instructions 2016-08-23 16:27:34 -04:00
devstack [devstack] fix keystone v3 deployemnt config 2016-08-31 11:50:14 +03:00
doc Remove Pavel Boldin from maintainers page 2016-08-25 08:46:50 -07:00
etc Merge "[Verify] Adding 'add-options' arg to rally verify genconfig cmd" 2016-09-01 14:29:11 +00:00
rally [Plugins] Rename workload dammy.failure -> Dummy.failure 2016-09-01 18:51:54 +03:00
rally-jobs [Plugins] Rename workload dammy.failure -> Dummy.failure 2016-09-01 18:51:54 +03:00
samples [Plugins] Rename workload dammy.failure -> Dummy.failure 2016-09-01 18:51:54 +03:00
tests Merge "[Verify] Adding 'add-options' arg to rally verify genconfig cmd" 2016-09-01 14:29:11 +00: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 Put in more propriate place test results 2016-08-21 18:52:44 -07:00
.gitreview Update .gitreview file to reflect repo rename 2015-04-18 00:37:36 +00:00
babel.cfg Add rally.sample.conf to project 2013-08-14 14:08:09 +04:00
Dockerfile [docker] fix ability to use rally verify install 2016-07-28 15:40:33 +03:00
install_rally.sh [Install] Improve installation script 2016-05-31 18:47:55 +03:00
LICENSE Initial commit 2013-08-03 09:17:25 -07:00
optional-requirements.txt Add monasca benchmark in plugin - Part 0: metrics 2016-07-31 00:38:18 +03:00
README.rst fix up the formatting of the readme for the announce script 2016-04-19 15:18:34 -04:00
requirements.txt Update requirements 2016-08-10 15:54:07 +03:00
setup.cfg Merge "Add Python 3.5 classifier and venv" 2016-07-31 18:02:03 +00:00
setup.py Updated from global requirements 2015-09-22 10:45:07 +00:00
test-requirements.txt launch tests in parallel 2016-07-27 17:24:46 +03:00
tox.ini Put in more propriate place test results 2016-08-21 18:52:44 -07:00

README.rst

Rally

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

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

Links