Also I feel like the most popular instructions were a blog post, rather than official documentation.
I'm not even sure they have a dedicated techwriter. This is why it is better to just follow the official RHV docs. You'll have to filter out the Red Hat specific details, like subscription-manager, but you'll definitely have a better experience
Technically S2D is designed to be used by DAS systems (or JBODs if you like to make Scott facepalm), and not internal server storage... even though it works just fine.
There's no problem to use RAID controller instead of a basic HBA as long as you a) patch the registry (see my link below) or use special "filter" driver to report "RAID" bus (sic!) as SATA or SAS, and b) disable write-back cache on BOTH controller and disk itself, so all writes become atomic.
P.S. It's a BAD idea to use anything like that in production because as long as Microsoft support will discover your S2D configuration isn't supported they will pull out and walk away with a grin face.
I just face palmed reading that first paragraph: New features
LVM RAID support
One of the biggest features of blivet-gui 2.0 is support of LVM RAID. When adding a new LV, you can now choose RAID level for it. LVM supports the same RAID types mdraid does but you can choose different level for every logical volume so it's more flexible than using LVM on top of an mdraid.
LVM still uses md raid, just like you would normally.
That said, people like their gui for all the things, why not have yet another tool to manage everything.
The IPMI from SuperMicro has a web interface where you can do user maintenance for ipmi, remote control of hosts, record video(for recording other people's access to this system i guess), from there you can set Serial over Lan options. Here is the base screenshot
It does use java for some things still. There are also functions here i have no clue what they are. No idea what RAKP Protocol Setting is, but it is there.
Here is a nice feature, it shows how much power your host is using. It changes every few seconds.
It was amazing that Scott found it so fast. I was on the Windows side of things. Inside Windows they were using the iSCSI initiator to connect to the FreeNAS. All the sudden Windows would just log a ton of iSCSI events and go down.
I looked up the events and most people resolved them by putting the iSCSI traffic on a separate NIC. This happened two days in a row at about the same time each day. I was looking at snapshot, backup, etc times when Scott found it in the FreeNAS logs.