rally-openstack/samples/tasks
ravikumar-venkatesan 723d76c783 Adds Nova keypair tests
This submission adds three methods to
rally/benchmark/scenarios/nova/utils.py
1) def create_keypair
2) def list_keypairs
3) def delete_keypair
Adds new file test_keypairs.py for nova
keypair scenarios

Added configuration files for keypair operations under
samples/tasks/scenarios/nova
1) create-and-list-keypairs.json
2) create-and-list-keypairs.yaml
3) create-and-delete-keypair.json
4) create-and-delete-keypair.yaml
5) boot-and-delete-server-with-keypairs.json
6) boot-and-delete-server-with-keypairs.yaml

Added unittests to test_utils.py and test_keypairs.py under
tests/unit/benchmark/scenarios/nova

Change-Id: Ic90d94d3dc925a9f225f760bfc550bf3e82e80b8
2015-02-23 10:14:25 +00: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 Adds Nova keypair tests 2015-02-23 10:14:25 +00: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.