I'm glad you made it work!
My main lesson from oVirt from the last two years is: It's not a turnkey solution.
Unless you are willing to dive deep and understand how it works (not so easy, because
there is few up-to-date materials to explain the concepts) *AND* spend a significant
amount of time to run it through its paces, you may not survive the first thing that goes
wrong.
And if you do, that may be even worse: Trying to fix a busy production farm that has a
core problem is stuff for nightmares.
So make sure you have a test environment or two to try things.
And it doesn't have to be physical, especially for the more complex things, that
require a lot of restart-from-scratch before you do the thing that breaks things.
You can run oVirt on oVirt or any other hypervisor that supports nested virtualization and
play with that before you deal with a "real patient".
I've gone through through catastrophic hardware failures, which would have resulted in
in a total loss without the resilience oVirt HCI with Gluster replicas provided, but
I've also lost a lot of hair and nails just running it.