Uploaded image for project: 'OpenShift Edge Enablement'
  1. OpenShift Edge Enablement
  2. OCPEDGE-42

Expand kernel-rt testing to include latency tests

XMLWordPrintable

    • Expand kernel-rt testing to include latency tests
    • Product / Portfolio Work
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • Hide

      2023-08-25

      Dev: Waiting on a PR that adds rteval to the test image to implement the rteval test

      QE: N/A

      Docs: N/A

      Show
      2023-08-25 :  Dev: Waiting on a PR that adds rteval to the test image to implement the rteval test QE: N/A Docs: N/A
    • L

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Create a new informing lane in CI which includes the functional tests from OCPVE-163 and the latency tests from the RHEL Shift Left initiative started by the Telco RAN team.
      • Enable the informing lane to run on bare metal on a consistent set of hardware.

      Why is this important?

      • We document that running workloads on OpenShift with a realtime kernel works but testing, in practice, is often done in a bespoke fashion in teams outside of OpenShift. This epic seeks to close the gap of automated integration testing OpenShift running a realtime kernel on real metal hardware.

      Scenarios

      1. https://docs.google.com/presentation/d/1NW8vEkP7zMd0vxWpD-p82srZljcAOtqLEhymuYcUQXQ/edit#slide=id.g1407d815407_0_5

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. OCPVE-163
      2. https://github.com/openshift/enhancements/blob/master/enhancements/support-for-realtime-kernel.md

      Open questions:

      1. What is the cost/licensing requirements for metal hardware (Equinix?) to support this new lane?
        1. How many jobs do we run and for how often?
      2. How do we integrate the metal hardware with Prow?
      3. Who should own this lane long term?
      4. Does OpenShift make any performance guarantees/promises?

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              rh-ee-jeroche Jeff Roche
              rhn-support-cscribne Chad Scribner
              Egli Hila
              Jeff Roche Jeff Roche
              Unassigned Unassigned
              Unassigned Unassigned
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: