openstack/rally-openstack
Code Issues Proposed changes
A collection of plugins for Rally framework designed for the OpenStack platform.
3,897 Commits 1 Branch 13 Tags 18 MiB
Python 99.4%
HTML 0.3%
Shell 0.3%
c2b57d6a63
Go to file
Boris Pavlovic c2b57d6a63 [CI] Fix Cinder update volume type scenario & service 
Now it's required to provide name (non backward compatible change
from Cinder team) this patch address the problem and unblocks our gate

Change-Id: I71874c7789c55d655262f131ace4c8eacc835bd8
2018-01-01 10:45:12 -08:00
devstack Switch everything to rally db 2017-08-29 13:25:41 -07:00
doc Fix the misspelling of "configuration" and "scenario" 2017-12-25 13:44:25 +08:00
etc [CLI] Improve Rally DB UX 2017-11-13 15:57:13 -08:00
rally [CI] Fix Cinder update volume type scenario & service 2018-01-01 10:45:12 -08:00
rally-jobs Modify Bgpvpn scenarios to test true bgpvpn 2017-12-14 17:42:52 +01:00
samples Modify Bgpvpn scenarios to test true bgpvpn 2017-12-14 17:42:52 +01:00
tasks Add task for getting OpenStack key performance metrics 2017-10-13 15:00:53 -07:00
tests [CI] Fix Cinder update volume type scenario & service 2018-01-01 10:45:12 -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 Update .gitreview file to reflect repo rename 2015-04-18 00:37:36 +00:00
bindep.txt [install] Add iputils to bindep 2016-12-30 18:37:41 +03:00
CONTRIBUTING.rst [docs][6] Re-design docs to cover all user-groups 2017-01-10 11:25:00 -08:00
Dockerfile [docker] Fix configuration 2017-12-10 23:44:32 +02:00
LICENSE Initial commit 2013-08-03 09:17:25 -07:00
README.rst Fixup Rally Tutorial Page Link in README 2017-06-25 19:37:54 -07:00
requirements.txt Merge "Add correct version for pyOpenSSL" 2017-11-25 11:54:58 +00:00
setup.cfg Reword samples and setup.cfg 2017-08-03 22:24:56 +00:00
setup.py Updated from global requirements 2015-09-22 10:45:07 +00:00
test-requirements.txt [requirements] Stop using upper limits for all cases 2017-11-06 17:28:31 +02:00
tox.ini [ci] Split legacy-rally-dsvm-cli job 2017-12-01 14:35:35 +02:00
upper-constraints.txt Simplify usage of docker container 2017-12-10 01:06:26 +02:00

README.rst

Rally

Team and repository tags

image

Latest Version

Gitter Chat

Trello Board

Apache License, Version 2.0

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