DHCP agent scheduler filtering ignored when agent service restarted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Wishlist
|
Unassigned |
Bug Description
We have a Xena deployment based on Linux bridge networking, with a mix of Neutron managed VXLAN, and routed/L3 provider networks.
neutron-dhcp-agent services are deployed to a set of network nodes in order to serve the VXLAN networks. These services are also deployed to a subset of compute nodes which are the only hosts with access to the routed provider networks.
We would like the network nodes to be used in preference to the compute nodes when DHCP instances are created against VXLAN tenant networks. Having written a patch to achieve this (modifying the DHCP scheduler filtering - https:/
As far as I can tell, when the DHCP agent service starts up it requests details of the active networks and seeing a network it can reach which doesn't have the correct number of agents deployed, takes over this responsibility, bypassing the scheduling filters. The existing filters which ensure a DHCP service has physical access to a given L3 segment appear to work because there is a second implementation of that filtering in https:/
I'd appreciate a second opinion on whether by making changes to the DHCP scheduler filtering only, it should be reasonable to expect its rules to apply at times after initial network/subnet creation? If there is an architectural reason the filters don't get re-used, would my best option be to add further patching in dhcp_rpc to achieve the desired behaviour? Thanks
tags: | added: rfe |
Changed in neutron: | |
importance: | Undecided → Wishlist |
This is a kind of enhancement requests, so I added "rfe" tag for discussion.