openstack
/
tripleo-heat-templates
Code Issues Proposed changes

Environment to deploy BGPVPN with Bagpipe in a unique file 

From a single file you can configure both the service
  plugin and the driver to have full functionality

Change-Id: I99124ba04311fa083038234b79df0dae4eea1435
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
This commit is contained in:
Ricardo Noriega 2017-09-04 16:37:36 +02:00
parent 271a5c62a8
commit c70d81587e
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
environments/neutron-bgpvpn-bagpipe.yaml
View File

@ -2,22 +2,25 @@
# backend for BGPVPN service plugin
#
# The BaGPipe driver for the BGPVPN service plugin is designed to work jointly
# with the openvswitch ML2 mechanism driver. It relies on the use of the
# with the openvswitch ML2 mechanism driver. It relies on the use of the
# bagpipe-bgp BGP VPN implementation on compute node and the MPLS implementation
# in OpenVSwitch.
#
resource_registry:
OS::TripleO::Services::NeutronBgpVpnApi: ../puppet/services/neutron-bgpvpn-api.yaml
OS::TripleO::Services::NeutronBgpVpnBagpipe: ../puppet/services/neutron-bgpvpn-bagpipe.yaml
parameter_defaults:
NeutronServicePlugins: 'router,bgpvpn'
BgpvpnServiceProvider: 'BGPVPN:BaGPipe:networking_bgpvpn.neutron.services.service_drivers.bagpipe.bagpipe.BaGPipeBGPVPNDriver:default'
# Required (example)
# BapipeMyAs: 64512
# Optional (example)
# BapipeApiPort: 8082
# BapipeApiPort: 8084
# BapipeDataplaneDriverIpVpn: 'ovs'
# BapipeEnableRtc: true
# BapipeOvsBridge: br-mpls
# BapipePeers: 192.168.10.1,192.168.10.2
# BapipeProxyArp: true