Epic Goal

• Fully support multiple storage classes on a single LVMS deployment. On a node with multiple disks (e.g. NVMe, SSD, HDD), customer want to be able to utilize/create different storage classes so that workload can be deployed to use the disk type it needs

Why is this important?

• Customer runs workloads (on single node OCP), which have different storage performance requirements. Customer SNO HW has 3 dwpd disks for heavy ready/write operations for read/write intensive apps and 1 dwpd disks or spinning disks as cost efficient for large data sets (only write intensive).

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Documentation with example on how to configure this available

Dependencies (internal and external)

none

Open questions::

1.  This is probably already possible today by creating multiple operands for the lvmo operator. I probably only needs CI/QE and Docs.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release 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>