-
Notifications
You must be signed in to change notification settings - Fork 170
Closed as not planned
Description
I’m running a heterogeneous on-premise cluster with NVMe disks:
- Some nodes have 1 NVMe disk
- Some nodes have 2 NVMe disk
- Some nodes have 3 NVMe disks
For reliability reasons, I don’t want to create a single VG spanning multiple disks (since one disk failure would cause data loss).
Instead, I create multiple VGs per node, for example:
nvme1nvme2nvme3
From a user perspective, it would be much nicer if workloads could just use a single StorageClass like lvm-nvme, instead of having to know about and choose between lvm-nvme1, lvm-nvme2, lvm-nvme3.
Feature request
- Allow a StorageClass to reference multiple VGs on a node.
- TopoLVM would then provision volumes from any available VG within that group.
Benefits:
- Simplifies UX (users don’t need to know disk/VG details).
- Works well with heterogeneous nodes (different number of disks).
Is there maybe a way to achieve this today with existing features?
Thanks!