Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-2976

Upstream: [BGP][I-P] Separate syncing of advertised routes to SB and processing of connected router.

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • OVN
    • None
    • 5
    • Hide

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) Integration test case are written and pass successfully

      ( ) The upstream pull request is merged upstream and pass CI

      Show
      Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) Integration test case are written and pass successfully ( ) The upstream pull request is merged upstream and pass CI
    • rhel-9
    • None
    • rhel-net-ovn
    • OVN FDP Sprint 14, OVN FDP Sprint 15, OVN FDP Sprint 16
    • 3

      This is tracking the upstream effort needed to deliver the feature request described below.

      Currently the "advertised_route_sync" engine node in northd takes care of synchronizing static and dynamic routes to SB. Both of them have separate node that takes care of actually aggregating the routes that should be advertised. There is one exception and that is if user sellected connected-as-host, those routes are aggregated during the en_advertised_route_sync_run(). That makes it hard to manage inputs of the sync. The goal is to separate the connected as host to another node, possibly into existing one or completely new one. This should make it easier to add I-P support for advertised routes.

       

      Note: The QE testing in this case should be sanity only, this change should be transparent to the user.

              amusil@redhat.com Ales Musil
              amusil@redhat.com Ales Musil
              OVN QE OVN QE
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: