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

Live-migration with Trunk ports: subports are flapping between hosts (source and destination) during the process

XMLWordPrintable

    • 8
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Given a VM with a trunk port and multiple subports running in a OpenStack environment using OVN for networking,

      When a live migration of the VM is initiated from the source host (compute-0) to the destination host (compute-1),

      Then, the OVN controller should ensure that the parent trunk port and subports are only bound to the destination host after migration, without flapping between source and destination during the process.

      Show
      Given a VM with a trunk port and multiple subports running in a OpenStack environment using OVN for networking, When a live migration of the VM is initiated from the source host (compute-0) to the destination host (compute-1), Then, the OVN controller should ensure that the parent trunk port and subports are only bound to the destination host after migration, without flapping between source and destination during the process.
    • rhel-sst-network-fastdatapath
    • ssg_networking
    • Important

      This bug is related to:

       

      When a VM with a Trunk port is migrated, the parent port is correctly bound to the new chassis. However, the subports are flapping during the process; e.g.: [1] the port is migrated from compute-0 to compute-1. The ovn-controller of each node (compute-0, compute-1) is always trying to claim the port (c34a1f96-d745-4e8c-8687-70d4b18d9f81) once the other node has claimed it.

      Because of that, Neutron is receiving multple port binding chassis updates [2] related to the same port. If by accident the source host makes the last claim of the subport, this port will be assigned to an incorrect host (chassis) and it won't be defined as UP. That will make the live-migration to fail.

      The goal of this bug is, if possible, to implement a mechanism similar to [3]: the LSP is aware of the multiple chassis and only the destination chassis claims it.

       

      [1]https://paste.opendev.org/show/bIWeAAXaXb68ut0R0YoI/

      [2]https://paste.opendev.org/show/bqCx4QxAu82vW9ohJUuq/

      [3]https://bugzilla.redhat.com/show_bug.cgi?id=2012179

       

              mheib@redhat.com Mohammad Heib
              rodolfo_alonso Rodolfo Alonso
              Ehsan Elahi Ehsan Elahi
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: