Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-6075

Add global MicroShift configuration to releases testing scenarios

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • QE
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • 3
    • None
    • None
    • uShift Sprint 277, uShift Sprint 278, uShift Sprint 279

      In QE Jenkins release testing, we use to run standard RF test suites with these configurations applied. Sometimes we set a few of them at the same time. These are very useful tests to validate these configurations don't interfere with each other.

      • FIPS: enabled and disabled
      • IP version: ipv4, ipv6, ipv6dualstack
      • low-latency: enabled and disabled
      • TLS protocol: v1.2 and v1.3
      • LVMS: enabled and disabled

      Analysis what scenarios need to added or modified to make this possible.

          1.
          		 Enable and disable lvms Sub-task Code Review Undefined Rama Kasturi Narra
          2.
          		 Add an scenario to enable all (or most) configs at the same time (ipv6 + FIPS + low-latency + TLSv1.3...) and validate there's no conflict Sub-task Code Review Undefined Rama Kasturi Narra

              knarra@redhat.com Rama Kasturi Narra
              agullon Alejandro Gullón
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: