From c53f747b1a96e696a44d6962e7624f49640e6a61 Mon Sep 17 00:00:00 2001 From: Slawek Kaplonski Date: Tue, 21 Apr 2020 13:16:12 +0200 Subject: [PATCH] Set Neutron's l3_ha flag to True in standalone ML2/OVS job Even if this is standalone job, when l3_ha config option is set to True in Neutron server, all routers will be created as HA routers. So for each such router created during the tests things like keepalived, neutron-keepalived-state-change-monitor will be spawned and also HA network will be created for tenants used by Tempest. This will give us better coverage of things which are most commonly used in Neutron. Depends-On: https://review.opendev.org/721799 Change-Id: I44ed60e88723e58ff1bb7bd0559540a596442f5a --- ci/environments/scenario007-standalone.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/ci/environments/scenario007-standalone.yaml b/ci/environments/scenario007-standalone.yaml index 82e80fd277..0523ce08b8 100644 --- a/ci/environments/scenario007-standalone.yaml +++ b/ci/environments/scenario007-standalone.yaml @@ -32,6 +32,7 @@ parameter_defaults: NeutronServicePlugins: 'router,qos,segments,trunk' NeutronVniRanges: ['1:4094', ] NeutronEnableDVR: false + NeutronL3HA: true KernelIpNonLocalBind: 0 Debug: true DockerPuppetDebug: True