Thank you Gianluca for your honest assessment.
Now if only you'd put that on the home page of oVirt, or better yet, used the
opportunity to change things.
Yes, after what I know today, I should not have started with oVirt on Gluster, but
unfortunately HCI is exactly the most attractive grassroots use case and the biggest
growth opportunity for oVirt.
AFAIK there is no competition out there. If there was, I probably would have jumped ship
already, as attached (habit dependent) as I am to CentOS.
In theory oVirt could start with single node HCI, and then go to 3nHCI to gain resilience.
That step is already crucial (ideally witha 2nHCI base on a warm storage standby) and
currently easy with Gluster, but "not supported" (with no warning or explanation
that I could remember) by oVirt. Whatever the reason, it is not at all obvious to the
newcomer, nor should it be unsurmountable to my understanding.
And as things go on and you're expanding some clusters, there is a natural tendency to
go towards dedicated storage say after reaching dual digits on HCI nodes, because it offer
better price/performance and controls. Again, that transition should be
"organic" of not seamless, with migration of VMs and their disks, perhaps not
live, even if gaps there should be closable, too.
Nobody else can do that, not VMware, not Nutanix, nor Proxmox.
And the cloud guys aren't offering anything right there, even if they probably should,
if only to make sure that any such grass-roots projects can be fork lifted easily into
their clouds, once their end product takes off.
IMHO this sort of opportunity needs serious seed money, organic growth from the community
and direct revenues obviously haven't done it yet.
But letting things just go on as they do now, I consider a death knell to oVirt.
Kind regards,
Thomas