1d98f0a7d4
The DHCP agent will resync its state with Neutron to recover from any transient notification or RPC errors. Currently, the periodic resync task waits on a timer to determine whether a re-sync is necessary. The interval between attempts by default is 5 seconds and can be longer thru config. This may cause a potentially long delay before an agent gets new work via an agent_updated RPC call. The idea of this RFE is to change the timer based periodic resync task into an event driven one. It also proposes a new DHCP agent config option "resync_throttle" to ensure the minimum interval taken between resync state events to avoid too frequent resyncing. In this way, we could force the agent to act on the resync request immediately therefore decreasing how much time is needed before DHCP services are available. Co-authored-by: Allain Legacy <Allain.legacy@windriver.com> Closes-Bug: #1780370 Change-Id: Ie9d758ba5f750a38dc19ea5ce8b2c6b414f9ef80
Team and repository tags
Welcome!
To learn more about neutron:
- Documentation: https://docs.openstack.org
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute:
CONTRIBUTING.rst