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

Test Plan: [ovn-ic] Synchronize Transit router between AZs

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • OVN
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      ( ) The new test plan is aligned with the epic's acceptance criteria

      Given a Transit Router and associated ports in ovn-ic-nb, 

      When the sync process runs, 

      Then each AZ’s ovn-nb must reflect the router and ports with tunnel keys and visibility flags set correctly.

      ( ) The test plan/test case pass successfully on all non blocking functions of the feature

      Show
      ( ) The new test plan is aligned with the epic's acceptance criteria Given a Transit Router and associated ports in ovn-ic-nb,  When the sync process runs,  Then each AZ’s ovn-nb must reflect the router and ports with tunnel keys and visibility flags set correctly. ( ) The test plan/test case pass successfully on all non blocking functions of the feature
    • rhel-10
    • None

      This task is tracking the test case writing activities to cover the feature request described below.

      Synchronize the Transit router entries in ovn-ic-nb to all ovn-nb databases in all NBs. That also includes the connected ports. For ports there needs to be a way to distinguish between ports that are local to all AZs (there might be connection to TS for example). Another important part is to properly synchronize tunnel keys for the Transit router itself but also for all the ports.

              ovnteam@redhat.com OVN Team
              nstbot NST Bot
              OVN QE OVN QE
              OVN
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: