Goal

• User should be able to remove device class from the cluster. Currently, this is a cumbersome procedure requiring the complete removal of the LVMCLuster

Why is this important?

• It will be easier for customers to manage their clusters with multiple device classes rather than deleting whole LVMS cluster. This feature will solve this problem

Scenarios

1. As a cluster administrator, i want to delete device class from LVMS cluster
   1. cluster administrator needs to check that devices from device class does not contain any data on it
      1. if any disk contains lvm data on it, cluster administrator need to move this data manually by using `pvmove` command
   2. once all disks are empty, cluster administrator can delete device class from LVMS CR
   3. LVMS will detect the change, check if disks are actually empty and remove device class and lvm volume group

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement

Done Checklist

• CI -  CI is running, tests are automated and merged.

• Release Technical Enablement <link to Feature Enablement Presentation>

• DEV- Upstream code and tests merged: <link to meaningful PR or GitHub Issue>

• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>

• DEV - Downstream build attached to advisory: <link to errata>

• QE - Test plans in Polarion: <link or reference to Polarion>

• QE - Automated tests merged: <link or reference to automated tests>

• DOC - Downstream documentation merged: <link to meaningful PR>