Hi José, On 07/17/2012 10:15 AM, jdbjunior@gmail.com wrote:
Thanks for the anwsers. Well, what I want is to get down & dirty into the code. But as I start reading the code, and testing it I can also support the infrastructure if there's anything to do. I can't be all day long involved but for sure I will put some hours everyday on the project. So if you guys think there are some "easier" tasks that I can help at the infrastructure of the project. Please let me know.
I think the first step is to get oVirt up and running. You will need at least one node, at least one storage node (but it can be local storage), and one ovirt-engine. If you have the hardware at home, you can follow along the oVirt "getting started" guide at http://wiki.ovirt.org/wiki/File:OVirt-3.0-Installation_Guide-en-US.pdf The next step would be to get the source code and succeed in building it. The main components of oVirt in terms of source code are the engine web application and the VDSM component which enables remote control and monitoring on the nodes. You can get information about compiling these in the wiki: * http://wiki.ovirt.org/wiki/Building_oVirt_engine * http://wiki.ovirt.org/wiki/Vdsm_Developers Please do stop into the #ovirt IRC channel on OFTC if you have any questions! Thanks, Dave. -- Dave Neary Community Action and Impact Open Source and Standards Team, Red Hat Phone: +33 9 50 71 55 62