openstack/rally
Code Issues Proposed changes

Fix 2 typos and 2 invalid links in doc

Browse Source 
Change-Id: Id08449f0beacc33687284f6766cfdc80f62dfc5d
This commit is contained in:
Kai Zhang 2014-10-30 23:22:54 +08:00
parent f6c02ea246
commit 2732e196ee
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/samples/tasks/README.rst
View File

@ -35,8 +35,8 @@ more about runners configurations, see samples in `doc/samples/tasks/runners
<https://github.com/stackforge/rally/tree/master/doc/samples/tasks/runners>`_.
Section "context" defines different types of environments in which task can
be launched. Look at `doc/samples/tasks/context
<https://github.com/stackforge/rally/tree/master/doc/samples/tasks/context>`_
be launched. Look at `doc/samples/tasks/contexts
<https://github.com/stackforge/rally/tree/master/doc/samples/tasks/contexts>`_
for samples.
Section "sla" defines details for determining compliance with contracted values
@ -46,4 +46,4 @@ Look at `doc/samples/tasks/sla
samples.
See a `detailed description of benchmark scenarios, contexts & runners
<https://github.com/stackforge/rally/tree/master/doc/source/benchmark.rst>`_.
<https://github.com/stackforge/rally/tree/master/doc/source/concepts.rst>`_.

4
doc/source/concepts.rst
View File

@ -224,7 +224,7 @@ User's view
From the user's prospective, contexts in Rally are manageable via the **task configuration files**. In a typical configuration file, each benchmark scenario to be run is not only supplied by the information about its arguments and how many times it should be launched, but also with a special **"context"** section. In this section, the user may configure a number of contexts he needs his scenarios to be run within.
In the example below, the **"users" context** specifies that the *"NovaServers.boot_server"* scenario should be run from **1 tenant** having **3 users** in it. Bearing in mind that the default quota for the number of instances is 10 instances pro tenant, it is also reasonable to extend it to, say, **20 instances** in the **"quotas" context**. Otherwise the scenario would eventually fail, since it tries to boot a server 15 times from a single tenant.
In the example below, the **"users" context** specifies that the *"NovaServers.boot_server"* scenario should be run from **1 tenant** having **3 users** in it. Bearing in mind that the default quota for the number of instances is 10 instances per tenant, it is also reasonable to extend it to, say, **20 instances** in the **"quotas" context**. Otherwise the scenario would eventually fail, since it tries to boot a server 15 times from a single tenant.
.. parsed-literal::
@ -332,7 +332,7 @@ Put the plugin into the **/opt/rally/plugins** or **~/.rally/plugins** directory
Creation
^^^^^^^^
Inherit a class for you plugin from base class for scenario, runner or context depends on what type of plugin you want create.
Inherit a class for your plugin from base class for scenario, runner or context depends on what type of plugin you want create.
See more information about `scenarios <ScenariosDevelopment>`_, `runnres <RunnersDevelopment>`_ and `contexts <ContextDevelopment>`_ creation.