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

LSO - Option to wipe local volumes

    XMLWordPrintable

Details

    • LSO - Option to wipe local disks
    • 2
    • False
    • None
    • False
    • Green
    • To Do
    • OCPSTRAT-871 - LSO - Option to wipe local volumes
    • OCPSTRAT-871LSO - Option to wipe local volumes
    • 100
    • 100% 100%
    • XS

    Description

      Epic Goal*

      Add an option to wipe volumes before LSO consumes it. In case the volume already contains data, LSO cannot use it. This is an opt-in option, users need to explicitly ask for it.

       
      Why is this important? (mandatory)

      Request from ODF and SNO team to allow LSO to consume local volumes without the need to clean them manually beforehand.

       
      Scenarios (mandatory) 

      Users can explicitly ask LSO to wipe the disks that are part of a LocalVolume by adding a CRD force wipe field.

      It does not apply to LocalVolumeSet (LVS), LVS could accidentally match an important volume (such as BIOS or UEFI partition) and wipe it.

       
      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" 

      Attachments

        Issue Links

          Activity

            People

              rh-ee-mpatlaso Maxim Patlasov
              rh-gs-gcharot Gregory Charot
              Chao Yang Chao Yang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2 weeks
                  2w
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 weeks
                  2w