XMLWordPrintable

    • Integrate CDI into CRIO
    • False
    • False
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined

      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

      • Integrate CDI into CRIO 

      Why is this important?

      • New interface for enabling "any" accelerator on "any" runtime, deprecating prestart hooks

      Scenarios

      1. GPUs, FPGAs, ... etc.

      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. https://github.com/container-orchestrated-devices/container-device-interface

      Previous Work (Optional):

      Open questions::

      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>

              sejug2 Sebastian Jug
              gausingh@redhat.com Gaurav Singh
              Walid Abouhamad Walid Abouhamad
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: