Amended sphinx documents

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

Change-Id: I520b08202910ad476447fa09ca0a5993fc1bffc5
This commit is contained in:
Oleh Anufriiev 2014-07-30 20:41:05 +03:00
parent 7812a72cdd
commit 8e25d36fd8
8 changed files with 29 additions and 10 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 178 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 207 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 178 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 117 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 79 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 128 KiB

View File

@ -13,27 +13,46 @@
License for the specific language governing permissions and limitations
under the License.
Welcome to Rally's documentation!
What is Rally?
=================================
Rally is a benchmarking tool for the community that is capable of performing
specific, complex and reproducible tests for 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.
Source Documentation
--------------------
.. image:: ./images/Rally-Actions.png
:width: 50%
:align: center
Contents:
* Deploy engine is not yet another deployer of OpenStack, but just a pluggable mechanism that allows to unify & simplify work with different deployers like: DevStack, Fuel, Anvil on hardware/VMs that you have.
* Verification - (work in progress) uses tempest to verify the functionality of a deployed OpenStack cloud. In future Rally will support other OS verifiers.
* Benchmark engine - allows to create parameterized load on the cloud based on a big repository of benchmarks.
Deeper in Rally:
----------------
.. toctree::
:maxdepth: 3
overview
concepts
deploy_engines
server_providers
verify
installation
usage
Development information:
------------------------
.. toctree::
:maxdepth: 3
deploy
verify
benchmark
cmds
implementation
improve_rally
rally_gatejob
Indices and tables
------------------