Epic Goal*

The goal of this epic is to improve, reduce and simplify the cleanup steps of the LSO deployment (LogicalVolume/LogicalVolumesets).

 
Why is this important? (mandatory)

Currently cleaning up LSO LogicalVolume/LogicalVolumesets require lot of manual, error-prone steps which badly degrate overall user experience. Support cases are raised by customers and Red Hat support team is also impacted.

 
Scenarios (mandatory) 

Deploy LSO, create LogicalVolume/LogicalVolumesets then clean up everything successfully.

 
Dependencies (internal and external) (mandatory)

None. Will benefit ODF when deployed on top of LSO.

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 - STOR
• Documentation - STOR
• QE - STOR
• PX - 
• Others -

Acceptance Criteria (optional)

The number of steps to clean up an LSO deployment should be reduced with automation.

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"