yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1509431@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1509431

Title:
  [RFE] Enhance BGP Dynamic Routing with L2VPN/L3VPN support

Status in neutron:
  Expired

Bug description:
  In BGP Dynamic Routing [1], on behalf of an OpenStack region, BGP
  Speakers advertise external reachability information to upstream
  (physical) routers. BGP Dynamic Routing alleviates the need to
  provision upstream routers whenever reachable subnets or floating IP
  addresses are added.

  In a public data center environment, BGP Dynamic Routing is limited to
  internet reachability. For some tenants, access to the public Internet
  is not enough. They may have networks connecting OpenStack routers to
  upstream L2VPNs or L3VPNs. This enhancement extends the scope of BGP
  Dynamic Routing so that it works with those upstream L2VPNs/L3VPNs.
  The BGP Speakers associate the routes that they advertise with
  L2VPNs/L3VPNs. The intention is to leverage both the BGP Dynamic
  Routing and BGPVPN [2] frameworks, bringing aspects of both together
  and adding functionality to associate advertised routes with the
  appropriate L2VPNs/L3VPNs.

  With BGP Dynamic Routing, the internal operation of OpenStack (between
  compute nodes, and between compute nodes and network nodes) remains
  untouched, using any of the variants and features available in
  OpenStack. This RFE does not propose any data plane changes.

  The reference implementation will use BGP EVPN Prefix Advertisement
  [3], based on EVPN Route Type 5 (EVPN IP Prefix Route) specifying a
  recursion through a GW IP address, linking to an EVPN Route Type 2
  (MAC/IP). The data plane will use VXLAN encapsulation on the networks
  connecting to the outside world (1).

  The initial scope will be network nodes only. Subsequent enhancements
  will extend support to DVR.

  (1) It is currently under investigation whether the networks
  connecting to the outside world must be specified as external gateway
  networks from OpenStack routers. A separate RFE will be filed to add
  VXLAN encapsulation support on external networks, if necessary.

  [1] https://blueprints.launchpad.net/neutron/+spec/bgp-dynamic-routing

  [2] http://docs.openstack.org/developer/networking-bgpvpn/

  [3] draft-ietf-bess-evpn-prefix-advertisement

  Proposed spec: https://review.openstack.org/322654

  Patch in networking-bgpvpn project:
  add vni to bgpvpn table https://review.openstack.org/#/c/332711/
  bgpvpn driver to notify neutron-dyanmic-routing https://review.openstack.org/340800

  Patch in neutron-dynamic-routing:
  bgpvpn binding to bgp speaker https://review.openstack.org/341273
  l3 vpn support https://review.openstack.org/345829
  EVPN support will be added soon.

  python-neutron-client patch:
  https://review.openstack.org/#/c/341308/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1509431/+subscriptions