rally-openstack/samples/tasks
Jesse Keating 349efd5330 Replace deprecated max_failure_precent sla
The new sla is a failure_rate with min/max sub-keys. Update the
documentation and examples to reflect this.

Change-Id: Id947e4684aa84fe7d6c239a28b92e2a893ddaf66
2015-01-26 13:03:29 -08:00
..
contexts Moving rally/doc/samples to rally/samples 2015-01-16 05:54:09 -08:00
runners Update location to samples 2015-01-21 10:13:19 -08:00
scenarios Add cinder scenario: create volume from volume(clone) 2015-01-22 15:41:53 +02:00
sla Replace deprecated max_failure_precent sla 2015-01-26 13:03:29 -08:00
support Moving rally/doc/samples to rally/samples 2015-01-16 05:54:09 -08:00
README.rst Update location to samples 2015-01-21 10:13:19 -08:00

Tasks Configuration Samples

To specify your tasks, use configuration files in json or yaml format.

General structure of configuration file: :

{
    "ScenarioClass.scenario_method":
        "args": {
            ...
        },
        "runner": {
            ...
        },
        "context": {
            ...
        }
        "sla": {
            ...
        }
    }
}

ScanarioClass should be a subclass of the base Scenario class and scenario_method specifies what benchmark task should be run. Section "args" is also related to scenario. To learn more about scenarios configuration, see samples in samples/tasks/scenarios.

Section "runners" specifies the way, how task should be run. To learn more about runners configurations, see samples in samples/tasks/runners.

Section "context" defines different types of environments in which task can be launched. Look at samples/tasks/contexts for samples.

Section "sla" defines details for determining compliance with contracted values such as maximum error rate or minimum response time. Look at samples/tasks/sla for samples.

See a detailed description of benchmark scenarios, contexts & runners.