Rally provides a framework for performance analysis and benchmarking of individual OpenStack components as well as full production OpenStack cloud deployments
Go to file
Olga Kopylova e4f58bf63b Validators adder for benchmarks preconditions
Implements decorator for adding validators to method.
Validators are called in benchmark runner.
Validation method should return instance of
rally.benchmark.validation.ValidationResult class.

Blueprint validate-benchmark-preconditions

Change-Id: I68c8f5cc5d8758026bbe7ef211aa914b313ebb81
2014-01-27 09:26:33 +02:00
contrib/devstack Extra scripts with DevStack support 2014-01-16 19:00:04 +04:00
doc LxcProvider network refactoring 2014-01-23 19:15:43 +02:00
etc/rally update rally conf sample 2013-10-15 14:59:18 +04:00
openstack-patches Added python clients patches 2013-10-18 14:20:51 +03:00
rally Validators adder for benchmarks preconditions 2014-01-27 09:26:33 +02:00
tests Validators adder for benchmarks preconditions 2014-01-27 09:26:33 +02:00
tools Update oslo code 2013-12-23 10:24:35 +04:00
.coveragerc Omit openstack/common/ in test coverage reports 2014-01-16 00:53:49 +04:00
.gitignore Add .venv to git ignore 2013-12-23 17:01:22 +04:00
.gitreview Add .gitreview file 2013-09-06 19:37:42 +04:00
.testr.conf Move tests to root dirrectory and fix tox 2013-08-28 19:08:07 +04:00
AUTHORS Add self to AUTHORS file 2013-10-11 04:49:28 -04:00
babel.cfg Add rally.sample.conf to project 2013-08-14 14:08:09 +04:00
LICENSE Initial commit 2013-08-03 09:17:25 -07:00
openstack-common.conf Add DB utils from Oslo 2013-08-25 14:51:38 +04:00
README.rst Fixed some formatting and typos in the README 2013-10-15 17:04:25 -06:00
requirements.txt Add FuelClient 2014-01-24 14:38:26 +02:00
run_tests.sh Move tests to root dirrectory and fix tox 2013-08-28 19:08:07 +04:00
setup.cfg Add support to build docs by Sphinx 2014-01-15 19:11:11 +04:00
setup.py Sync with global requirements 2014-01-01 23:08:07 +04:00
test-requirements.txt Add support to build docs by Sphinx 2014-01-15 19:11:11 +04:00
tox.ini Sync with global requirements 2014-01-01 23:08:07 +04:00

Rally

Introduction

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.

In the OpenStack ecosystem there are currently several tools that are helpful in carrying out the benchmarking process for an OpenStack deployment. To name a few, there are DevStack and FUEL, which are intended for deploying and managing OpenStack clouds, the Tempest testing framework which validates OpenStack APIs, some tracing facilities like Tomograph with Zipkin. The challenge, however, is to compile all these tools together on a reproducible basis. That can be a rather difficult task since the number of compute nodes in a practical deployment can easily be large and also because one may be willing to use many different deployment strategies that pursue different goals (e.g., while benchmarking the Nova Scheduler, one usually does not care of virtualization details, but is more concerned with the infrastructure topologies; while in other specific cases it may be the virtualization technology that matters). What Rally aims to do is Compile many already existing benchmarking facilities into one project, making it flexible to user requirements and ensuring the reproducibility of test results.

Architecture

Rally is split into 4 main components:

  1. Deployment Engine, which is responsible for processing and deploying VM images (using DevStack or FUEL according to users preferences). The engine can do one of the following:

    • deploy an Operating System (OS) on already existing VMs;
    • starting VMs from a VM image with pre-installed OS and OpenStack;
    • delpoying multiple VMs inside each OpenStack compute node based on a VM image.
  2. VM Provider, which interacts with cloud provider-specific interfaces to load and destroy VM images;

  3. Benchmarking Tool, which carries out the benchmarking process in several stages:

    • runs Tempest tests, reduced to 5-minute length (to save the usually expensive computing time);
    • runs the user-defined test scenarios (using the Rally testing framework);
    • collects all the test results and processes the by Zipkin tracer;
    • puts together a benchmarking report and stores it on the machine Rally was lauched on.
  4. Orchestrator, which is the central component of the system. It uses the Deployment Engine, to run control and compute nodes, in addition to launching an OpenStack distribution. After that, it calls the Benchmarking Tool to start the benchmarking process.

Wiki page:

https://wiki.openstack.org/wiki/Rally

Launchpad page:

https://launchpad.net/rally

Code is hosted on github:

https://github.com/stackforge/rally