yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1910533@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Sometimes in multistack spine&leaf topologies, when dhcp agents are run
on compute nodes there is a need to assign each network to be hosted by
all dhcp agents. Otherwise vms spawn on some of the sites may not get
properly configured IP addresses.

Of course this can be done by setting correct number in
"dhcp_agents_per_network" config option but this solution may not scale
well as it needs to be updated everytime when new nodes/sites are added.

So maybe better option would be to propose new dhcp scheduler class which can be used in such cases.
This new scheduler would simply always schedule all networks to the all dhcp agents which it will find in the deployment.

** Affects: neutron
     Importance: Wishlist
     Assignee: Slawek Kaplonski (slaweq)
         Status: New


** Tags: l3-ipam-dhcp rfe-triaged

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

Title:
  [RFE] New dhcp agents scheduler - use all agents for each network

Status in neutron:
  New

Bug description:
  Sometimes in multistack spine&leaf topologies, when dhcp agents are
  run on compute nodes there is a need to assign each network to be
  hosted by all dhcp agents. Otherwise vms spawn on some of the sites
  may not get properly configured IP addresses.

  Of course this can be done by setting correct number in
  "dhcp_agents_per_network" config option but this solution may not
  scale well as it needs to be updated everytime when new nodes/sites
  are added.

  So maybe better option would be to propose new dhcp scheduler class which can be used in such cases.
  This new scheduler would simply always schedule all networks to the all dhcp agents which it will find in the deployment.

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