openstack/rally-openstack
Code Issues Proposed changes
A collection of plugins for Rally framework designed for the OpenStack platform.
2,406 Commits 1 Branch 13 Tags 18 MiB
Python 99.4%
HTML 0.3%
Shell 0.3%
70c6500d72
Go to file
Lv Fumei 70c6500d72 Modify nested_level from dict to integer 
In function create_nested_snapshots_and_attach_volume, nested_level's
default value is 1, and it is used to operate with an integer
(for i in range(nested_level - 1):).

Change-Id: I4879d7cdcb5a56b83a1415c4a8fc427241ddc913
Closes-Bug: #1594656
2016-06-21 14:55:18 +08:00
devstack Create deployment conf depend on identity version 2016-06-08 15:16:37 +00:00
doc [Requirements] Remove `fixtures' package 2016-06-06 15:38:44 +03:00
etc Merge "[Verify] Add tempest configs and move to new section" 2016-06-09 17:16:36 +00:00
rally Merge "Mark several cleanup resources as tenant_resource" 2016-06-19 23:16:09 +00:00
rally-jobs Merge "Mark several cleanup resources as tenant_resource" 2016-06-19 23:16:09 +00:00
samples Modify nested_level from dict to integer 2016-06-21 14:55:18 +08:00
tests Merge "Revert "Gate: prepopulate cluster with one server"" 2016-06-18 09:54:24 +00:00
.coveragerc Integrate Rally & Alembic 2016-01-29 11:24:16 +00:00
.dockerignore Fix docker build command 2015-11-10 16:33:29 -08:00
.gitignore [gates] Convert Rally to the new Devstack plugin model 2015-09-03 23:00:09 -07:00
.gitreview Update .gitreview file to reflect repo rename 2015-04-18 00:37:36 +00:00
Dockerfile [Docs] Add cli reference to docs 2016-02-26 16:31:03 +02:00
LICENSE Initial commit 2013-08-03 09:17:25 -07:00
README.rst fix up the formatting of the readme for the announce script 2016-04-19 15:18:34 -04:00
requirements.txt Updated from global requirements 2016-06-08 22:04:28 +00:00
setup.cfg Drop python 2.6 classifier 2015-11-19 14:39:01 +02:00
setup.py Updated from global requirements 2015-09-22 10:45:07 +00:00
test-requirements.txt Updated from global requirements 2016-05-28 00:39:43 +00:00
tox.ini Documentation tox fix 2016-02-29 13:12:22 +00: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