yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1910533@xxxxxxxxxxxxxxxxxx>]

After longer investigation it seems for me that our existing scheduler can already schedule network to the dhcp agents "per segment". If subnet has segment configured it will filter host candidates per that segment in https://github.com/openstack/neutron/blob/4381f792c8bd8e5d309ed50288dd4a15a3628e0f/neutron/api/rpc/agentnotifiers/dhcp_rpc_agent_api.py#L205
So this RFE doesn't makes sense really and I'm closing it now.

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

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

Status in neutron:
  Won't Fix

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