Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

This features aims to improve, reduce and simplify the cleanup steps of the LSO deployment (LogicalVolume/LogicalVolumesets) after the operator is removed.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

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.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

Streamline the deletion of artefacts after LSO has been deleted. The deployment should be clean of any LSO artefacts.

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

As an OCP admin, I want to remove LSO operator and the associated resources.

As an OCP admin, I am running a CI that deploys and remove OCP/LSO, I need a simple and efficient way to clean up and redeploy without manual steps.

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

ODF removal

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Cleaning LSO artefacts introduces operational frictions with customers when removing LSO which redirects the task to Red Hat support. Adding a clean up step upon LSO deletion will improve customer user experience, decrease potential operational mistakes as well as reducing support involvement.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

This should not be enabled by default to preserve customer's data. This feature should be opt in.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

Add clean up procedure to the OCP storage LSO guide. Add limitations if any.

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

Limited to LSO deployments which is usually limited in used on public cloud.