openstack/rally-openstack
Code Issues Proposed changes
A collection of plugins for Rally framework designed for the OpenStack platform.
683 Commits 1 Branch 13 Tags 18 MiB
Python 99.4%
HTML 0.3%
Shell 0.3%
eb4d082c60
Go to file
Sergey Skripnick eb4d082c60 Add new script for gate jobs 
This script will run scenario specified by $RALLY_SCENARIO
environment variable.

Also tags now supported. Tags are stand for modifying
deployment or environment somehow.

Currently implemented only "v3" tag. This tag is changing
deployment endpoints to use keystone v3 protocol.

For example we want to run two scenarios: one for keysone v2
and one for v3. Then we need to create two files:

my-rally.yaml    # will be run vs keystone v2 (v2 is used by default)
my-rally_v3.yaml # will be run vs keystone v3

And export $RALLY_SCENARIO=my-rally.yaml

Change-Id: I44d1788e3892be59afbf8eaecb5d3e3b995fc3a8
2015-02-19 23:23:15 +01:00
doc Publishing functional tests reports 2015-02-10 06:49:46 +02:00
etc/rally Fix defect of 'separate log level for Rally' 2014-11-19 22:11:17 +02:00
rally Add Mistral benchmark 2015-02-06 16:56:53 +04:00
rally-jobs Add new script for gate jobs 2015-02-19 23:23:15 +01:00
samples Merge "Add update + add/delete resource cases" 2015-02-13 12:04:49 +00:00
tests Merge "Add aliases "rally task|deployment|verify use"" 2015-02-19 13:37:42 +00:00
.coveragerc Omit openstack/common/ in test coverage reports 2014-01-16 00:53:49 +04:00
.gitignore Prepare documentation for readthedocs 2014-06-05 17:45:51 +03:00
.gitreview Add .gitreview file 2013-09-06 19:37:42 +04:00
Dockerfile Add Dockerfile 2014-12-24 14:22:19 +02:00
LICENSE Initial commit 2013-08-03 09:17:25 -07:00
README.rst Mention Rally ReadTheDocs in README 2015-02-11 18:42:40 +03:00
requirements.txt Updated from global requirements 2015-02-17 20:43:25 +00:00
setup.cfg Fix all py3 related issues 2015-01-26 15:18:36 +00:00
setup.py Fix bash completition setup 2014-10-13 23:24:24 +04:00
test-requirements.txt Updated from global requirements 2014-11-20 14:13:38 +00:00
tox.ini Replace ' with " in rally/benchmark and tests/unit 2015-02-05 15:15:56 -06: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

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

Rally documentation:

http://rally.readthedocs.org/en/latest/

Rally step-by-step tutorial:

http://rally.readthedocs.org/en/latest/tutorial.html

RoadMap:

https://docs.google.com/a/mirantis.com/spreadsheets/d/16DXpfbqvlzMFaqaXAcJsBzzpowb_XpymaK2aFY2gA2g

Launchpad page:

https://launchpad.net/rally

Code is hosted on github:

https://github.com/stackforge/rally