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

[BGP] dynamic-routing - only learn routes that thave rtm_protocol > RTPROT_STATIC.

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • OVN
    • None
    • [BGP] dynamic-routing - only learn routes that thave rtm_protocol > RTPROT_STATIC
    • False
    • False
    • Hide

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

      ( ) The acceptance criteria defined below are met.

      Given a logical router with options:dynamic-routing=true monitoring a VRF table containing 3 BGP-learned routes (rtm_protocol=186) and 2 static routes (rtm_protocol=4),

      When ovn-controller processes the VRF route table via netlink notifications,

      Then exactly 3 Advertised_Route records appear in the OVN southbound database with prefixes matching the BGP routes and 0 records for the static routes.

      ( ) The epics work is available in a downstream build (nightly/async or other)

      ( ) Test coverage is available in downstream CI if applicable

      ( ) All cards under the epic have been moved to Done

      ( ) Failed Test Plans have bugs added as children to the epic/feature.

      Show
      Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. Given a logical router with options:dynamic-routing=true monitoring a VRF table containing 3 BGP-learned routes (rtm_protocol=186) and 2 static routes (rtm_protocol=4), When ovn-controller processes the VRF route table via netlink notifications, Then exactly 3 Advertised_Route records appear in the OVN southbound database with prefixes matching the BGP routes and 0 records for the static routes. ( ) The epics work is available in a downstream build (nightly/async or other) ( ) Test coverage is available in downstream CI if applicable ( ) All cards under the epic have been moved to Done ( ) Failed Test Plans have bugs added as children to the epic/feature.
    • FDP-2753 - OVN-Kubernetes native BGP convergence
    • rhel-9
    • FDP-2753OVN-Kubernetes native BGP convergence
    • rhel-net-ovn
    • 100% To Do, 0% In Progress, 0% Done
    • ssg_networking

      This epic tracks all the effort needed to deliver the solution related to the feature request described below.

      What's the bug?

      When a logical router is configured to learn dynamic routes (LR.options:dynamic-routing=true) it currently learns all the non-OVN routes that are present in the VRF table it monitors.

      It's actually problematic if routes in the VRF are a combination of:

      • ovn installed routes
      • FRR (BGP/OSPF/etc) installed dynamic routes (these have rtm_protocol > RTPROT_STATIC)
      • user configured static routes

      OVN(-controller) will also learn the latter as static routes.  Arguably this is a bug because the OVN feature is about "dynamic-routing".  Moreover, if a user shares the VRF with OVN and wishes OVN to use the static routes it could just explicitly configure them in the NB database as Logical_Router_Static_Route records.

      ovn-controller should filter routes it learns and only learn those that were externally learned (likely through a dynamic routing protocol) and are marked as such in the VRF table (rtm_protocol > RTPROT_STATIC).

      Why is it needed?

      To enable the CMS (ovn-kubernetes) to share the VRF OVN monitors and updates when dynamic routing is configured.

      Who will benefit? 

      ovn-kubernetes transitioning to use OVN's native BGP support.  Potentially neutron-ovn too.

              ovnteam@redhat.com OVN Team
              dceara@redhat.com Dumitru Ceara
              OVN QE OVN QE
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: