07727d2a4f
The create-update-delete stack scenario executes the following actions with using Heat: - creates the new stack (with some resources) - updates the stack and stack resoruces with the new template - deletes the stack. Unit-tests for the changes above are also included into patch. Patch also adds rally test cases for stack create-update-delete stack scenario (because rally tests require test scenario to be used by test case samples): Case 1: - Heat creates a new stack - Heat updates the stack with adding additional resource to the stack - Heat deletes the stack Case 2: - Heat creates a stack - Heat updates the stack with deleting some resource from the stack - Heat deletes the stack. Change-Id: I4c0ff24d0651434450a281a62670f1bd6c2a0000
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.