yahoo-eng-team team mailing list archive

[Armando Migliaccio <1468236@xxxxxxxxxxxxxxxxxx>]

** Changed in: neutron
       Status: Triaged => 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/1468236

Title:
  enable neutron support distributed DHCP agents

Status in neutron:
  Won't Fix

Bug description:
  the current DHCP service in neutron is centralized, it suffers from several ailments in the large-scale scenarios
  1. VM can't get IP at booting time, the most serious is that leads to metadata service   can't work.
  2. DHCP agent need much time to reboot if it has served for a large VMs.
  3. network node has a large number of namespaces, especially in public cloud, there are so many tenants and private networks.

  I think we can run dhcp-agent across all compute nodes, but it does not completely like current DVR, the main difference are as below:
  1. it simplify the dhcp-agent scheduler in neutron-server, when we create a VM, neutron-server just send the RPC message by port host id.
  2. the dhcp-agent running on a compute node just serve the VMs on this compute node, if this dhcp-agent down, it just affect the VMs running on this node.
  3. move the network-binding-dhcp-agent from neutron-server to dhcp-agent, it can remove the race hapens between neutron-server multi-workers.

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