RE documentation
> "do this, do that"
this is generally what I feel when I read most documentation, not just ovirt - I find it frustrating at times because there is little to no context or any "linking" of "why would you want to do X".
In the past I have used approved vendor design documentation guides (from Cisco / in cisco-world). Basically like as-built documentation. I have done a google search for ovirt design docs and it has led me to this place [1]. Maybe this could help you? Seems to be some useful info there.
Although I was reading the openshift on ovirt page [2] and it is incomplete with a message at the top with a link to "the documentation". However when clicking the link it doesn't take you to the documentation for "openshift on ovirt" but instead takes you to [3] and that page does not contain information about openshift.