93b8a3301c
The new task format was introduced recently. It unifies different sections and tries to make the things a bit simpler. Rally task consists of subtasks. Their amount should be at least one. The subtask is a group of workloads. Soon, it will be possible to define a single SLA for all workloads in a subtask and even more - use once executed contexts for workloads (i.e. create temporary users, network not for each workload but for a group of them). The workload is a combination of different plugins to be executed for a test. The most important are Scenario plugin (what will be executed in each iteration), runner (how the load should be generated) and contexts (what resources should be precreated before the workload). One scenario with different runners/contexts can create different load. To distinguish them the new section "description" of workload was introduced. It allows to add a custom description for a workload which will be dispayed in the report files. In case of missing "description" section, the description of scenario will be taken. Also, I need to mention that "failure_rate: 0" SLA is a default now, so there is no need to specify it. Change-Id: If99e8c722d9ccb18b8b9d7e12214e76e483a2016 |
||
---|---|---|
api-ref | ||
bin | ||
devstack | ||
doc | ||
etc | ||
neutron | ||
rally-jobs | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pylintrc | ||
.stestr.conf | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
TESTING.rst | ||
babel.cfg | ||
bindep.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
Welcome!
To learn more about neutron:
- Documentation: https://docs.openstack.org
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute:
CONTRIBUTING.rst