Re: [ovirt-users] Upgrade path from running 3.6 (centos 7) to 4.1
On Thu, Mar 2, 2017 at 10:16 AM Peter Hudec wrote: > A Few weeks ago I did upgrade from 3.5 to 4.1 > The release-by-release (3.5 -> 3.6 -> 4.0 -> 4.1)upgrade we found out as > very time consuming, since we were running CentOS 6 on all HOST and > Engine too. We decided to install new 4.1 and migrate the VM. > Agree, it takes time - but there is the InCluster migration policy which allows mixing (in a single direction - EL6 -> EL7) hosts, especially to prevent downtime. > > The only disadvantage of this upgrade is the VM downtime during the > migration. You need to export and import them again. > What about detach and attach the storage domain? Wasn't that a viable option? Or did you prefer export-import one (or several) VMs at a time? Y. > > Peter > > > On 02/03/2017 08:09, Lionel Caignec wrote: > > Ok thank you, > > > > Ok another question, i need to ugprade engine to 4.0 first and then to > 4.1, do i need to do the same for the hypervisor or can i directly go to > 4.1? > > > > - Mail original - > > De: "Yedidyah Bar David" > > À: "Lionel Caignec" > > Cc: "users" > > Envoyé: Jeudi 2 Mars 2017 07:59:56 > > Objet: Re: [ovirt-users] Upgrade path from running 3.6 (centos 7) to 4.1 > > > > On Thu, Mar 2, 2017 at 7:07 AM, Lionel Caignec wrote: > >> Hi, > >> i'm running an ovirt cluster in 3.6 (centos 7) no hosted engine. > >> Is it possible to upgrade directly from 3.6 to 4.1? Or this is not > recommended. > > > > It's not possible. You need to go through 4.0. > > > > Best, > > > >> > >> > >> Thanks, > >> Lionel > >> ___ > >> Users mailing list > >> Users@ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > -- > *Peter Hudec* > Infraštruktúrny architekt > phu...@cnc.sk <mailto:phu...@cnc.sk> > > *CNC, a.s.* > Borská 6, 841 04 Bratislava > Recepcia: +421 2 35 000 100 > > Mobil:+421 905 997 203 <+421%20905%20997%20203> > *www.cnc.sk* <http:///www.cnc.sk> > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path from running 3.6 (centos 7) to 4.1
A Few weeks ago I did upgrade from 3.5 to 4.1 The release-by-release (3.5 -> 3.6 -> 4.0 -> 4.1)upgrade we found out as very time consuming, since we were running CentOS 6 on all HOST and Engine too. We decided to install new 4.1 and migrate the VM. The only disadvantage of this upgrade is the VM downtime during the migration. You need to export and import them again. Peter On 02/03/2017 08:09, Lionel Caignec wrote: > Ok thank you, > > Ok another question, i need to ugprade engine to 4.0 first and then to 4.1, > do i need to do the same for the hypervisor or can i directly go to 4.1? > > - Mail original - > De: "Yedidyah Bar David" > À: "Lionel Caignec" > Cc: "users" > Envoyé: Jeudi 2 Mars 2017 07:59:56 > Objet: Re: [ovirt-users] Upgrade path from running 3.6 (centos 7) to 4.1 > > On Thu, Mar 2, 2017 at 7:07 AM, Lionel Caignec wrote: >> Hi, >> i'm running an ovirt cluster in 3.6 (centos 7) no hosted engine. >> Is it possible to upgrade directly from 3.6 to 4.1? Or this is not >> recommended. > > It's not possible. You need to go through 4.0. > > Best, > >> >> >> Thanks, >> Lionel >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > > > -- *Peter Hudec* Infraštruktúrny architekt phu...@cnc.sk <mailto:phu...@cnc.sk> *CNC, a.s.* Borská 6, 841 04 Bratislava Recepcia: +421 2 35 000 100 Mobil:+421 905 997 203 *www.cnc.sk* <http:///www.cnc.sk> ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path from running 3.6 (centos 7) to 4.1
Ok thank you, Ok another question, i need to ugprade engine to 4.0 first and then to 4.1, do i need to do the same for the hypervisor or can i directly go to 4.1? - Mail original - De: "Yedidyah Bar David" À: "Lionel Caignec" Cc: "users" Envoyé: Jeudi 2 Mars 2017 07:59:56 Objet: Re: [ovirt-users] Upgrade path from running 3.6 (centos 7) to 4.1 On Thu, Mar 2, 2017 at 7:07 AM, Lionel Caignec wrote: > Hi, > i'm running an ovirt cluster in 3.6 (centos 7) no hosted engine. > Is it possible to upgrade directly from 3.6 to 4.1? Or this is not > recommended. It's not possible. You need to go through 4.0. Best, > > > Thanks, > Lionel > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path from running 3.6 (centos 7) to 4.1
On Thu, Mar 2, 2017 at 7:07 AM, Lionel Caignec wrote: > Hi, > i'm running an ovirt cluster in 3.6 (centos 7) no hosted engine. > Is it possible to upgrade directly from 3.6 to 4.1? Or this is not > recommended. It's not possible. You need to go through 4.0. Best, > > > Thanks, > Lionel > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Upgrade path from running 3.6 (centos 7) to 4.1
Hi, i'm running an ovirt cluster in 3.6 (centos 7) no hosted engine. Is it possible to upgrade directly from 3.6 to 4.1? Or this is not recommended. Thanks, Lionel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path/possibility from 3.3?
You need a step update from one major to another. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: yd...@redhat.com IRC : ydary On Mon, Apr 11, 2016 at 7:27 PM, William Kwan wrote: > Hi all, > > I have a couple of oVirt cluster running 3.3.3-2.el6. I would like to > upgrade them to the latest version. I sort of remember upgrading from 3.3 > to 3.5 required an step to upgrade to 3.4 as an extra step. With the new > 3.6, will it be fine to upgrade straight from 3.3.3 to 3.6? or I need some > extra steps? > > Another question is about preservation of the virtual machines. Can I > export the VMs to some storage, upgrade oVirt and then import the VMs > afterwards? > > Thanks in advance. > Will > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Upgrade path/possibility from 3.3?
Hi all, I have a couple of oVirt cluster running 3.3.3-2.el6. I would like to upgrade them to the latest version. I sort of remember upgrading from 3.3 to 3.5 required an step to upgrade to 3.4 as an extra step. With the new 3.6, will it be fine to upgrade straight from 3.3.3 to 3.6? or I need some extra steps? Another question is about preservation of the virtual machines. Can I export the VMs to some storage, upgrade oVirt and then import the VMs afterwards? Thanks in advance.Will___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path from Fedora 20 oVirt 3.5 to Fedora 22 oVirt 3.6
On 12/26/2015 2:22 PM, Blaster wrote: On 11/10/2015 1:10 AM, Sandro Bonazzola wrote: Hi, upgrade from FC20 to FC22 has not been tested and you're welcome to help testing it. What I would suggest is: - make an image of your existing engine (I suggest clonezilla for doing it) - install ovirt-release36 from http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm - fedup from fc20 to fc22 directly, without the fc21 step - run rpmconf -a and update relevant config files (be sure to not just overwrite them!) - run postgresql-setup --upgrade - run engine-setup I suggest to update to fc22 directly because there aren't FC21 builds of ovirt engine and the fedup process may not work as expected with missing repos. If the upgrade fails, you can restore the disk image created with clonezilla and retry with a different procedure. If you hit any issue or if you succeed let us know! So I did a fedup from 20 to 22, which went fairly well. I did have some issues though: named was missing some libraries after the upgrade. Removing named and reinstalling has fixed that up. rpmconf -a is giving me the following error: # rpmconf -a /usr/libexec/pk-command-not-found: error while loading shared libraries: libpackagekit-glib2.so.16: cannot open shared object file: No such file or directory dnf provides "*/libpackagekit-glib2.so.16" Last metadata expiration check performed 0:59:14 ago on Sat Dec 26 13:19:20 2015. Error: No Matches found So not sure what's going on there. I do have PackageKit-glib-devel installed. postgresql-setup upgrade Cannot upgrade because the database in /var/lib/pgsql/data is not of compatible previous version 9.2. What do I do about this? I did engine-setup afterwards and everything seems to be running fine. I did have to set my host CPU type back to Sandybridge as it wasn't recognizing my I7 4790K. Seems to be a known issue. I also have explanation points next to all my VMs stating that my time zone configuration differs between the VM config and the guest config, which they do not. Finally having a chance to get back at this. This ended up not going anywhere near as well as I had originally thought. The reason why the Postgress upgrade was failing was because I was still running 9.3 for some reason after the fedup upgrade. As I started diagnosing the known NFS server problem, I discovered after the fed22 update, it apparently only updates you to the base Fedora 22 packages. You then need to do a dnf update to get the latest. Which then fixed my NFS problem, but then vdsm refused to connect to the database. It was at that point I discovered my installed version of Postgress was now @ 9.4, instead of 9.3. Not sure how I got to 9.3, as I thought Fedora 20, which is where I came from has 9.2, and Fedora 22 had 9.4. So now I did the Postgress upgrade, which worked as expected above. But vdsm still would not connect to the database. After googling that issue, the only suggestion I saw was to remove the password from the vdsm conf file and re-run engine setup. That really upset Ovirt and it wiped out everything and proceeded to start with a fresh configuration, wiping out my datacenter. I do run a nightly ovirt backup, which I attempted to restore from, but it wouldn't let me do that as my backup which was from the previous night was for 3.5, and I was now at 3.6.1. So much for backups. It was at that point I just decided to investigate Hosted Engine, seeing as I was needing to start from scratch. After spending several hours researching that, it appears HE is know where near ready for any sort of daily driver. The WIKI how to seemed severely out of date and I couldn't find a usable engine appliance ISO that seemed to be ready to with out hours or days of additional hacking. So in the end I just re-ran the All-In-One setup and spent a couple hours rebuilding my datacenter. So to the above steps, a dnf update needs to added as a step after the fedup reboot. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path from Fedora 20 oVirt 3.5 to Fedora 22 oVirt 3.6
On Sat, Dec 26, 2015 at 2:22 PM, Blaster wrote: > On 11/10/2015 1:10 AM, Sandro Bonazzola wrote: >> >> Hi, upgrade from FC20 to FC22 has not been tested and you're welcome to >> help testing it. >> What I would suggest is: >> - make an image of your existing engine (I suggest clonezilla for doing >> it) >> - install ovirt-release36 from >> http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm >> - fedup from fc20 to fc22 directly, without the fc21 step >> - run rpmconf -a and update relevant config files (be sure to not just >> overwrite them!) >> - run postgresql-setup --upgrade >> - run engine-setup >> >> I suggest to update to fc22 directly because there aren't FC21 builds of >> ovirt engine and the fedup process may not work as expected with missing >> repos. >> >> If the upgrade fails, you can restore the disk image created with >> clonezilla and retry with a different procedure. >> >> If you hit any issue or if you succeed let us know! > > > So I did a fedup from 20 to 22, which went fairly well. I did have some > issues though: > > named was missing some libraries after the upgrade. Removing named and > reinstalling has fixed that up. > > rpmconf -a is giving me the following error: > # rpmconf -a > /usr/libexec/pk-command-not-found: error while loading shared libraries: > libpackagekit-glib2.so.16: cannot open shared object file: No such file or > directory > dnf provides "*/libpackagekit-glib2.so.16" > Last metadata expiration check performed 0:59:14 ago on Sat Dec 26 13:19:20 > 2015. > Error: No Matches found > > So not sure what's going on there. I do have PackageKit-glib-devel > installed. > Try doing "dnf reinstall *PackageKit*" to get everything correctly loaded. > postgresql-setup upgrade > > Cannot upgrade because the database in /var/lib/pgsql/data is not of > compatible previous version 9.2. > > What do I do about this? > The Fedora PostgreSQL packages only include the version of pgsql plus the previous. Fedora 22 had PostgreSQL 9.4 (with upgrade capability from 9.3, which was in Fedora 21). The way to solve that would be to forcibly install the postgresql-upgrade package from Fedora 21 to upgrade it correctly. I'm not sure that would work like you'd hope, though. > I did engine-setup afterwards and everything seems to be running fine. > Then don't worry about it, for now. > I did have to set my host CPU type back to Sandybridge as it wasn't > recognizing my I7 4790K. Seems to be a known issue. > > I also have explanation points next to all my VMs stating that my time zone > configuration differs between the VM config and the guest config, which they > do not. > Not sure why that's happening. -- 真実はいつも一つ！/ Always, there's only one truth! ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path from Fedora 20 oVirt 3.5 to Fedora 22 oVirt 3.6
On 11/10/2015 1:10 AM, Sandro Bonazzola wrote: Hi, upgrade from FC20 to FC22 has not been tested and you're welcome to help testing it. What I would suggest is: - make an image of your existing engine (I suggest clonezilla for doing it) - install ovirt-release36 from http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm - fedup from fc20 to fc22 directly, without the fc21 step - run rpmconf -a and update relevant config files (be sure to not just overwrite them!) - run postgresql-setup --upgrade - run engine-setup I suggest to update to fc22 directly because there aren't FC21 builds of ovirt engine and the fedup process may not work as expected with missing repos. If the upgrade fails, you can restore the disk image created with clonezilla and retry with a different procedure. If you hit any issue or if you succeed let us know! So I did a fedup from 20 to 22, which went fairly well. I did have some issues though: named was missing some libraries after the upgrade. Removing named and reinstalling has fixed that up. rpmconf -a is giving me the following error: # rpmconf -a /usr/libexec/pk-command-not-found: error while loading shared libraries: libpackagekit-glib2.so.16: cannot open shared object file: No such file or directory dnf provides "*/libpackagekit-glib2.so.16" Last metadata expiration check performed 0:59:14 ago on Sat Dec 26 13:19:20 2015. Error: No Matches found So not sure what's going on there. I do have PackageKit-glib-devel installed. postgresql-setup upgrade Cannot upgrade because the database in /var/lib/pgsql/data is not of compatible previous version 9.2. What do I do about this? I did engine-setup afterwards and everything seems to be running fine. I did have to set my host CPU type back to Sandybridge as it wasn't recognizing my I7 4790K. Seems to be a known issue. I also have explanation points next to all my VMs stating that my time zone configuration differs between the VM config and the guest config, which they do not. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path from Fedora 20 oVirt 3.5 to Fedora 22 oVirt 3.6
I've updgraded this way: fc20->fc21->fc22, because fedup couldn't find GPG-Key for FC22 repos. Next step: postgresql-setup --upgrade, because postgresql refused to start with unupgraded DB. After this I installed oVirt 3.6 release packege and did dnf update --best --allowerasing: it resulted in deletion of old engine packages, but since I've got AIO install, I checked that allinone plugin had also upgraded. First try to run engine-setup said, that it could not connect to DB, so I've copied old pg_hba.conf and also changed max_connections to 150 in postgresql.conf. After all this I've managed to successfully run engine-setup. Hi would like to be sure of the correct upgrate path to take. Should I first upgrade Fedora 20 -> Fedora 21 -> Fedora 22 and then upgrade oVirt from 3.5 to 3.6? Or would be better to upgrade in the Fedora 20: oVirt 3.5 -> oVirt 3.6 and then make the OS upgrades FD20->FD21->FD22 In the release notes http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_previous_versions [1] don't says anything about the upgrade path of the OS, but searching I'm aware that oVirt 3.5 is only compatible with FD20 not with 21, or 22 oVirt 3.6 is only compatible with FD20 not with 21 or 20 Thanks in advance -- David Marzal Cánovas Servicio de Mecanización e Informática Asamblea Regional de Murcia Paseo Alfonso XIII, nº53 30203 - Cartagena Tlfno: 968326800 Links: -- [1] http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_previous_versions ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path from Fedora 20 oVirt 3.5 to Fedora 22 oVirt 3.6
On Thu, Nov 12, 2015 at 4:26 PM, David Marzal Canovas wrote: > Hi Sandro, thanks for the tips. > > After a few problems, I think everything is working OK. > > I already had an image of my server so I tried the path that you suggested > and this is what I found: > > yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm > fedup --network 22 --product=server > > > This show a warning but the upgrade is successful : > > WARNING: potential problems with upgrade > ovirt-engine-backend-3.5.4.2-1.fc20.noarch (no replacement) requires > vdsm-jsonrpc-java-1.0.15-1.fc20.noarch (replaced by > vdsm-jsonrpc-java-1.1.5-1.fc22.noarch) > ovirt-engine-3.5.4.2-1.fc20.noarch (no replacement) requires > 1:java-1.7.0-openjdk-1.7.0.79-2.5.5.0.fc20.x86_64 (replaced by > 1:java-1.8.0-openjdk-1.8.0.65-3.b17.fc22.x86_64) > Continue with the upgrade at your own risk. > > > > After reboot the system is upgraded but perl is broken due to some > packages not being up to date. This can be fixed with (after allowing dnf > in the firewall ) > > dnf distro-sync --setopt=deltarpm=0 > > > Upgrade the DB and change the configuration (ovirt 3.6 needs lc_messages = > 'en_US.UTF-8' ) > > postgresql-setup --upgrade > vim /var/lib/pgsql/data/postgresql.conf > > /var/lib/pgsql/data/pg_hba.conf > > > Check the rest of configuration files > > rpmconf -a > > > Then check the services because nfs has some bug and dies on startup > https://bugzilla.redhat.com/show_bug.cgi?id=1192501 > https://bugzilla.redhat.com/show_bug.cgi?id=1178720 > > systemctl status postgresql.service nfs > > until you execute > > systemctl enable nfs-server.service > > > > And now we finally can upgrade oVirt > > engine-setup > > > It will show a warning about versionlock: > > DNF Failed loading plugin: versionlock > > But it would upgrade oVirt correctly. > > Great! > At my first attempt I don't have any problem with the > > fedup --network 22 --product=server > > but I didn't modify all the necessary files and fix the nfs so at one pont > y restore the image of the server and start over. > In the second attempt (the next day) the command complaint about > ovirt-release35-006-1 > > Downloading failed: El paquete ovirt-release35-006-1.noarch.rpm no está > firmado (is not signed) > > we add an issue with the tool we use for signing the rpms, it should be fixed now. > I had to remove this package and the files on /etc/yum.repos.d to be able > to upgrade Fedora to 22 > > yum remove ovirt-release35 > rm /etc/yum.repos.d/ovirt-3.5* > > I also test before trying to use fedup to just yum upgrade the system but > end with the same error so finally I delete ovirt-release35 and could > continue with the process described. > I hope this is useful if someone needs to upgrade their systems. > And thanks for an incredible product. :) > > > PD: Sorry for the (lack of) formating > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Upgrade path from Fedora 20 oVirt 3.5 to Fedora 22 oVirt 3.6
Hi Sandro, thanks for the tips. After a few problems, I think everything is working OK. I already had an image of my server so I tried the path that you suggested and this is what I found: yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm fedup --network 22 --product=server This show a warning but the upgrade is successful : WARNING: potential problems with upgrade ovirt-engine-backend-3.5.4.2-1.fc20.noarch (no replacement) requires vdsm-jsonrpc-java-1.0.15-1.fc20.noarch (replaced by vdsm-jsonrpc-java-1.1.5-1.fc22.noarch) ovirt-engine-3.5.4.2-1.fc20.noarch (no replacement) requires 1:java-1.7.0-openjdk-1.7.0.79-2.5.5.0.fc20.x86_64 (replaced by 1:java-1.8.0-openjdk-1.8.0.65-3.b17.fc22.x86_64) Continue with the upgrade at your own risk. After reboot the system is upgraded but perl is broken due to some packages not being up to date. This can be fixed with (after allowing dnf in the firewall ) dnf distro-sync --setopt=deltarpm=0 Upgrade the DB and change the configuration (ovirt 3.6 needs lc_messages = 'en_US.UTF-8' ) postgresql-setup --upgrade vim /var/lib/pgsql/data/postgresql.conf /var/lib/pgsql/data/pg_hba.conf Check the rest of configuration files rpmconf -a Then check the services because nfs has some bug and dies on startup https://bugzilla.redhat.com/show_bug.cgi?id=1192501 https://bugzilla.redhat.com/show_bug.cgi?id=1178720 systemctl status postgresql.service nfs until you execute systemctl enable nfs-server.service And now we finally can upgrade oVirt engine-setup It will show a warning about versionlock: DNF Failed loading plugin: versionlock But it would upgrade oVirt correctly. At my first attempt I don't have any problem with the fedup --network 22 --product=server but I didn't modify all the necessary files and fix the nfs so at one pont y restore the image of the server and start over. In the second attempt (the next day) the command complaint about ovirt-release35-006-1 Downloading failed: El paquete ovirt-release35-006-1.noarch.rpm no está firmado (is not signed) I had to remove this package and the files on /etc/yum.repos.d to be able to upgrade Fedora to 22 yum remove ovirt-release35 rm /etc/yum.repos.d/ovirt-3.5* I also test before trying to use fedup to just yum upgrade the system but end with the same error so finally I delete ovirt-release35 and could continue with the process described. I hope this is useful if someone needs to upgrade their systems. And thanks for an incredible product. :) PD: Sorry for the (lack of) formating ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path from Fedora 20 oVirt 3.5 to Fedora 22 oVirt 3.6
On Mon, Nov 9, 2015 at 11:14 AM, David Marzal Canovas wrote: > Hi would like to be sure of the correct upgrate path to take. > > Should I first upgrade Fedora 20 -> Fedora 21 -> Fedora 22 > > and then upgrade oVirt from 3.5 to 3.6? > > Or would be better to upgrade in the Fedora 20: oVirt 3.5 -> oVirt 3.6 > > and then make the OS upgrades FD20->FD21->FD22 > > In the release notes > http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_previous_versions > > don't says anything about the upgrade path of the OS, but searching I'm > aware that > > oVirt 3.5 is only compatible with FD20 not with 21, or 22 > > oVirt 3.6 is only compatible with FD20 not with 21 or 20 > > Thanks in advance > Hi, upgrade from FC20 to FC22 has not been tested and you're welcome to help testing it. What I would suggest is: - make an image of your existing engine (I suggest clonezilla for doing it) - install ovirt-release36 from http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm - fedup from fc20 to fc22 directly, without the fc21 step - run rpmconf -a and update relevant config files (be sure to not just overwrite them!) - run postgresql-setup --upgrade - run engine-setup I suggest to update to fc22 directly because there aren't FC21 builds of ovirt engine and the fedup process may not work as expected with missing repos. If the upgrade fails, you can restore the disk image created with clonezilla and retry with a different procedure. If you hit any issue or if you succeed let us know! > -- > David Marzal Cánovas > Servicio de Mecanización e Informática > Asamblea Regional de Murcia > Paseo Alfonso XIII, nº53 > 30203 - Cartagena > Tlfno: 968326800 > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Upgrade path from Fedora 20 oVirt 3.5 to Fedora 22 oVirt 3.6
Hi would like to be sure of the correct upgrate path to take. Should I first upgrade Fedora 20 -> Fedora 21 -> Fedora 22 and then upgrade oVirt from 3.5 to 3.6? Or would be better to upgrade in the Fedora 20: oVirt 3.5 -> oVirt 3.6 and then make the OS upgrades FD20->FD21->FD22 In the release notes http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_previous_versions [1] don't says anything about the upgrade path of the OS, but searching I'm aware that oVirt 3.5 is only compatible with FD20 not with 21, or 22 oVirt 3.6 is only compatible with FD20 not with 21 or 20 Thanks in advance -- David Marzal Cánovas Servicio de Mecanización e Informática Asamblea Regional de Murcia Paseo Alfonso XIII, nº53 30203 - Cartagena Tlfno: 968326800 Links: -- [1] http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_previous_versions___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] upgrade path from Ovirt 3.5x to 3.6x
Thanks Michal, Your reply somehow answer to my question, but I still have some bits of fuzziness Hosted engine VM upgrade itself is almost clear (maintenance, db backup, reformat, reinstall, db import). However: 1. Inter-cluster migration is somehow unsupported. Should we worried about moving VM from EL6 cluster to EL7? You know... different vdsm etc is ovirt migration feature atomic and reversible (if something goes wrong during the process)? 2. More important: the only Ovirt version that supports both EL6.6 and EL7.1 is 3.53. my real question is: what happen as soon as I finish upgrade of my ovirt to version 3.54 (or 3.55) *while running HOSTS on EL6.6* ? I mean, there will be a point in time when a version mismatch/overlap will be unavoidable. For example: how people should correctly jump from version 3.53 (EL6.6) to 3.54 (EL6.7)? Ovirt team should support at least one or two previous version to support overlaps... Thanks AG *From:* Michal Skrivanek [mailto:michal.skriva...@redhat.com] *Sent:* Friday, October 09, 2015 1:33 PM *To:* Andrea Ghelardi *Cc:* users (users@ovirt.org); Simone Tiraboschi *Subject:* Re: [ovirt-users] upgrade path from Ovirt 3.5x to 3.6x nono, the upgrade is live and all your VMs can keep humming. But there are manual steps involved: Simone can probably update about Hosted Engine which would be somewhat special, but at least for regular VMs you can currently use: 1) create a new cluster with same settings as your existing cluster 2) remove one host from the old cluster (the one to be upgraded/reinstalled to EL7). While moving the host to maintenance your VMs will be migrated to other EL6 hosts in that cluster (make sure you have enough capacity to do that beforehand, of course:) 3) upgrade/reinstall the host with EL7. If youdon't have anything custom on the host reinstallation might be the best option 4) add it to the new cluster, installing/deploying it via UI, then it should come up - this is your EL7-based cluster now 5) manually migrate (Migrate To button) some of your VMs from the old cluster to the new one (there's an advanced section in the dialog, allowing you cross-cluster migrations 6) repeat until all your hosts and VMs are on EL7-based cluster, then you can decommission it, and perhaps rename the cluster back to its original name Thanks, michal ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] upgrade path from Ovirt 3.5x to 3.6x
On 8 Oct 2015, at 17:48, Andrea Ghelardi wrote: > Hallo, > I needed a quick confirmation on this subject. > > Our environment is Ovirt 3.511 (yes, I’ll upgrade soon, I know) running on a > Centos 6.6 hosted engine VM on a cluster of Centos 6.6 physical servers. > > Since Ovirt 3.6x will be compatible with Centos 7 hypervisor only, how I’m > supposed to upgrade hosted engine, VM and HOSTs? > > i.e. readme tells us the well known procedure (put hosted eng in maintenance, > upgrade, etc) but I will eventually end in a scenario where my hosted engine > 3.6 will run on centos 7 VM running (on) a lot of centos 6.6 servers... > > Please tell me I have not to create a totally different datacenter and export > -> import all VMs… nono, the upgrade is live and all your VMs can keep humming. But there are manual steps involved: Simone can probably update about Hosted Engine which would be somewhat special, but at least for regular VMs you can currently use: 1) create a new cluster with same settings as your existing cluster 2) remove one host from the old cluster (the one to be upgraded/reinstalled to EL7). While moving the host to maintenance your VMs will be migrated to other EL6 hosts in that cluster (make sure you have enough capacity to do that beforehand, of course:) 3) upgrade/reinstall the host with EL7. If youdon't have anything custom on the host reinstallation might be the best option 4) add it to the new cluster, installing/deploying it via UI, then it should come up - this is your EL7-based cluster now 5) manually migrate (Migrate To button) some of your VMs from the old cluster to the new one (there's an advanced section in the dialog, allowing you cross-cluster migrations 6) repeat until all your hosts and VMs are on EL7-based cluster, then you can decommission it, and perhaps rename the cluster back to its original name Thanks, michal > > Thank you! > Andrea Ghelardi > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] upgrade path from Ovirt 3.5x to 3.6x
Hallo, I needed a quick confirmation on this subject. Our environment is Ovirt 3.511 (yes, I’ll upgrade soon, I know) running on a Centos 6.6 hosted engine VM on a cluster of Centos 6.6 physical servers. Since Ovirt 3.6x will be compatible with Centos 7 hypervisor only, how I’m supposed to upgrade hosted engine, VM and HOSTs? i.e. readme tells us the well known procedure (put hosted eng in maintenance, upgrade, etc) but I will eventually end in a scenario where my hosted engine 3.6 will run on centos 7 VM running (on) a lot of centos 6.6 servers... Please tell me I have not to create a totally different datacenter and export -> import all VMs... Thank you! Andrea Ghelardi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade path
Dear Johan Basically we did just that last week, but we created a new cluster and put it new hosts with CentOS 7.1 and then migrated the machines, we also made the experience that Live Migration between clusters (in this Case Fedora 20 -> CentOS 7.1) does work if not you have to reboot the hosts. The last thing we did not due is migrated the hosted engine as well, but from my understanding it should basically be that same as migrating to a hosted engine – i will report once we go there Cheers Soeren From: Johan Kooijman mailto:m...@johankooijman.com>> Date: Thursday 28 May 2015 09:39 To: users mailto:users@ovirt.org>> Subject: [ovirt-users] Upgrade path Hi all, What would be the best upgrade path for upgrading a 3.5.2 cluster from C6 to C7? Am I right in understanding that a cluster can have mixed hosts, but once a VM is on a C7 host, it cannot be migrated back to C6? -- Met vriendelijke groeten / With kind regards, Johan Kooijman ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Upgrade path
Hi all, What would be the best upgrade path for upgrading a 3.5.2 cluster from C6 to C7? Am I right in understanding that a cluster can have mixed hosts, but once a VM is on a C7 host, it cannot be migrated back to C6? -- Met vriendelijke groeten / With kind regards, Johan Kooijman ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
