User Tools

Site Tools


ovirt_rpm_update31to32

<note warning>

Draft, not final. Be careful.

</note>

<note>

I'm tested this procedure in my test lab with fresh oVirt 3.1 installation with following configuration:

</note>

oVirt 3.1 to 3.2 Update Procedure

To update ovirt 3.1 to version 3.2 you can follow next procedure:

1. If possible, backup engine, also you can backup all VM to export domain using oVirt console.

2. 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

3. Check if 31 repo also ENABLED in /etc/yum.repos.d/ovirt-dre.repo

[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

2. On oVirt engine node execute engine-upgrade

engine-upgrade

3. If engine-upgrade found new version of ovirt-engine-setup you will be prompted to update this package, do it, then run engine-upgrade again:

yum update ovirt-engine-setup

engine-upgrade

4. engine-upgrade will stop oVirt engine, then back up database, then update packages and then start oVirt engine again.

5. Check if engine works correctly, if yes, now you can start to upgrade hosts.

6. Switch host to “Maintenance” mode.

7. 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

8. Disable 3.1 repo in /etc/yum.repos.d/ovirt-dre.repo

[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

9. Add epel repositories for mom and for python-pthreading packages (http://fedoraproject.org/wiki/EPEL/FAQ).

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/

10. Update vdsm packages.

yum clean all&&yum makecache
yum update

11. Restart vdsmd and activate host.

service vdsmd restart
ovirt_rpm_update31to32.txt · Last modified: 2013/04/04 13:52 by dreyou