Make explicit the network backend used in the CI jobs
All Neutron CI jobs (except for unit, functional and fullstack jobs),
have explicitly defined the network backend used:
- linuxbridge
- ovs
- ovn
That was discussed and approved during the Neutron CI meetings [1].
[1]https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-06-15-15.00.log.html
Depends-On: https://review.opendev.org/c/openstack/neutron/+/797051
Change-Id: I4d18ef3e3adf24cf646e0546e7c38145f5a4aa92
diff --git a/zuul.d/project.yaml b/zuul.d/project.yaml
index c876579..7a3afc2 100644
--- a/zuul.d/project.yaml
+++ b/zuul.d/project.yaml
@@ -64,11 +64,11 @@
irrelevant-files: *tempest-irrelevant-files
- devstack-plugin-ceph-tempest-py3:
irrelevant-files: *tempest-irrelevant-files
- - neutron-grenade-multinode:
+ - neutron-ovs-grenade-multinode:
irrelevant-files: *tempest-irrelevant-files
- grenade:
irrelevant-files: *tempest-irrelevant-files
- - neutron-tempest-dvr:
+ - neutron-ovs-tempest-dvr:
voting: false
irrelevant-files: *tempest-irrelevant-files
- interop-tempest-consistency:
@@ -85,7 +85,7 @@
jobs:
- tempest-slow-py3:
irrelevant-files: *tempest-irrelevant-files
- - neutron-grenade-multinode:
+ - neutron-ovs-grenade-multinode:
irrelevant-files: *tempest-irrelevant-files
- tempest-full-py3:
irrelevant-files: *tempest-irrelevant-files
@@ -102,7 +102,7 @@
irrelevant-files: *tempest-irrelevant-files
- tempest-all:
irrelevant-files: *tempest-irrelevant-files
- - neutron-tempest-dvr-ha-multinode-full:
+ - neutron-ovs-tempest-dvr-ha-multinode-full:
irrelevant-files: *tempest-irrelevant-files
- nova-tempest-v2-api:
irrelevant-files: *tempest-irrelevant-files