openstack/rally-openstack

History

Cédric Savignan d6f8c33baf Modify Bgpvpn scenarios to test true bgpvpn Currently the bgpvpn scenarios test only a record in the database when a bgpvpn is created and associated with a network or a router. To test a true bgpvpn and not only a record in the neutron database a active port need to be created in the network associated to the bgpvpn. This change add a server which belong to a network in the context of all the bgpvpn scenarios concerned. If a bgpvpn driver is used on the openstack, a true bgpvpn is created. Change-Id: I64fb6bacf7866332ea55b3c5792bb23db366decd		2017-12-14 17:42:52 +01:00
..
contexts	Add router in context	2017-06-22 14:14:43 +02:00
runners	[Core] Add support for default platform and rally self job	2017-03-27 20:04:14 +03:00
scenarios	Modify Bgpvpn scenarios to test true bgpvpn	2017-12-14 17:42:52 +01:00
sla	Implement new random name generator for keystone scenarios	2015-10-16 08:00:21 -05:00
support	Deprecate install_test.sh script	2017-10-09 17:31:51 +03:00
README.rst	Reword samples and setup.cfg	2017-08-03 22:24:56 +00:00

README.rst

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

}

]

}

Scenario Plugin should be a subclass of the base Scenario class and implement run() method. 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 scenarios, contexts & runners.