-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Problem Statement
The current MachineClass definition in Omni appears to support only a single storage device per machine. This presents a limitation when deploying advanced storage solutions like Piraeus/LINSTOR, which require dedicated, unformatted block devices on each node to create storage pools.
Without the ability to provision multiple disks for a machine, it's not possible to properly configure and utilize such Container Storage Interface (CSI) drivers for creating replicated, high-availability persistent storage.
Use Case
I am attempting to deploy the Piraeus/LINSTOR storage solution on a Talos cluster managed by Omni. The standard deployment pattern for Piraeus involves:
- Using the primary disk for the Talos operating system.
- Attaching one or more additional, separate disks to each worker node.
- Configuring LINSTOR to use these additional disks to create a distributed storage pool for providing PersistentVolumes.
Request
Could you please advise on one of the following:
- Is there an existing, undocumented method or a recommended workaround to attach and expose additional block devices to a machine?
- If not, could this feature be considered for a future release?
This enhancement would significantly improve Omni's capabilities for supporting stateful workloads with robust, modern storage solutions.
Thank you