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
2,938 Commits 1 Branch 21 Tags 123 MiB
Python 96.2%
HTML 3%
JavaScript 0.4%
Shell 0.3%
Go to file
Alexander Maretskiy 695dffec7f [Reports] Add an option for embedding JS/CSS libs into report 
This change allows running command `report' with `--html-static'
option so all required JS/CSS will be embedded to HTML file.
Having all required CSS/JS loaded directly from HTML makes
report working without access to the Internet.

Added third-party libraries files:
    rally/ui/templates/libs/nv.d3.1.1.15-beta.min.css
    rally/ui/templates/libs/angular.1.3.3.min.js
    rally/ui/templates/libs/nv.d3.1.1.15-beta.min.js
    rally/ui/templates/libs/d3.3.4.13.min.js

Notes about licenses compatibility:
    https://angularjs.org/
    https://github.com/angular/angular.js/blob/master/LICENSE
    The MIT License
    compatible with Apache License Version 2.0
    according to http://www.apache.org/legal/resolved.html

    http://d3js.org/
    https://github.com/mbostock/d3/blob/master/LICENSE
    BSD 3-clause License
    compatible with Apache License Version 2.0
    according to http://www.apache.org/legal/resolved.html

    http://nvd3.org/
    https://github.com/novus/nvd3/blob/master/LICENSE.md
    Apache License Version 2.0

Change-Id: I8913ecc585ee17affb1d8a0b29bb475c1e07427f
Closes-Bug: #1505533
 		2015-11-24 11:33:25 +02:00
certification/openstack Add quotation marks 2015-11-10 11:27:28 +08:00
devstack Use local.conf instead of localrc 2015-10-21 16:47:56 +03:00
doc Merge "[Spec]Add a spec for distiributed load generation" 2015-11-21 00:32:43 +00:00
etc [Reports] Add an option for embedding JS/CSS libs into report 2015-11-24 11:33:25 +02:00
rally [Reports] Add an option for embedding JS/CSS libs into report 2015-11-24 11:33:25 +02:00
rally-jobs Fix floating ip setting name in samples 2015-11-20 09:58:56 +11:00
samples Fix floating ip setting name in samples 2015-11-20 09:58:56 +11:00
tests [Reports] Add an option for embedding JS/CSS libs into report 2015-11-24 11:33:25 +02:00
.coveragerc Fix & Restore cover job 2015-10-06 07:58:37 +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
.testr.conf Reorganize test module structure 2014-10-07 13:50:40 +00:00
Dockerfile Make Docker Container work out of the box 2015-10-12 07:34:36 -07:00
LICENSE Initial commit 2013-08-03 09:17:25 -07:00
README.rst Add 'Who Is Using Rally' paragraph to the docs 2015-09-24 17:34:03 +03:00
babel.cfg Add rally.sample.conf to project 2013-08-14 14:08:09 +04:00
install_rally.sh Merge "install Rally in existing virtualenv" 2015-11-16 11:22:06 +00:00
openstack-common.conf Remove all non-incubated oslo code 2015-02-23 14:31:36 +00:00
optional-requirements.txt Add validate monasca service to authenticate.py 2015-10-19 14:59:11 -06:00
requirements.txt Updated from global requirements 2015-11-20 04:59:47 +00:00
setup.cfg Install data files in proper path 2015-06-10 18:46:43 +03:00
setup.py Updated from global requirements 2015-09-22 10:45:07 +00:00
test-requirements.txt Updated from global requirements 2015-11-20 04:59:47 +00:00
tox.ini Use config file for genconfig and update sample config 2015-08-07 14:08:43 +02: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

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 git.openstack.org:

http://git.openstack.org/cgit/openstack/rally

Code is mirrored on github:

https://github.com/openstack/rally