We're about to gain support for many types of complex storage for the root filesystem, but this is distinct from the "root disk" which includes /boot and the ESP for example.
We had a subthread around this starting around here: #94 (comment)
Basically my proposal is that we support "equivalent RAID 1" by teaching coreos-installer how to replicate the /boot partition and ESP to multiple block devices. Making the root filesystem RAID is an orthogonal thing - for example, one might choose to use a higher RAID level for the OS and data, or one could use Stratis/btrfs/LVM for /. Another important variation here is to use LUKS-on-RAID (or equivalent) for the root device. To restate, the root filesystem can be distinct from how /boot and the ESP works.
I think it would work in this scenario to make /boot be MD-RAID - the bootloaders support that and it would mean having ostree update kernels would be fully transparent.
We can't make the ESP be RAID - that would need to be manually sync'd.
We're about to gain support for many types of complex storage for the root filesystem, but this is distinct from the "root disk" which includes
/bootand the ESP for example.We had a subthread around this starting around here: #94 (comment)
Basically my proposal is that we support "equivalent RAID 1" by teaching
coreos-installerhow to replicate the/bootpartition and ESP to multiple block devices. Making the root filesystem RAID is an orthogonal thing - for example, one might choose to use a higher RAID level for the OS and data, or one could use Stratis/btrfs/LVM for/. Another important variation here is to use LUKS-on-RAID (or equivalent) for the root device. To restate, the root filesystem can be distinct from how/bootand the ESP works.I think it would work in this scenario to make
/bootbe MD-RAID - the bootloaders support that and it would mean having ostree update kernels would be fully transparent.We can't make the ESP be RAID - that would need to be manually sync'd.