yahoo-eng-team team mailing list archive

[Thomas Morin <1717560@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When a user wants a VM with multiple interfaces, if DHCP gives a default
route for all of the corresponding subnets, the actual interface that
will actually be used as a default is not easily predictable (depends on
the order in which interfaces are enabled in the VM, and on when DHCP
offers are received and processed).

A solution to this can be to *not* set a default gateway on the subnets
which we don't want to use as a default, but it is only applicable if
there is no need to use these interfaces to reach one or more (non
default) prefixes.

In the case where one interface needs to be the default and one or more
other interfaces are used to reach other subnets via a router, what
people most often do is have custom teaks via cloud-init that fix
routing, but this is of course cumbersome.

This is an RFE for introducing an API extension for a new
'default_route' attribute on the subnet resource, this attribute would
default to true (current behavior), and that could be set to false by a
user whenever there is a need to *not* have a default route on the
router.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: 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/1717560

Title:
  allow to have no default route in DHCP host routes

Status in neutron:
  New

Bug description:
  When a user wants a VM with multiple interfaces, if DHCP gives a
  default route for all of the corresponding subnets, the actual
  interface that will actually be used as a default is not easily
  predictable (depends on the order in which interfaces are enabled in
  the VM, and on when DHCP offers are received and processed).

  A solution to this can be to *not* set a default gateway on the
  subnets which we don't want to use as a default, but it is only
  applicable if there is no need to use these interfaces to reach one or
  more (non default) prefixes.

  In the case where one interface needs to be the default and one or
  more other interfaces are used to reach other subnets via a router,
  what people most often do is have custom teaks via cloud-init that fix
  routing, but this is of course cumbersome.

  This is an RFE for introducing an API extension for a new
  'default_route' attribute on the subnet resource, this attribute would
  default to true (current behavior), and that could be set to false by
  a user whenever there is a need to *not* have a default route on the
  router.

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