openstack/neutron
Code Issues Proposed changes
1b549eaf08
neutron/zuul.d/project.yaml

117 lines
4.7 KiB
YAML
Raw Normal View History

Move zuul jobs definitions to zuul.d directory We already have many different jobs defined for Zuul in Neutron repo. Up to now all those jobs were in .zuul.yaml file but this file growth really big and it was hard to read and navigate in it. So this patch proposes to move jobs definitions to zuul.d directory to separate yaml files per "job types". So there will be now separate files with definitions for: * grenade jobs, * base jobs like functional and fullstack, * rally jobs, * tempest multi node jobs, * tempest single node jobs, * tripleo jobs. And maybe others in the future. Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7
2019-11-27 12:16:12 +01:00
# NOTE: In doc/source/contributor/testing/ci_scenario_jobs.rst file there is
# document with summary of all tempest, neutron-tempest-plugin and grenade jobs
# summary.
# Please update this document always when any changes to jobs are made.
- project:
templates:
- neutron-tempest-plugin-jobs
- openstack-cover-jobs
- openstack-lower-constraints-jobs
Add Python3 xena unit tests This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for xena. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: Id13ad7e9dd8d40833680b0cf7b7612d648ba1ebe
2021-03-26 15:27:35 +00:00
- openstack-python3-xena-jobs
- openstack-python3-xena-jobs-arm64
Move zuul jobs definitions to zuul.d directory We already have many different jobs defined for Zuul in Neutron repo. Up to now all those jobs were in .zuul.yaml file but this file growth really big and it was hard to read and navigate in it. So this patch proposes to move jobs definitions to zuul.d directory to separate yaml files per "job types". So there will be now separate files with definitions for: * grenade jobs, * base jobs like functional and fullstack, * rally jobs, * tempest multi node jobs, * tempest single node jobs, * tripleo jobs. And maybe others in the future. Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7
2019-11-27 12:16:12 +01:00
- publish-openstack-docs-pti
- periodic-stable-jobs
- check-requirements
- release-notes-jobs-python3
check:
jobs:
Limit execution of the neutron CI jobs on some irrelevant file This patch tries to make execution of the CI jobs in the Neutron queue to be more smart. There is no need to e.g. run linuxbridge scenario jobs job when only changed files in patch are in e.g. the openvswitch agent module, or vice versa. Change-Id: Ie33514da28991fa5952a1d8c289402ecb9ffee49
2021-02-09 12:31:17 +01:00
- neutron-functional-with-uwsgi
- neutron-fullstack-with-uwsgi
- neutron-rally-task
- neutron-grenade-multinode
Switch neutron-grenade-dvr-multinode to be non voting temporary This job is very unstable due to related bug. As we are just before releasing new stable release, lets unblock our gate for now quickly by making it non-voting and removing it from the gate queue temporary. Change-Id: I971be39b50d521ea51090633ba465116a2118506 Related-Bug: #1920778
2021-03-22 16:09:06 +01:00
- neutron-grenade-dvr-multinode:
# TODO(slaweq): make that job voting when bug
# https://bugs.launchpad.net/neutron/+bug/1920778
# will be fixed
voting: false
Limit execution of the neutron CI jobs on some irrelevant file This patch tries to make execution of the CI jobs in the Neutron queue to be more smart. There is no need to e.g. run linuxbridge scenario jobs job when only changed files in patch are in e.g. the openvswitch agent module, or vice versa. Change-Id: Ie33514da28991fa5952a1d8c289402ecb9ffee49
2021-02-09 12:31:17 +01:00
- neutron-tempest-multinode-full-py3
- neutron-tempest-dvr-ha-multinode-full
- neutron-tempest-slow-py3
- neutron-tempest-ipv6-only
- neutron-ovn-tempest-ovs-release
- neutron-ovn-tempest-ovs-release-ipv6-only
Remove networking-midonet job from Neutron's check queue This job can't run on python 3 and it's failing 100% since long time. There is no point to run it like that now as it's only waste of infra resources. We will re-add this job to Neutron's check queue when it will be fixed. Change-Id: Id5b8fc484112e16c7b627b38af3440f1ce387ffb
2020-01-19 11:08:41 +01:00
# TODO(slaweq): add this job again to the check queue when it will be
# working fine on python 3
#- networking-midonet-tempest-aio-ml2-centos-7:
# voting: false
Enable neutron-ovn jobs in check queue Jobs: * neutron-ovn-tripleo-ci-centos-7-containers-multinode * neutron-ovn-rally were disabled during the process of migration of networking-ovn code to the neutron repo. Now those jobs should runs fine so lets enable them as non-voting jobs first. Additionally job "neutron-ovn-tripleo-ci-centos-7-containers-multinode" was in the meantime renamed to be the "neutron-ovn-tripleo-ci-centos-8-containers-multinode" as it runs on CentOS 8 now. Change-Id: I90e038767101e12ba94cdc7ed7431bc3e34b8044
2020-02-28 12:11:50 +01:00
- neutron-ovn-rally-task:
voting: false
Move zuul jobs definitions to zuul.d directory We already have many different jobs defined for Zuul in Neutron repo. Up to now all those jobs were in .zuul.yaml file but this file growth really big and it was hard to read and navigate in it. So this patch proposes to move jobs definitions to zuul.d directory to separate yaml files per "job types". So there will be now separate files with definitions for: * grenade jobs, * base jobs like functional and fullstack, * rally jobs, * tempest multi node jobs, * tempest single node jobs, * tripleo jobs. And maybe others in the future. Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7
2019-11-27 12:16:12 +01:00
# TripleO jobs that deploy OVN.
# Note we don't use a project-template here, so it's easier
# to disable voting on one specific job if things go wrong.
# In Stein and beyond, fs010 will run using
# networking-ovn-tripleo-ci-centos-7-containers-multinode.
# If you need any support to debug these jobs in case of
# failures, please reach us on #tripleo IRC channel.
Add Python3 xena unit tests This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for xena. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: Id13ad7e9dd8d40833680b0cf7b7612d648ba1ebe
2021-03-26 15:27:35 +00:00
- openstack-tox-py36: # from openstack-python3-xena-jobs template
Increase tox-py3{6,7} and lower-constraints timeout to 3600 seconds As seen in the reported bug, in heavy loaded CI systems, the Neutron openstack-tox-py3{6,7} and openstack-tox-lower-constraints jobs tend to timeout. Change-Id: I3f7aff297e8c1797eb23adac7b29dc65619c1e8a Closes-Bug: #1860332
2020-01-22 10:05:34 +00:00
timeout: 3600
Add Python3 xena unit tests This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for xena. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: Id13ad7e9dd8d40833680b0cf7b7612d648ba1ebe
2021-03-26 15:27:35 +00:00
- openstack-tox-py38: # from openstack-python3-xena-jobs template
Increate tox-py38 timeout to 3600 seconds Days after [1] was merged, [2] was merged too, adding a new CI job: py38. This patch amends [1] increasing the timeout for this new job. [1] https://review.opendev.org/#/c/703751 [2] https://review.opendev.org/#/c/693401 Change-Id: I128f3c4621d2354ac6b0d07ccf34b84862efe7de Closes-Bug: #1860332
2020-01-27 13:31:00 +00:00
timeout: 3600
Increase tox-py3{6,7} and lower-constraints timeout to 3600 seconds As seen in the reported bug, in heavy loaded CI systems, the Neutron openstack-tox-py3{6,7} and openstack-tox-lower-constraints jobs tend to timeout. Change-Id: I3f7aff297e8c1797eb23adac7b29dc65619c1e8a Closes-Bug: #1860332
2020-01-22 10:05:34 +00:00
- openstack-tox-lower-constraints: # from openstack-tox-lower-constraints template
timeout: 3600
Increase tox-cover timeout to 4800 seconds Change-Id: I2200329c9c5402562b84794f669177728794a5cd Related-Bug: #1860332
2020-01-29 17:23:24 +00:00
- openstack-tox-cover: # from openstack-cover-jobs template
timeout: 4800
Switch neutron-rally-task job to ML2/OVS and skip "test_models_sync" After switch of the default Neutron backend to the ML2/OVN in the Devstack we had 2 rally jobs running actually with the same Neutron backend. This patch configures explicitly ML2/OVS as a backend in the 'neutron-rally-task' job so it is like it was before the change in the Devstack repo. In order to fix the CI, this patch also skips "test_models_sync" test cases. Once [1] is fixed and released, we'll be able to create SQL tables specifying the "_constraints_included" flag. When creating a table, this flag should be set to "False" in order to be able to set the "index" and "unique" parameters for each column in the table definition, as we do now. "test_update_router_admin_state" is excluded from "neutron-ovn-tempest-slow" until LP#1890445 is fixed. Set "test_restart_wsgi_on_sighup_multiple_workers" as unstable. CI job "neutron-ovn-tempest-slow" has been set to non-voting until LP#1930402 is fixed. Related-Bug: #1929518 Related-Bug: #1890445 Related-Bug: #1930402 Related-Bug: #1930367 [1]https://github.com/sqlalchemy/alembic/issues/848 Change-Id: I38ed7931169434fecbbefa3762f51a522ef3c509
2021-05-14 08:31:32 +02:00
# TODO(ralonsoh): this job has been set to non-voting until LP#1930402
# is fixed.
- neutron-ovn-tempest-slow:
voting: false
Move zuul jobs definitions to zuul.d directory We already have many different jobs defined for Zuul in Neutron repo. Up to now all those jobs were in .zuul.yaml file but this file growth really big and it was hard to read and navigate in it. So this patch proposes to move jobs definitions to zuul.d directory to separate yaml files per "job types". So there will be now separate files with definitions for: * grenade jobs, * base jobs like functional and fullstack, * rally jobs, * tempest multi node jobs, * tempest single node jobs, * tripleo jobs. And maybe others in the future. Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7
2019-11-27 12:16:12 +01:00
gate:
jobs:
Promote -uwsgi jobs to be gating Uwsgi based jobs (functional, fullstack and tempest) are voting since some time and are as stable as "non-uwsgi" onces. Recently on the CI meeting we decided to move "non-uwsgi" functional and fullstack jobs to be run only in periodic queue and promote "uwsgi" jobs to be gating also. Change-Id: Id24316f04e1ff619c8ce2fe475f873961cbb92e4
2020-08-12 12:17:39 +02:00
- neutron-functional-with-uwsgi
- neutron-fullstack-with-uwsgi
Remove tempest-integrated-networking job from neutron queue As we agreed during virtual PTG we want to change tempest-multinode-full-py3 that it will run only integrated-networking tests. And then promote it to be voting and gating job. This new multinode job can replace singlenode tempest-integrated-networking job so this patch removes this one from the queues too. Change-Id: Ic61b636625824bbd6b7624a057db308a484ee463
2020-06-17 14:29:05 +02:00
- neutron-tempest-multinode-full-py3
Move zuul jobs definitions to zuul.d directory We already have many different jobs defined for Zuul in Neutron repo. Up to now all those jobs were in .zuul.yaml file but this file growth really big and it was hard to read and navigate in it. So this patch proposes to move jobs definitions to zuul.d directory to separate yaml files per "job types". So there will be now separate files with definitions for: * grenade jobs, * base jobs like functional and fullstack, * rally jobs, * tempest multi node jobs, * tempest single node jobs, * tripleo jobs. And maybe others in the future. Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7
2019-11-27 12:16:12 +01:00
- neutron-grenade-multinode
Switch neutron-grenade-dvr-multinode to be non voting temporary This job is very unstable due to related bug. As we are just before releasing new stable release, lets unblock our gate for now quickly by making it non-voting and removing it from the gate queue temporary. Change-Id: I971be39b50d521ea51090633ba465116a2118506 Related-Bug: #1920778
2021-03-22 16:09:06 +01:00
# TODO(slaweq): make that job gating when bug
# https://bugs.launchpad.net/neutron/+bug/1920778
# will be fixed
# - neutron-grenade-dvr-multinode
Switch neutron-rally-task job to ML2/OVS and skip "test_models_sync" After switch of the default Neutron backend to the ML2/OVN in the Devstack we had 2 rally jobs running actually with the same Neutron backend. This patch configures explicitly ML2/OVS as a backend in the 'neutron-rally-task' job so it is like it was before the change in the Devstack repo. In order to fix the CI, this patch also skips "test_models_sync" test cases. Once [1] is fixed and released, we'll be able to create SQL tables specifying the "_constraints_included" flag. When creating a table, this flag should be set to "False" in order to be able to set the "index" and "unique" parameters for each column in the table definition, as we do now. "test_update_router_admin_state" is excluded from "neutron-ovn-tempest-slow" until LP#1890445 is fixed. Set "test_restart_wsgi_on_sighup_multiple_workers" as unstable. CI job "neutron-ovn-tempest-slow" has been set to non-voting until LP#1930402 is fixed. Related-Bug: #1929518 Related-Bug: #1890445 Related-Bug: #1930402 Related-Bug: #1930367 [1]https://github.com/sqlalchemy/alembic/issues/848 Change-Id: I38ed7931169434fecbbefa3762f51a522ef3c509
2021-05-14 08:31:32 +02:00
# TODO(obondarev): this job is disabled untill switched back to OVS
#- neutron-tempest-slow-py3
Switch tempest jobs to neutron specific ones In neutron CI queues we were running tempest-slow-py3 and tempest-ipv6-only jobs which are defined in tempest repository and runs all tests, e.g related to Swift or Cinder. This patch defines new jobs: "neutron-tempest-slow-py3" and "neutron-tempest-ipv6-only" which inherits from the tempest jobs but disables Cinder and Swift services. Additionally "neutron-tempest-ipv6-only" job now runs only "integrated-networking" tox_envlist. Change-Id: Icd376c144e1993ca84890c76743fda4196662d9b
2021-01-13 15:42:17 +01:00
- neutron-tempest-ipv6-only
Revert "Disable neutron-ovn-tempest-ovs-release temporarily" This reverts commit 5b12d808aa3255a595bc2f8ee01411819b5b72f3. Fixes for this issue on nova's side [1] and [2] are already merged so let's make neutron-ovn job voting again. [1] https://review.opendev.org/#/c/705760 [2] https://review.opendev.org/#/c/706213/ Change-Id: I1117a8195af5a5b3eb2faa7a920e9d66747846dc
2020-02-10 10:09:16 +00:00
- neutron-ovn-tempest-ovs-release
[OVN] Make OVN IPv6 job voting again This job neutron-ovn-tempest-ovs-release-ipv6-only was broken due to a os-vif misconfiguration which is now fixed by https://review.opendev.org/#/c/753575. Change-Id: I7c89659e0de130f0c4b720ee7489d895a308f69d Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
2020-11-12 09:27:39 +00:00
- neutron-ovn-tempest-ovs-release-ipv6-only
Add Python3 xena unit tests This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for xena. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: Id13ad7e9dd8d40833680b0cf7b7612d648ba1ebe
2021-03-26 15:27:35 +00:00
- openstack-tox-py36: # from openstack-python3-xena-jobs template
Increase tox-py3{6,7} and lower-constraints timeout to 3600 seconds As seen in the reported bug, in heavy loaded CI systems, the Neutron openstack-tox-py3{6,7} and openstack-tox-lower-constraints jobs tend to timeout. Change-Id: I3f7aff297e8c1797eb23adac7b29dc65619c1e8a Closes-Bug: #1860332
2020-01-22 10:05:34 +00:00
timeout: 3600
- openstack-tox-lower-constraints: # from openstack-tox-lower-constraints template
timeout: 3600
Switch neutron-rally-task job to ML2/OVS and skip "test_models_sync" After switch of the default Neutron backend to the ML2/OVN in the Devstack we had 2 rally jobs running actually with the same Neutron backend. This patch configures explicitly ML2/OVS as a backend in the 'neutron-rally-task' job so it is like it was before the change in the Devstack repo. In order to fix the CI, this patch also skips "test_models_sync" test cases. Once [1] is fixed and released, we'll be able to create SQL tables specifying the "_constraints_included" flag. When creating a table, this flag should be set to "False" in order to be able to set the "index" and "unique" parameters for each column in the table definition, as we do now. "test_update_router_admin_state" is excluded from "neutron-ovn-tempest-slow" until LP#1890445 is fixed. Set "test_restart_wsgi_on_sighup_multiple_workers" as unstable. CI job "neutron-ovn-tempest-slow" has been set to non-voting until LP#1930402 is fixed. Related-Bug: #1929518 Related-Bug: #1890445 Related-Bug: #1930402 Related-Bug: #1930367 [1]https://github.com/sqlalchemy/alembic/issues/848 Change-Id: I38ed7931169434fecbbefa3762f51a522ef3c509
2021-05-14 08:31:32 +02:00
# TODO(ralonsoh): this job has been disabled until LP#1930402 is fixed.
#- neutron-ovn-tempest-slow:
Increase tox-py3{6,7} and lower-constraints timeout to 3600 seconds As seen in the reported bug, in heavy loaded CI systems, the Neutron openstack-tox-py3{6,7} and openstack-tox-lower-constraints jobs tend to timeout. Change-Id: I3f7aff297e8c1797eb23adac7b29dc65619c1e8a Closes-Bug: #1860332
2020-01-22 10:05:34 +00:00
#- neutron-ovn-rally-task
Switch tripleo based job to be run on Centos 8 Change-Id: I737a837ab76240d710e93cc7ea82c33f5e7acc2a
2020-01-07 11:54:57 +01:00
#- neutron-ovn-tripleo-ci-centos-8-containers-multinode
Move zuul jobs definitions to zuul.d directory We already have many different jobs defined for Zuul in Neutron repo. Up to now all those jobs were in .zuul.yaml file but this file growth really big and it was hard to read and navigate in it. So this patch proposes to move jobs definitions to zuul.d directory to separate yaml files per "job types". So there will be now separate files with definitions for: * grenade jobs, * base jobs like functional and fullstack, * rally jobs, * tempest multi node jobs, * tempest single node jobs, * tripleo jobs. And maybe others in the future. Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7
2019-11-27 12:16:12 +01:00
experimental:
jobs:
Move some non-voting jobs to the experimental queue To give some relief to Zuul resources, lets move non-voting jobs which are broken and failing all the time to the experimental queue for now. We can bring them back to check queue when we will fix them. Change-Id: I4c4dd7a17ea7cc483bb4b3ed7cff7ee91f917ed9
2021-01-14 17:19:26 +01:00
- neutron-grenade-ovn
- neutron-tempest-with-uwsgi-loki
- neutron-ovn-tempest-full-multinode-ovs-master
[OVN] Add single node tempest job with OVN master branch (exp. pipeline) This patch adds a new single node tempest job with OVN master branch to the experimental pipeline because sometimes we need to test a feature that is not yet included in the packaged version of OVN. We do have a multi node job with OVN master branch in the experimetal pipeline at the moment but, it's broken due to https://review.opendev.org/c/zuul/zuul-jobs/+/762650. So it's no use at the moment. Depends-On: https://review.opendev.org/c/openstack/devstack/+/781971 Change-Id: I3f21ddc9ec97f2fa7ccb467893a37eb1b5342542 Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
2021-03-24 14:01:58 +00:00
- neutron-ovn-tempest-ovs-master
Move tempest job with neutron-lib master to the experimental queue The job neutron-tempest-with-neutron-lib-master is mostly to check if current neutron changes will work fine with some changes done in neutron-lib. It isn't really needed to run it on all patches and can be rune on demand by running experimental queue if that is needed. This patch also removes job neutron-ovn-tempest-ovs-master from the experimental queue as we already have there similar multinode job. As job neutron-ovn-tempest-ovs-master wasn't used anywhere, this patch also removes its definition. Finally this patch improves ci_scenario_jobs document and adds there info about experimental queue and what is there currently. Change-Id: I0fc4ffd5db2673cefcd01307555d1a3900bb12e8
2021-02-04 11:24:09 +01:00
- neutron-tempest-with-neutron-lib-master
Move zuul jobs definitions to zuul.d directory We already have many different jobs defined for Zuul in Neutron repo. Up to now all those jobs were in .zuul.yaml file but this file growth really big and it was hard to read and navigate in it. So this patch proposes to move jobs definitions to zuul.d directory to separate yaml files per "job types". So there will be now separate files with definitions for: * grenade jobs, * base jobs like functional and fullstack, * rally jobs, * tempest multi node jobs, * tempest single node jobs, * tripleo jobs. And maybe others in the future. Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7
2019-11-27 12:16:12 +01:00
periodic:
jobs:
- neutron-functional
Promote -uwsgi jobs to be gating Uwsgi based jobs (functional, fullstack and tempest) are voting since some time and are as stable as "non-uwsgi" onces. Recently on the CI meeting we decided to move "non-uwsgi" functional and fullstack jobs to be run only in periodic queue and promote "uwsgi" jobs to be gating also. Change-Id: Id24316f04e1ff619c8ce2fe475f873961cbb92e4
2020-08-12 12:17:39 +02:00
- neutron-fullstack
Move zuul jobs definitions to zuul.d directory We already have many different jobs defined for Zuul in Neutron repo. Up to now all those jobs were in .zuul.yaml file but this file growth really big and it was hard to read and navigate in it. So this patch proposes to move jobs definitions to zuul.d directory to separate yaml files per "job types". So there will be now separate files with definitions for: * grenade jobs, * base jobs like functional and fullstack, * rally jobs, * tempest multi node jobs, * tempest single node jobs, * tripleo jobs. And maybe others in the future. Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7
2019-11-27 12:16:12 +01:00
- neutron-tempest-postgres-full
- neutron-tempest-mariadb-full
- neutron-tempest-with-os-ken-master
- neutron-ovn-tempest-ovs-master-fedora
Make all periodic jobs to be voting It's easier to check what was wrong if jobs in periodic queue are voting. It will not block any development so it is safe to do that. Change-Id: I038f83afb1fd47de8570f526e594c4c69f4bfe19
2021-02-02 11:10:44 +01:00
- devstack-tobiko-faults-centos:
voting: true
Move "Co-gating" jobs to the periodic queue To use less infra resources by every Neutron patch, let's move co-gating jobs, like Ironic, Openstacksdk and Tripleo based jobs to the periodic queue. Those jobs will be still run daily so we should have pretty good coverage if (and when) some neutron change broke those projects but we will use less infra resources by running jobs for every patch proposed to Neutron. Change-Id: I91c55c9151a11401bd3a7fbe94e378a027bc97df
2021-01-19 17:09:00 +01:00
- ironic-tempest-ipa-wholedisk-bios-agent_ipmitool-tinyipa
- openstacksdk-functional-devstack-networking
- tripleo-ci-centos-8-content-provider
- neutron-centos-8-tripleo-standalone:
Make all periodic jobs to be voting It's easier to check what was wrong if jobs in periodic queue are voting. It will not block any development so it is safe to do that. Change-Id: I038f83afb1fd47de8570f526e594c4c69f4bfe19
2021-02-02 11:10:44 +01:00
voting: true
Move "Co-gating" jobs to the periodic queue To use less infra resources by every Neutron patch, let's move co-gating jobs, like Ironic, Openstacksdk and Tripleo based jobs to the periodic queue. Those jobs will be still run daily so we should have pretty good coverage if (and when) some neutron change broke those projects but we will use less infra resources by running jobs for every patch proposed to Neutron. Change-Id: I91c55c9151a11401bd3a7fbe94e378a027bc97df
2021-01-19 17:09:00 +01:00
vars: &consumer_vars
consumer_job: true
build_container_images: false
remove_tags:
- build
dependencies: &consumer_deps
- tripleo-ci-centos-8-content-provider
- neutron-ovn-tripleo-ci-centos-8-containers-multinode:
vars: *consumer_vars
dependencies: *consumer_deps
Add periodic jobs to test "nftables" binaries In order to check how the "nftables" binaries work with Neutron, two new jobs have been added to the periodic queue: - neutron-tempest-plugin-scenario-linuxbridge-nftables - neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-nftables In those two jobs, the binaries for "iptables", "ip6tables", "arptables" and "ebtables" are replaced with the "nftables" counterparts; by default, newer operating systems use the "nftables" versions, providing the legacy API to the user but executing the new packet handling in Netfilter. Change-Id: Idec6d480886298f6d71b1dd649c9255ee6b7bebb Related-Bug: #1508155 Related-Bug: #1922892
2021-04-07 10:56:09 +00:00
- neutron-tempest-plugin-scenario-linuxbridge-nftables
- neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-nftables
Copy Permalink