Change flat network name for nosdn fdio scenario
[apex-tripleo-heat-templates.git] / environments / neutron-ml2-vpp.yaml
1 # Environment file used to enable networking-vpp ML2 mechanism driver
2
3 resource_registry:
4   OS::TripleO::Services::NeutronOvsAgent: OS::Heat::None
5   OS::TripleO::Services::ComputeNeutronOvsAgent: OS::Heat::None
6   OS::TripleO::Services::NeutronVppAgent: ../puppet/services/neutron-vpp-agent.yaml
7   OS::TripleO::Services::Etcd: ../puppet/services/etcd.yaml
8   OS::TripleO::Services::Vpp: ../puppet/services/vpp.yaml
9   OS::TripleO::Services::NeutronL3Agent: OS::Heat::None
10
11 parameter_defaults:
12   #Comma delimited list of <physical_network>:<VPP Interface>.
13   #Example: "datacentre:GigabitEthernet2/2/0"
14   #NeutronVPPAgentPhysnets: ""
15
16   NeutronMechanismDrivers: vpp
17   NeutronNetworkType: vlan
18   NeutronServicePlugins: vpp-router
19   NeutronTypeDrivers: vlan,flat
20   NeutronFlatNetworks: external
21   ExtraConfig:
22     # Use Linux Bridge driver for DHCP agent.
23     neutron::agents::dhcp::interface_driver: "neutron.agent.linux.interface.BridgeInterfaceDriver"
24     # Create VPP tap0 interface and connect it to br-ex linux bridge for external connectivity.
25     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"]
26