ZFS management support

Feature Request

zfs support

Environment

I'm working on an atomic installation that runs off USB and provisions all disk on hardware under storage pools which are then partitioned out (some of you might be familiar with a solaris variant that did this called smartos). I'd really like to do this with ZFS as it's (as far as hardware goes) the most reliable with "surprising" configurations; raidz just kind of handles what you throw at it and can trivially suss out and bubble hardware errors, something I need to do as the machines will need to self-heal.

Desired Feature

Support for creating a zfs tank from device lists or globs. Support for configuring mountpoints (and optionally volumes) off the tank and configuring their parameters.

Other Information

Been writing golang for a long time and I'm happy to write this patch, but looking at your code I don't know exactly how to go about it. I see everything is broken into stages, not all of them are going to be necessary with a ZFS installation (e.g., created filesystems are automatically mounted unless told otherwise) or a ZFS layer might need additional massage to support it. A guide on what to do here to get my patch accepted would be extremely welcome.

And of course this begets the requirement for kernel modules; my thought on this is if you want zfs, you know that you need kernel modules. Would like to hear opinions on how to solve this best.

Start by reading Ignition's staged architecture and existing storage stages to understand where filesystem provisioning belongs. Define how ZFS device lists or globs, pools, mountpoints, volumes, parameters, and kernel-module requirements fit the configuration model. Done means the design is agreed and ZFS provisioning behavior is covered, including stages that are unnecessary for ZFS installations.