Version 3.2.2 - Stable builds
oVirt 3.2.1 to 3.2.2 update procedure
oVirt 3.2 to 3.2.1 update procedure
oVirt 3.1 to 3.2.1 update procedure
sudo wget http://www.dreyou.org/ovirt/ovirt-dre.repo -P /etc/yum.repos.d/
Chek if ovirt32-dre, vdsm32-dre repositories enabled by default in /etc/yum.repos.d/ovirt-dre.repo (enable=1), i.e. :
[vdsm32-dre]
name=Vdsm for oVirt 3.2 repo
baseurl=http://www.dreyou.org/ovirt/vdsm32/
http://www1.dreyou.org/ovirt/vdsm32/
enabled=1
gpgcheck=0
[ovirt32-dre]
name=oVirt 3.2 engine repo
baseurl=http://www.dreyou.org/ovirt/ovirt-engine32/
http://www1.dreyou.org/ovirt/ovirt-engine32/
enabled=1
gpgcheck=0
Then:
yum clean all
yum makecache
Direct links to repositories:
Add epel repositories for mom and for python-pthreading packages (http://fedoraproject.org/wiki/EPEL/FAQ).
yum clean all
yum makecache
If you plan to use gluster volumes, add gluster 3.4-alpha repositories (needed by vdsm-gluster)
sudo wget http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.4.0alpha2/CentOS/glusterfs-alpha-epel.repo -P /etc/yum.repos.d/
Check that the engine FQDN is resolvable from the node (For example, edit /etc/hosts).
Check that the CentOS version is 6.4, make update if needed.
Now you must have java 1.7 to install and use oVirt.
yum install java-1.7.0-openjdk
Add epel repositories for python-ply, python-kitchen needed by ovirt-engine-cli (http://fedoraproject.org/wiki/EPEL/FAQ).
yum install ovirt-engine
engine-setup
Now you can enter to engine console and add you nodes to cluster.
Install history database
yum install ovirt-engine-dwh
Configure ovirt-engine-dwh
ovirt-engine-dwh-setup
Install reports
yum install ovirt-engine-reports
Configure reports
ovirt-engine-reports-setup
If you have some problems while installing engine or running Vms look here.