Public bug reported:
Currently the code in DHCP agent scheduler counts only active agents that host
network.
In such case it may allow more agents to host the network than it is configured.
This is creates possibility of race condition when several DHCP agents start up
at the same time and try to get active networks.
The network gets hosted by several agents eventhough it might already be hosted
by other agents.
This just wastes ports/fixed ips from tenant's network range and increases load
on controllers.
It's better to let rescheduling mechanism to sort out active/dead agents
for each of networks.
** Affects: neutron
Importance: Medium
Assignee: Eugene Nikanorov (enikanorov)
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1506092
Title:
Count all network-agent bindings during scheduling
Status in neutron:
New
Bug description:
Currently the code in DHCP agent scheduler counts only active agents that
host network.
In such case it may allow more agents to host the network than it is
configured.
This is creates possibility of race condition when several DHCP agents start
up at the same time and try to get active networks.
The network gets hosted by several agents eventhough it might already be
hosted by other agents.
This just wastes ports/fixed ips from tenant's network range and increases
load on controllers.
It's better to let rescheduling mechanism to sort out active/dead
agents for each of networks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1506092/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
