Thank you Gianluca, for supporting my claim: it's patchwork and not "a solution designed for the entire enterprise". Instead it's more of "a set of assets where two major combinations from a myriad of potential permutations have received a bit of testing and might be useful somewhere in your enterprise". As such, I see very little future for oVirt as anything that doesn't achieve scale these days is doomed to die. I gather IBM is betting on RH in the cloud, but oVirt isn't designed for that (and suffers a license overhead for little if any extra value over the cloud native stack) and HCI doesn't make sense in any existing cloud: its mission is more like bootstrapping your own. Once you achieve any scale, storage will move to specialized appliances. I can see oVirt and especially the HCI variant on the potentially many stopovers from the edge to the cloud core and even in special data center holdouts. There the ability to really deliver the best fault resilient 1-9 node scalability (somewhat bigger shouldn't be a problem anyway) with the ability to carefully tune and mingle between resilience and storage efficiency is key. You don't want to redeploy oVirt in a 100 embedded locations across a bigger geography, just because you've outgrown 3 nodes. I could see oVirt run on ships, (including space ships), in factories, in the military, train networks, schools or just about any place that need to combine some local presence with resilience, flexibility and remote management (but low dependence). But you'd have to go at it strategically and with a truly unified approach between the Gluster and oVirt teams. The management engine, KVM, VDO and Gluster are each brilliant pieces of engineering, the combination of which could be a force to reckon with, everywhere outside the cloud. But not with the current approach, where each component is allowed to trudge along at its own pace, hopefully not breaking as each is evolving independently. And of course, the final product must be available free of charge so money doesn't get in the way of scale. When a nation adopts oVirt to digitalize its school, or its rail systems, or an industry giant to runs its factories, revenue should not be an issue. And at the low-end you really want to beat QNAP with a 3 node HCI at a similar cost and energy footprint e.g. using RASPI modules (or just three last generation smartphones for that matter). That's how you'd get the scale. I hope you'll find something valuable in all this rant! And sorry for the bother.