yahoo-eng-team team mailing list archive

[OpenStack Infra <1780370@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/580548
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1d98f0a7d43bc45b66260053bde76d992fd613b8
Submitter: Zuul
Branch:    master

commit 1d98f0a7d43bc45b66260053bde76d992fd613b8
Author: Kailun Qin <kailun.qin@xxxxxxxxx>
Date:   Fri Jul 6 20:20:08 2018 +0800

    Event driven periodic resync task for DHCP agents
    
    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@xxxxxxxxxxxxx>
    
    Closes-Bug: #1780370
    Change-Id: Ie9d758ba5f750a38dc19ea5ce8b2c6b414f9ef80


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1780370

Title:
  [RFE] Replace the timer based periodic resync task of DHCP agents with
  an event driven one

Status in neutron:
  Fix Released

Bug description:
  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. 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 a event driven one. We could force the agent to act on the resync
  request immediately therefore decreasing how much time is needed
  before DHCP services are available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1780370/+subscriptions