Thanks Tony. I will take a look. Features (Design documents) | oVirt says "Most of them are outdated, but provide historical design context", but it should help anyway.
On 8/7/2021 16:30，Tony Pearce<tonyppe@gmail.com> wrote：
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.Tony PearceOn Sat, 7 Aug 2021 at 00:50, Jesse Hu <jessehubj@163.com> wrote:Thanks Tony and Thomas. https://www.ovirt.org/documentation/ contains docs for using oVirt, but not docs for developing oVirt.
Somewhat I agree on "I also have not encountered any useful oVirt/RHV architecture books. The
ones I found were very much "do this, do that" and didn't help me as a
technical architect.". oVirt is open sourced under Apache License, but seems like currently it's not open to contributors or 3rd party developers who want to modify and rebuild from the source code？
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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://lists.ovirt.org/archives/list/users@ovirt.org/message/KEXLSWDN4AAD4X3NBNIYFCFRNZKUJHPK/