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

[EVPN] Configurable bridge/lo/vxlan interface names.

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • OVN
    • None
    • [EVPN] Configurable bridge/lo/vxlan interface names.
    • 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 switch LS1 with EVPN enabled and custom interface names defined in NB (other_config:dynamic-routing-bridge-name=custom-br-tenant, …-vxlan-if-name=custom-vxlan, …-advertise-if-name=custom-lo),

      When ovn-northd pushes that configuration and ovn-controller converges on a hypervisor that already has those interfaces present,

      Then querying the specific datapath with ovn-sbctl --columns=external_ids find Datapath_Binding logical_datapath=<LS1-UUID> shows all three keys (dynamic-routing-bridge-name, …-vxlan-if-name, …-advertise-if-name) set to the custom values and ovn-controller keeps the host-side interfaces named custom-br-tenant, custom-vxlan, and custom-lo.

      ( ) 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 switch LS1 with EVPN enabled and custom interface names defined in NB (other_config:dynamic-routing-bridge-name=custom-br-tenant, …-vxlan-if-name=custom-vxlan, …-advertise-if-name=custom-lo), When ovn-northd pushes that configuration and ovn-controller converges on a hypervisor that already has those interfaces present, Then querying the specific datapath with ovn-sbctl --columns=external_ids find Datapath_Binding logical_datapath=<LS1-UUID> shows all three keys (dynamic-routing-bridge-name, …-vxlan-if-name, …-advertise-if-name) set to the custom values and ovn-controller keeps the host-side interfaces named custom-br-tenant, custom-vxlan, and custom-lo. ( ) 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 feature?

      Make the host-side br-$vni, vxlan-$vni, lo-$vni interface names configurable for logical switches that have EVPN enabled (LS.other_config.dynamic-routing-vni=<VNI>).

      The names should be configured through new Logical Switch options, e.g.:

      • Logical_Switch.other_config:dynamic-routing-bridge-name=<value>
      • Logical_Switch.other_config:dynamic-routing-vxlan-if-name=<value>
      • Logical_Switch.other_config:dynamic-routing-advertise-if-name=<value>

      Why is it needed?

      This is needed for Layered Products that already have non-native EVPN integration and allows simpler upgrade procedures when moving to the OVN-native support.

      Who will benefit? 

      Layered products (OpenShift, OpenStack).

              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: