Count all network-agent bindings during scheduling
Bug #1506092 reported by
Eugene Nikanorov
This bug report is a duplicate of:
Bug #1388698: dhcp_agents_per_network does not work appropriately..
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
In Progress
|
Medium
|
Eugene Nikanorov | ||
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.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to neutron (master) | #1 |
| Changed in neutron: | |
| status: | New → In Progress |
| tags: | added: l3-ipam-dhcp |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on neutron (master) | #2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/