diff options
authorFeng Pan <fpan@redhat.com>2018-04-13 17:47:09 -0400
committerTim Rozet <trozet@redhat.com>2018-04-19 04:15:10 +0000
commitd2e2b0a96806fa5eef2090d934f9e09372ce5074 (patch)
parent3df29834f02d09d4976ca42dbe04d494506848da (diff)
Change flat network name for nosdn fdio scenario
Since we use networking-vpp's router functionality, we need to create a tap interface on VPP to connect to br-ex on the host for external connectivity. Change-Id: Ia25db8456f1ad6beb96c7b9b5f318b166ef4576a Signed-off-by: Feng Pan <fpan@redhat.com> (cherry picked from commit f19a086d771a1719bbd5d94a18f2ba1e5e243d61)
1 files changed, 5 insertions, 2 deletions
diff --git a/environments/neutron-ml2-vpp.yaml b/environments/neutron-ml2-vpp.yaml
index e497013..ade976d 100644
--- a/environments/neutron-ml2-vpp.yaml
+++ b/environments/neutron-ml2-vpp.yaml
@@ -17,7 +17,10 @@ parameter_defaults:
NeutronNetworkType: vlan
NeutronServicePlugins: vpp-router
NeutronTypeDrivers: vlan,flat
+ NeutronFlatNetworks: external
- # Use Linux Bridge driver for DHCP and L3 agent.
+ # Use Linux Bridge driver for DHCP agent.
neutron::agents::dhcp::interface_driver: "neutron.agent.linux.interface.BridgeInterfaceDriver"
- neutron::agents::l3::interface_driver: "neutron.agent.linux.interface.BridgeInterfaceDriver"
+ # Create VPP tap0 interface and connect it to br-ex linux bridge for external connectivity.
+ fdio::vpp_exec_commands: ["create tap host-if-name vpp_ext_tap host-bridge br-ex rx-ring-size 1024 tx-ring-size 1024", "set interface state tap0 up"]