-
Epic
-
Resolution: Done-Errata
-
Major
-
openshift-4.13, openshift-4.14
-
TopoLVM Design: Support PVCs in smaller Increments than 1Gi
-
Future Sustainability
-
-
0% To Do, 0% In Progress, 100% Done
-
False
-
-
False
-
Green
-
-
XL
-
None
Epic Goal
Currenlty, LVMS has a min PVC size of 1GiB. This should be changed to support sizes of 1 MiB via Design Proposal.
This Epic should achieve an accepted design that can be implemented in a separate Epic due to the scope size.
Why is this important?
On a small edge device with limited storage (e.g. only 32GB sd card) in combination with lots of small PVCs, this could lead to a situation where a solution can not be deployed.
Thin provisioning does not really help, because just "by the book", the disk would be full.
Acceptance Criteria
- Release Technical Enablement - Provide necessary release enablement details and documents.
- Be able to create and bind a PVC with 10 MiB size if proposal is implemented.
- Acceptance from TopoLVM and Proposal being merged into upstream
Dependencies (internal and external)
- LVM does support LV with MB sizes.
- The issue seems to be the lvmd rest API, which requires Size in GB as INT, causing the size. See here where the rounding up happens.
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement Feature Presented in OCPVE Sprint Call
- DEV - Upstream code and tests merged: https://github.com/topolvm/topolvm/pull/766
- DEV - Upstream documentation merged: N/A no visible change to customer
- 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: N/A no visible change to customer
- is related to
-
OCPBUGS-6251 not possible to create a PV that is smaller than 1GB
-
- Closed
-
- relates to
-
OCPSTRAT-726 LVMS TopoLVM Replacement - Dev Preview MVP
-
- Closed
-
- links to
-
RHBA-2024:126443 LVMS 4.15 Bug Fix and Enhancement update