7f0413c84c
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
20 lines
905 B
YAML
20 lines
905 B
YAML
---
|
|
prelude: >
|
|
Introduce the experimental features framework.
|
|
features:
|
|
- |
|
|
Some Neutron features are not supported due to lack of resources or
|
|
technical expertise to maintain them. As they arise, those features will
|
|
be marked as experimental by the Neutron core team.
|
|
Deployers will be able to continue using experimental features by
|
|
explicitly enabling them in the 'experimental' section of neutron.conf.
|
|
The ML2 linuxbridge driver is the first feature to be marked as
|
|
experimental. To continue using it, deployers have to set to True the
|
|
'linuxbridge' option in the 'experimental' section of neutron.conf.
|
|
deprecations:
|
|
- |
|
|
The ML2 linuxbridge agent has been marked as experimental due to lack
|
|
of resources to maintain it. To continue using it, deployers have to set
|
|
to True the 'linuxbridge' option in the 'experimental' section of
|
|
neutron.conf
|