yahoo-eng-team team mailing list archive

[Kevin Benton <1464361@xxxxxxxxxxxxxxxxxx>]

For now I don't think we are going to go forward with this because it's
a very invasive change and there isn't a really strong demand for it.
Let's revisit this if necessary after the routed networks and other
model changes happen during mitaka that are designed to help with large
operator use cases like this.

** Changed in: neutron
       Status: Confirmed => Won't Fix

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

Title:
  Support for multiple gateways in Neutron subnets

Status in neutron:
  Won't Fix

Bug description:
  Currently, the subnets in Neutron only support one gateway. For
  provider networks in large data centers, quite often, the architecture
  is such a way that multiple gateways are configured for the subnets.
  These multiple gateways are typically spread across backplanes  so
  that the production traffic can be load-balanced between backplanes.

  This is just my use case for supporting multiple gateways, but other
  folks might have more use cases as well.

  I want to open up a discussion on this topic and figure out the best
  way to handle this. Should this be done in a same way as dns-
  nameserver, with a separate table with two columns:  gateway_ip,
  subnet_id.

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