Draft, not final. Be careful.
I’m tested this procedure in my test lab with fresh oVirt 3.1 installation with following configuration:
To update ovirt 3.1 to version 3.2 you can follow next procedure:
If possible, backup engine, also you can backup all VM to export domain using oVirt console.
Add info about 3.2 repo to /etc/yum.repos.d/ovirt-dre.repo and
[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
[vdsm31-dre]
name=Vdsm for oVirt 3.1 repo
baseurl=http://www.dreyou.org/ovirt/vdsm31/
http://www1.dreyou.org/ovirt/vdsm31/
enabled=1
gpgcheck=0
[ovirt31-dre]
name=oVirt 3.1 engine repo
baseurl=http://www.dreyou.org/ovirt/ovirt-engine31/
http://www1.dreyou.org/ovirt/ovirt-engine31/
enabled=1
gpgcheck=0
engine-upgrade
yum update ovirt-engine-setup
engine-upgrade
engine-upgrade will stop oVirt engine, then back up database, then update packages and then start oVirt engine again.
Check if engine works correctly, if yes, now you can start to upgrade hosts.
Switch host to “Maintenance” mode.
Add info about 3.2 repo to /etc/yum.repos.d/ovirt-dre.repo
[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
[vdsm32-dre]
name=Vdsm for oVirt 3.1 repo
baseurl=http://www.dreyou.org/ovirt/vdsm31/
http://www1.dreyou.org/ovirt/vdsm31/
enabled=0
gpgcheck=0
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/
yum clean all&&yum makecache
yum update
service vdsmd restart