neutron/zuul.d
Miguel Lavalle 7f0413c84c Implement experimental features framework
During the Zed PTG it was decided to handle unsupported features in
Neutron as experimental. See section titled "When we say something is
not supported?", day 2 in [1]. The agreement was:

"We keep existing jobs for linuxbridge driver for example, but when the
tests start to fail we skip them and finally we stop the job also.
To make it clear for operators we add warning logs highlighting that the
given feature/driver is experimental, and introduce cfg option to enable
such features explicitly."

This commit implements this agreement, initially with Linuxbridge

Depends-On: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/845646

[1] https://lists.openstack.org/pipermail/openstack-discuss/2022-April/028164.html

Change-Id: Ib18efa3f472736b58c8967847b1061da0e3897d7
2022-06-30 17:59:49 -05:00
..
base.yaml Set nslookup_target in FIPS jobs 2022-06-20 20:59:53 +05:30
grenade.yaml Switch tick-tick job to upgrade from xena 2022-06-06 19:06:51 +05:30
job-templates.yaml Drop lower-constraints.txt and its testing 2022-05-02 13:01:42 -05:00
project.yaml Drop lower-constraints.txt and its testing 2022-05-02 13:01:42 -05:00
rally.yaml Implement experimental features framework 2022-06-30 17:59:49 -05:00
tempest-multinode.yaml Implement experimental features framework 2022-06-30 17:59:49 -05:00
tempest-singlenode.yaml [fips jobs] blacklist AttachInterfacesTestJSON tempest test 2022-06-21 12:55:38 +05:30
tripleo.yaml Skip non-functional jobs on functional roles/playbooks changes 2022-05-31 11:32:39 +05:30