I can hear you saying: "You did understand that single node HCI is just a toy,
right?"
For me the primary use of a single node HCI is adding some disaster resilience in small
server edge type scenarios, where a three node HCI provides the fault tolerance: 3+1 with
a bit of distance, warm or even cold stand-by, potentially manual switch and reduced
workload in case disaster strikes.
Of course, another 3nHCI would be better, but who gets that type of budget, right?
What I am trying say: If you want oVirt to gain market share, try to give HCI more love.
And while you're at it, try to make expanding from 1nHCI to 3nHCI (and higher counts)
a standard operational procedure to allow expanding a disaster stand-by into a production
setup, while the original 3nHCI is being rebuilt.
For me low-budget HCI is where oVirt has its biggest competitive advantage against vSan
and Nutanix, so please don't treat the HCI/gluster variant like an unwanted child any
more.
In the mean-time OVA imports (from 4.3.10 exports) on my 4.4.2 1nHCI fail again, which
I'll report separately.