Dear Nir
I want to make a VDI solution using Ovirt.
But, to sell it in Korea, we need to pass through the Korean Common Criteria(CC) for security reason.
Moreover, if our customers complain about any errors because of Ovirt itself,
we have to fix it in code level of Ovirt.
Even, we need to add more customized features to Ovirt to make more competitive VDI solution.
To cover the above issues, our developers should know the internal structure of Ovirt,
and could change, verify, or add some codes to the source code of Ovirt.
For the start, UML could be the first step for analyzing Ovirt by our developers.
Can you help me if you have other suggestions to start analyzing the source code of Ovirt in detail??
Hope for your reply.
Sincerely yours.
Hyunsoo Lee