dcf2d7b074
(types.ImageResourceType.transform method) 1. Changing sample scenario files to store image name as regexp. This will help avoid further issues with current image version of devstack and rally being out of sync. 2. Changing logic of _id_from_name method. name and regex keys from resource_config dictionary are treated the same, (as regexp) with name having priority. Going forward 'name' key should always be used, and 'regexp' key is to there to support legacy configurations. Also, exact check will be performed on resource name. 3. Related unit test changed correspodently.. 4. Added unit test for multiple maches of the same image name. Change-Id: Ie0fc509445a652384f78864ad7d491e34b5a4d88 |
||
|---|---|---|
| .. | ||
| contexts | ||
| runners | ||
| scenarios | ||
| sla | ||
| support | ||
| README.rst | ||
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 doc/samples/tasks/scenarios.
Section "runners" specifies the way, how task should be run. To learn more about runners configurations, see samples in doc/samples/tasks/runners.
Section "context" defines different types of environments in which task can be launched. Look at doc/samples/tasks/context for samples.
Section "sla" defines details for determining compliance with contracted values such as maximum error rate or minimum response time. Look at doc/samples/tasks/sla for samples.
See a detailed description of benchmark scenarios, contexts & runners.