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

QE verification: [EVPN] Configurable bridge/lo/vxlan interface names.

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • ovn26.03
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      ( ) The bug has been reproduced and verified by QE members
      ( ) Test coverage has been added to downstream CI
      ( ) For new feature, failed test plans have bugs added as children to the epic
      ( ) The bug is cloned to any relevant release that we support and/or is needed

      Show
      ( ) The bug has been reproduced and verified by QE members ( ) Test coverage has been added to downstream CI ( ) For new feature, failed test plans have bugs added as children to the epic ( ) The bug is cloned to any relevant release that we support and/or is needed
    • rhel-9
    • None

      This ticket is tracking the QE verification effort for the solution to the problem 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
              nstbot NST Bot
              OVN QE OVN QE
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: