The general idea was, that with oVirt I'd get a little more automation and benefits than with just using VirtualBox as a GUI for KVMs.
Boy did I underestimate the amount of intellectual investment for the first value return. Turned out quite a bit bigger than vSphere, but much more intriguing, because after all: The code was all there! I got hooked... beyond reasonble, perhaps. With Openstack they jury has come back a long time ago: Unless you're willing to sacrifice a double digit team for a year or three, don't go near it. Three node HCI oVirt just looked like a tight little project with plenty of expandability... sigh! _______________________________________________ Users mailing list -- email@example.com To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://firstname.lastname@example.org/message/VTLWH3UKDDOBHXHAQPN5UADWTPZ2KYED/