yahoo-eng-team team mailing list archive

[OpenStack Infra <1920065@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/815265
Committed: https://opendev.org/openstack/neutron-dynamic-routing/commit/8a0ddf6051c81b982187bb062b194284398f5703
Submitter: "Zuul (22348)"
Branch:    master

commit 8a0ddf6051c81b982187bb062b194284398f5703
Author: Dr. Jens Harbott <harbott@xxxxxxxxxx>
Date:   Mon Oct 25 11:50:24 2021 +0200

    Add a StaticScheduler without automatic scheduling
    
    The automatic scheduling that was introduced in [0] is having some
    issues. Add a StaticScheduler that can be used as an alternative for
    deployments that want explicit control over where their BGP speakers are
    getting scheduled.
    
    Add a job that runs with the new scheduler.
    
    [0] https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/478455
    
    Depends-On: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/815294
    Closes-Bug: 1920065
    Signed-off-by: Dr. Jens Harbott <harbott@xxxxxxxxxx>
    Change-Id: Ib7fcd0c7371bc75089b10024ee1b6e75c98f0188


** 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/1920065

Title:
  Automatic rescheduling of BGP speakers on DrAgents

Status in neutron:
  Fix Released

Bug description:
  In case when dynamic routing agent becomes unreachable, neutron takes
  these actions:

  1. Remove all BGP speakers from unreachable agents
  2. Schedule all unassigned BGP speakers on available DrAgents

  This behavior can be undesirable, in the following cases:

  1. Speakers are removed from DrAgent, even if there is no other
  alive agent running. Sometimes, I'd prefer them to stay configured
  exactly where they are, and come back after DrAgent is back online,
  after the server is restarted or so. This sometimes leads to situations,
  especially when there is only one active DrAgent, that speakers are
  not configured on any DrAgent at all.

  2. Sometimes it is desirable to let operator control which components
  are running where. For example, not every node running DrAgent has
  reachability to all iBGP peers, and network designer places route
  reflectors, DrAgents, BGP speakers, in their appropriate places, keeping
  in mind high availability and other concerns. In these setups, it could
  be better to let the speaker fail on DrAgent which is down. Moving speaker
  to another DrAgent also means that the source IP address for the BGP
  session will also change, which sometimes can be not so good to reconfigure
  on the other side of BGP peering, and not predictable at all.

  These situations may happen after following change was introduced:
  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/478455

  My proposal is to add a configuration flag to control this behavior:
  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/780675

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