Functional tests to explicitly use ML2/OVS

The Neutron project is changing DevStack to default to the ML2/OVN
mechanism driver by default [0] but, a handful of functinal tests
for openstacksdk is not backend agnostic (see the Story linked with this
patch) and needs to be adapted or skipped when running with ML2/OVN. As
a first step, just to unblock the DevStack gate this patch is explicitly
configuring the functional tests to run against ML2/OVS.

[0] ML2/OVS is and will be still full supported by the community.

Change-Id: I374b03130310e17b01d2b992eebe70658617e297
Story: 2007919
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
This commit is contained in:
Lucas Alvares Gomes 2020-07-13 15:33:32 +01:00
parent 0ebfffe835
commit c9f6b1043d
1 changed files with 15 additions and 0 deletions

View File

@ -44,7 +44,22 @@
vars:
devstack_localrc:
Q_ML2_PLUGIN_EXT_DRIVERS: qos,port_security
Q_AGENT: openvswitch
Q_ML2_TENANT_NETWORK_TYPE: vxlan
Q_ML2_PLUGIN_MECHANISM_DRIVERS: openvswitch
devstack_services:
# OVN services
ovn-controller: false
ovn-northd: false
ovs-vswitchd: false
ovsdb-server: false
q-ovn-metadata-agent: false
# Neutron services
q-agt: true
q-dhcp: true
q-l3: true
q-metering: true
q-svc: true
# sdk doesn't need vnc access
n-cauth: false
n-novnc: false