Hello! I was asking because I use my 3 hypervisor also as providers of glusterfs bricks (replicate) and I have some issue when I upgraded Hypervisor (think about glusterfs packages and vdsm-gluster).
In your configuration you you shouldn't have any problems if you do it as per your e-mail. On Fri, Oct 31, 2014 at 1:17 PM, Markus Stockhausen <[email protected] > wrote: > Hi, > > sorry I forgot that: NFS, engine is running in a qemu VM "outside" the > cluster. > > Markus > ------------------------------ > *Von:* Gabi C [[email protected]] > *Gesendet:* Freitag, 31. Oktober 2014 12:12 > *An:* Markus Stockhausen > *Cc:* ovirt-users > *Betreff:* Re: [ovirt-users] Upgrade order 3.4.2 -> 3.5.x > > Hello! > > What kind of storage domains do you have? > > On Fri, Oct 31, 2014 at 1:02 PM, Markus Stockhausen < > [email protected]> wrote: > >> Hi, >> >> maybe a stupid one. Just want to make sure that nothing goes wrong. We >> plan to make a rolling upgrade of our landscape going to 3.5.1 in >> december. >> So we always need some hypervisor nodes up and running during the >> process. >> >> Looking at older posts I assume that upgrading the engine should be >> sufficient, while hypervisor nodes with vdsm 4.14.17 (from 3.4 repos) and >> the active VMs keep on running. The start of the engine after the upgrade >> should catch up and resync all states. >> >> Afterwards I clean hypervisor hosts one by one and clean/reinstall it >> into >> the cluster? >> >> Thanks in advance. >> >> Markus >> >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/users >> >> >
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
