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

Review Cinder CSI operator merge into csi-operator repo

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Review Cinder CSI operator merge into csi-operator repo
    • BU Product Work
    • 1
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-1518 - TechDebt - Merge CSI driver operators into common csi-operator repo (Internal / Not customer facing)
    • OCPSTRAT-1518TechDebt - Merge CSI driver operators into common csi-operator repo (Internal / Not customer facing)
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal*

      The OS as Infra team is working on HCP for OSP and requires to Merge OpenStack Cinder CSI driver operator into csi-operator repo.

      As this is a delicate work, the OCP storage team needs to allocate some time to review the PRs before merging them.

       
      Why is this important? (mandatory)

      • Ability to run cinder and manila operators as controller Pods in a hosted control plane
      • Ability to run Node DaemonSet in a guest clusters

       
      Scenarios (mandatory) 

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

      1.  

       
      Dependencies (internal and external) (mandatory)

      What items must be delivered by other teams/groups to enable delivery of this epic. 

      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” 

            hekumar@redhat.com Hemant Kumar
            rh-gs-gcharot Gregory Charot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: