yahoo-eng-team team mailing list archive

[Assaf Muller <amuller@xxxxxxxxxx>]

Public bug reported:

While overlay networks are typically available on every host, flat or
VLAN provider networks are often not. It may be the case where each rack
only has access to a subset of networks defined in Neutron (Determined
by the network's physical_network tag). In these cases, you would
install a DHCP agent in every rack, but the DHCP scheduler could
schedule a network to the wrong agent, and you end up in a situation
where the dnsmasq instance is on the wrong rack and has no reachability
to its VMs.

More information may be found here:
https://etherpad.openstack.org/p/Network_Segmentation_Usecases.
Specifically "DHCP agents and metadata serices are run on nodes within each L2.  When the neutron network is created we specifically assign the dhcp agent in that segment to that network".

** Affects: neutron
     Importance: Undecided
     Assignee: Assaf Muller (amuller)
         Status: In Progress

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

Title:
  DHCP agent scheduler can schedule dnsmasq to an agent without
  reachability to the network its supposed to serve

Status in neutron:
  In Progress

Bug description:
  While overlay networks are typically available on every host, flat or
  VLAN provider networks are often not. It may be the case where each
  rack only has access to a subset of networks defined in Neutron
  (Determined by the network's physical_network tag). In these cases,
  you would install a DHCP agent in every rack, but the DHCP scheduler
  could schedule a network to the wrong agent, and you end up in a
  situation where the dnsmasq instance is on the wrong rack and has no
  reachability to its VMs.

  More information may be found here:
  https://etherpad.openstack.org/p/Network_Segmentation_Usecases.
  Specifically "DHCP agents and metadata serices are run on nodes within each L2.  When the neutron network is created we specifically assign the dhcp agent in that segment to that network".

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