yahoo-eng-team team mailing list archive

[Ryan Tidwell <1577572@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

It would extremely helpful if Neutron were able to determine whether
there is a mechanism operating on an external network that can handle
advertising next-hops to upstream routers. "Fast-exit" DVR
(https://bugs.launchpad.net/neutron/+bug/1577488) is an example of a use
case where a framework for providing this information inside Neutron
would be useful. With the Mitaka release BGP dynamic routing
functionality was added to Neutron. BGP dyanmic routing exposes the
concept of bindings between networks and BGP processes, which can
provide the information described above. However, this is not a generic
approach that supports other routing providers such as IPv6 proxy ND,
OSPF, or other routing technology. What is needed is a framework that
allows Neutron to ask whether there is a mechanism operating on an
external or provider network that is handling routing traffic.

To this end I'm proposing the creation of a simple, yet generic
framework in Neutron that allows any number of "routing providers" to be
registered with Neutron. Each routing provider is able to answer the
question "do you route to next-hops on network X?". Among other things,
this answer allows fast-exit DVR to be enabled dynamically based on
whether appropriate routing is in place without placing more config file
burden on operators or having tenants set attributes on a router to get
fast-exit treatment.

** Affects: neutron
     Importance: Wishlist
         Status: Confirmed


** Tags: l3-ipam-dhcp rfe

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

Title:
  [RFE] Routing providers framework

Status in neutron:
  Confirmed

Bug description:
  It would extremely helpful if Neutron were able to determine whether
  there is a mechanism operating on an external network that can handle
  advertising next-hops to upstream routers. "Fast-exit" DVR
  (https://bugs.launchpad.net/neutron/+bug/1577488) is an example of a
  use case where a framework for providing this information inside
  Neutron would be useful. With the Mitaka release BGP dynamic routing
  functionality was added to Neutron. BGP dyanmic routing exposes the
  concept of bindings between networks and BGP processes, which can
  provide the information described above. However, this is not a
  generic approach that supports other routing providers such as IPv6
  proxy ND, OSPF, or other routing technology. What is needed is a
  framework that allows Neutron to ask whether there is a mechanism
  operating on an external or provider network that is handling routing
  traffic.

  To this end I'm proposing the creation of a simple, yet generic
  framework in Neutron that allows any number of "routing providers" to
  be registered with Neutron. Each routing provider is able to answer
  the question "do you route to next-hops on network X?". Among other
  things, this answer allows fast-exit DVR to be enabled dynamically
  based on whether appropriate routing is in place without placing more
  config file burden on operators or having tenants set attributes on a
  router to get fast-exit treatment.

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