cf2853a36d
1. Following Rally plugin structure, create the kuryr plugin. 2. Add one scenario of listing the networks. 3. Add the task file to trigger the scenario. Currently, users can try this task (with rally installed) by running: rally --plugin-paths rally-jobs/plugins/ task start rally-jobs/tasks/scenarios/list_networks.json 4. Merge gal's update on the gate task yaml. implements blueprint: fullstack-testing Change-Id: Ie68c4f4f70a81cfeafe2b13e2a896570576a6892 |
||
---|---|---|
.. | ||
extra | ||
plugins | ||
tasks/scenarios | ||
kuryr.yaml | ||
README.rst |
Rally job related files
This directory contains rally tasks and plugins that are run by OpenStack CI.
Structure
- plugins - directory where you can add rally plugins. Almost everything in Rally is a plugin. Benchmark context, Benchmark scenario, SLA checks, Generic cleanup resources, ....
- extra - all files from this directory will be copy pasted to gates, so you are able to use absolute paths in rally tasks. Files will be located in ~/.rally/extra/*
- kuryr.yaml is a task that is run in gates against OpenStack with Kuryr and Neutron deployed
Useful links
- More about Rally: https://rally.readthedocs.org/en/latest/
- Rally release notes: https://rally.readthedocs.org/en/latest/release_notes.html
- How to add rally-gates: https://rally.readthedocs.org/en/latest/gates.html
- About plugins: https://rally.readthedocs.org/en/latest/plugins.html
- Plugin samples: https://github.com/openstack/rally/tree/master/samples/plugins