Fix texts and images in docs

* Reuse the images from the repository in README
* Shrink the images to 800-1000px
* Fix incorrect sectioning, typos, missing info etc. on ReadTheDocs
* Add a tutorial step about the --abort-on-sla-failure feature
* Move Rally deployment engines to a separate tutorial step
* rally use deployment -> rally deployment use

Change-Id: Id5f492e40a041aa3308e9faa21b833220415323d
This commit is contained in:
Mikhail Dubov 2015-02-16 03:37:58 +03:00
parent 5d53b4465c
commit 90ca881e84
18 changed files with 2 additions and 5 deletions

View File

@ -17,8 +17,7 @@ The OpenStack QA team mostly works on CI/CD that ensures that new patches don't
**Rally** workflow can be visualized by the following diagram: **Rally** workflow can be visualized by the following diagram:
.. image:: https://wiki.openstack.org/w/images/e/ee/Rally-Actions.png .. image:: doc/source/images/Rally-Actions.png
:width: 700px
:alt: Rally Architecture :alt: Rally Architecture
@ -43,8 +42,7 @@ Use Cases
There are 3 major high level Rally Use Cases: There are 3 major high level Rally Use Cases:
.. image:: https://wiki.openstack.org/w/images/6/6e/Rally-UseCases.png .. image:: doc/source/images/Rally-UseCases.png
:width: 700px
:alt: Rally Use Cases :alt: Rally Use Cases

Binary file not shown.

Before

Width:  |  Height:  |  Size: 182 KiB

After

Width:  |  Height:  |  Size: 94 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 135 KiB

After

Width:  |  Height:  |  Size: 76 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 207 KiB

After

Width:  |  Height:  |  Size: 137 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 178 KiB

After

Width:  |  Height:  |  Size: 172 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 117 KiB

After

Width:  |  Height:  |  Size: 103 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 79 KiB

After

Width:  |  Height:  |  Size: 66 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 128 KiB

After

Width:  |  Height:  |  Size: 114 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 116 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 131 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 37 KiB

After

Width:  |  Height:  |  Size: 47 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 35 KiB

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 30 KiB

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 31 KiB

After

Width:  |  Height:  |  Size: 39 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 54 KiB

After

Width:  |  Height:  |  Size: 72 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 57 KiB

After

Width:  |  Height:  |  Size: 75 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 78 KiB

After

Width:  |  Height:  |  Size: 109 KiB

View File

@ -19,7 +19,6 @@ What is Rally?
**OpenStack** is, undoubtedly, a really *huge* ecosystem of cooperative services. **Rally** is a **benchmarking tool** that answers the question: **"How does OpenStack work at scale?"**. To make this possible, Rally **automates** and **unifies** multi-node OpenStack deployment, cloud verification, benchmarking & profiling. Rally does it in a **generic** way, making it possible to check whether OpenStack is going to work well on, say, a 1k-servers installation under high load. Thus it can be used as a basic tool for an *OpenStack CI/CD system* that would continuously improve its SLA, performance and stability. **OpenStack** is, undoubtedly, a really *huge* ecosystem of cooperative services. **Rally** is a **benchmarking tool** that answers the question: **"How does OpenStack work at scale?"**. To make this possible, Rally **automates** and **unifies** multi-node OpenStack deployment, cloud verification, benchmarking & profiling. Rally does it in a **generic** way, making it possible to check whether OpenStack is going to work well on, say, a 1k-servers installation under high load. Thus it can be used as a basic tool for an *OpenStack CI/CD system* that would continuously improve its SLA, performance and stability.
.. image:: ./images/Rally-Actions.png .. image:: ./images/Rally-Actions.png
:width: 100%
:align: center :align: center