Uploaded image for project: 'OpenShift Storage'
  1. OpenShift Storage
  2. STOR-2297

TechDebt: Remove oVirt CSi driver + operator

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • TechDebt: Remove oVirt CSi driver + operator
    • False
    • None
    • False
    • Not Selected
    • To Do

      Epic Goal*

      Remove oVirt CSi driver + operator from OpenShift's payload. Stop building it, stop shipping it.

       
      Why is this important? (mandatory)

      We still ship oVirt CSI driver + operator, despite oVirt (RHEV) support was removed from OCP 4.14 (!!!). We do not maintain the code any longer, is probably full of CVEs.

      Scenarios (mandatory) 

      Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

      1. As OCP developer, I can see oVirt CSI driver and operator are not built nor shipped as part of OCP payload (`oc adm release info | grep ovirt`).

       
      Dependencies (internal and external) (mandatory)

      None

      Contributing Teams(and contacts) (mandatory) 

      Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

      • Development - 
      • Documentation -
      • QE - 
      • PX - 
      • Others -

      Acceptance Criteria (optional)

      Provide some (testable) examples of how we will know if we have achieved the epic goal.  

      Drawbacks or Risk (optional)

      Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

      Done - Checklist (mandatory)

      The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

      • CI Testing -  Basic e2e automationTests are merged and completing successfully
      • Documentation - Content development is complete.
      • QE - Test scenarios are written and executed successfully.
      • Technical Enablement - Slides are complete (if requested by PLM)
      • Engineering Stories Merged
      • All associated work items with the Epic are closed
      • Epic status should be “Release Pending” 

              Unassigned Unassigned
              rhn-engineering-jsafrane Jan Safranek
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: