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

[EVPN] ovn-controller: support dual-stack for ovn-evpn-local-ip

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • OVN
    • None
    • ovn-controller: support dual-stack for ovn-evpn-local-ip
    • False
    • False
    • Hide

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

      ( ) The acceptance criteria defined below are met.

      Given EVPN-enabled logical switches with distinct VNIs,

      When ovn-evpn-local-ip is configured as "$VNI1:$IP1,$VNI2:$IP2",

      Then each VNI's VXLAN tunnel flows use its corresponding local IP as the source address.

      ( ) 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 EVPN-enabled logical switches with distinct VNIs, When ovn-evpn-local-ip is configured as "$VNI1:$IP1,$VNI2:$IP2", Then each VNI's VXLAN tunnel flows use its corresponding local IP as the source address. ( ) 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?

      Currently ovn-controller only supports a single value (IPv4 OR IPv6) for the per-chassis ovn-evpn-local-ip configuration. This value is used as the local-ip for the VXLAN tunnel flows ovn-controller configures for EVPN enabled switches.

      From our ovn-controller man page:

            <dt><code>external_ids:ovn-evpn-local-ip</code></dt>
      <dd>
        IP address used as a source address for the EVPN traffic leaving this
        OVN setup. There is currently support only for single IP address
        being specified. NOTE: this feature is experimental and may be subject
        to removal/change in the future.
      </dd>

      Also in the upstream TODO file:

        * Allow ovn-evpn-local-ip to accept list of
    $VNI1:$LOCAL_IP1,$VNI2:$LOCAL_IP2 combinations which will be properly
    reflected in physical flows for given LS with VNI.

       

      Why is it needed?

      Dual-stack deployments (IPv4 + IPv6) are a common thing. It's necessary to support dual-stack before we can promote the EVPN OVN support to "fully supported" from "experimental".
       

      Who will benefit? 

      All potential users of the OVN EVPN native support (e.g., ovn-kubernetes or neutron).

              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: