OVirt

oVirt is a complete open sourced virtualization management platform working with KVM. The project is made of:
 * The Engine core, which is the backend server that does the management.
 * The various VDSM agents installed on each host you 'll use as a hypervisor for VMs
 * A client side UI (GWT based) and/or RESTful API to control the engine core.

PostgreSQL

 * Install PostgreSQL server:


 * Configure PostgreSQL server:


 * Allow network access:


 * Start:

Database

 * Create user and database for engine:


 * OPTIONAL: Create user and database for dwh:


 * OPTIONAL: Create user and database for reports:

Installation

 * Add oVirt overlay to

Portage overlay exists here: http://github.com/alonbl/ovirt-overlay

Using a recent Portage version you can add the overlay creating :

This can be done automatically with :

If you use an older Portage or prefer to use layman to manage your overlays, you can add the oVirt overlay XML file into :

And then add it using:


 * Sync the repository:


 * Install ovirt-engine:

You may need to add unstable keywords to various packages.


 * OPTIONAL: Emerge ovirt-engine-dwh and/or ovirt-engine-reports:


 * Configure ovirt-engine:

Follow instructions.

Apache

 * Enable mod_proxy, add after APACHE2_OPTS="XXX":


 * Restart:

Testing
Login into http://localhost/ovirt-engine

Logs are at

Install vdsm

 * Install dev-python/pyflakes as it is needed by vdsm:


 * Obtain VDSM source RPM:


 * Convert rpm package to tgz:


 * Unpack the archive:


 * Enter the directory and do the configure-make-make install magic (Recommended to use  when compiling from source so you can have all files under one directory per package):

How to contribute

 * oVirt project is working with Gerrit code review for code contribution.
 * In order to register and login to oVirt's Gerrit, you'll need an OpenID account.
 * You can use a Google OpenID, or register to some other provider and use it,
 * All other details can be found here: http://www.ovirt.org/wiki/Working_with_oVirt_Gerrit

oVirt Node integration

 * By default development setup works with hosts based on base distro's installations.
 * In order to be able to work with oVirt Node (which is a sub-set of the base OS), you'll need to setup a Public Key environment.
 * More details on Engine and oVirt Node integration can be found here: http://www.ovirt.org/wiki/Engine_Node_Integration.
 * Note that by default Gentoo does not have folder, and you'll need to create it (or write an ebuild which will do that).

Troubleshooting JBoss (obsolete)
If you're being attacked by exceptions, follow this list:


 * Verify jboss folder owner and permissions.
 * If your machine has an SELinux policy installed, make sure it will not block JBoss. Here is a very dirty and insecure jboss.te just to temporarily pass these denials (you'll also need selinux-java)

127.0.0.1 localhost engine-dev
 * Used TCP ports: 8702/8083/1090/4457
 * Since JBoss binds to the hostname, your hostname should be resolvable, or you may add it to for local resolution.

External resources

 * Additional information (including presentations)
 * Users list: users@ovirt.org