elajkat 6d53058c39 Update rally-task-neutron to have only ovs as mech driver
Neutron recently introduced the experimental feature concept and moved
linuxbridge driver under it as it lacks maintainers and has more and
more issues with its testing.
To use experimental feature the experimental cfg group must be filled
with linuxbridge = True, but rally-task-neutron don't need linuxbridge
driver.
The patch that introduce experimental framework check [1].

[1]: https://review.opendev.org/c/openstack/neutron/+/845181
Related-Bug: #1980948

Change-Id: If2016c6b2cf03c064e2903549e0e991995275024
2022-07-12 10:23:39 +00:00
..
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2021-12-15 14:18:24 +02:00
2021-12-15 14:18:24 +02:00
2021-11-07 16:50:42 +01:00
2021-11-07 16:50:42 +01:00
2022-07-12 13:20:31 +03:00

Zuul V3 configuration

Zuul is a pipeline-oriented project gating system. It facilitates running tests and automated tasks in response to Code Review events.

See official doc for more details.

What do we have in this dir?

Note

Do not document all files and jobs here. It will (for sure) become outdated at some point.

  • zuul.yaml - the main configuration file. It contains a list of jobs which should be launched at CI for rally-openstack project
  • base.yaml - the second by importance file. It contains basic parent jobs.
  • All other files are named as like a job for which they include definition.

Where are the actual job playbooks?

Unfortunately, Zuul defines zuul.d (as like .zuul.d) as a directory for project configuration and job definitions.

Ansible roles, tasks cannot be here, so we placed them at tests/ci/playbooks directory.