Stratis storage pool #6519
Labels
C: storage
P: minor
Priority: minor. The lowest priority, below "default."
R: declined
Resolution: While a legitimate bug or proposal, it has been decided that no action will be taken.
T: enhancement
Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
The problem you're addressing (if any)
QubesOS heavily relies on fast snapshots, which LVM is not designed for. Furthermore, LVM only offers a command-line interface and an interactive shell. The D-Bus API is incomplete, and the C and Python APIs are deprecated.
Describe the solution you'd like
Like LVM thin provisioning, Stratis uses
dm-thin
internally. However, Stratis is a persistent daemon with a D-Bus API, and so (hopefully) can perform snapshots much faster. Additionally, Stratis intends to offer integrity support, and may do so already.Where is the value to a user, and who might that user be?
Users who need high I/O throughput will be able to obtain faster qube starts. Furthermore, integrity support is a necessary first step towards untrusted storage domains.
Describe alternatives you've considered
We could keep the existing LVM2 pool, or switch to BTRFS.
Additional context
This is not intended as a replacement for the BTRFS pool, but rather as an improved version of the LVM2 pool. Stratis is Red Hat’s next generation storage offering and so should be highly stable and reliable, provided that it is not misused. BTRFS is more robust to space exhaustion and other errors, at (potentially) a cost in throughput.
Relevant documentation you've consulted
Related, non-duplicate issues
#6476
The text was updated successfully, but these errors were encountered: