ravikumar-venkatesan 9180e74757 Adds Designate domain-update test
This submission adds create_and_update_domain method to
rally/benchmark/scenarios/designate/basic.py.

Adds update method to "utils.py" under
"rally/benchmark/scenarios/designate".

Added configuration files for designate update-domain
operation under samples/tasks/scenarios/designate.
1) create-and-update-domain.json
2) create-and-update-domain.yaml

Also added unit tests to 'test_basic.py' and 'test_utils.py'
under 'rally/tests/unit/plugins/openstack/scenarios/designate'.
Change-Id: I58468666c0eb73143a0a451466ba41d12a9076d6
2015-12-22 08:38:14 +00:00
..
2015-08-22 05:25:33 +05:30
2015-04-20 14:02:43 +05:30

Tasks Configuration Samples

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

JSON schema of input task format:

:

{
    "type": "object",
    "$schema": "http://json-schema.org/draft-04/schema",
    "patternProperties": {
        ".*": {
            "type": "array",
            "items": {
                "type": "object",
                "properties": {
                    "args": {
                        "type": "object"
                    },
                    "runner": {
                        "type": "object",
                        "properties": {
                            "type": {"type": "string"}
                        },
                        "required": ["type"]
                    },
                    "context": {
                        "type": "object"
                    },
                    "sla": {
                        "type": "object"
                    },
                },
                "additionalProperties": False
            }
        }
    }
}

For humans:

::
{
"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.