Ack, thx. On Tue, Feb 16, 2016 at 11:46 AM, Yedidyah Bar David <[email protected]> wrote:
> On Tue, Feb 16, 2016 at 11:58 AM, Johan Kooijman <[email protected]> > wrote: > > Didi, > > > > Ok, the piece of information on engine still supported on 3.6 was > unknown to > > me. Makes my job a lot easier. > > > > What would be the recommended path: first upgrade the nodes to 3.6 and > then > > the engine? Or the other way around? > > Generally speaking, first engine then nodes. I am pretty certain it's > documented > on the wiki, didn't check. > > > > > On Tue, Feb 16, 2016 at 8:45 AM, Yedidyah Bar David <[email protected]> > wrote: > >> > >> On Tue, Feb 16, 2016 at 9:30 AM, Johan Kooijman <[email protected] > > > >> wrote: > >> > Yes. I pasted the information on AIO, that was wrong on my end. I have > >> > an > >> > engine running on dedicated hardware and about 20 nodes in this > cluster. > >> > I > >> > do like to upgrade without downtime :) I know how to achieve this on > the > >> > node-end, but since I have to go from C6 to C7, I wonder what the > >> > procedure > >> > would be for engine. > >> > >> Please explain exactly what you are trying to do. > >> > >> Note that engine is still supported on el6. > >> > >> (new) Hosts are not. > >> > >> all-in-one is running both together, thus is not supported on el6 > either. > >> > >> IIRC we do not have a tested procedure to upgrade the engine from C6 to > C7 > >> yet, see also: > >> > >> https://bugzilla.redhat.com/show_bug.cgi?id=1234257 > >> https://bugzilla.redhat.com/show_bug.cgi?id=1285743 > >> > >> Best, > >> > >> > > >> > On Mon, Feb 15, 2016 at 9:21 PM, Alexander Wels <[email protected]> > >> > wrote: > >> >> > >> >> On Monday, February 15, 2016 08:21:40 PM Johan Kooijman wrote: > >> >> > Hi Alexander, > >> >> > > >> >> > Thanks for the input! My 3.5 is running on C6 however: > >> >> > > >> >> > Upgrade of All-in-One on EL6 is not supported in 3.6. VDSM and the > >> >> > packages > >> >> > requiring it are not built anymore for EL6 > >> >> > > >> >> > >> >> Well that was a piece of information you forgot to mention in your > >> >> initial > >> >> email. So now I am not entirely sure what you are trying to do. Are > you > >> >> trying > >> >> to save your existing VMs when you reinstall your machine? > >> >> > >> >> > >> >> > On Mon, Feb 15, 2016 at 3:37 PM, Alexander Wels <[email protected]> > >> >> > wrote: > >> >> > > On Monday, February 15, 2016 02:40:47 PM Johan Kooijman wrote: > >> >> > > > Hi, > >> >> > > > > >> >> > > > Can anybody recommend me best practice upgrade path for an > >> >> > > > upgrade > >> >> > > > from > >> >> > > > oVirt 3.5 on C6 to 3.6 on C7.2? > >> >> > > > >> >> > > The answer sort of depends on what you want. Do you want no > >> >> > > downtime > >> >> > > on > >> >> > > your > >> >> > > VMs or is downtime acceptable. Also are you running hosted engine > >> >> > > or > >> >> > > not? > >> >> > > > >> >> > > This is the basic plan which can be adjusted based on what your > >> >> > > needs > >> >> > > are: > >> >> > > > >> >> > > 1. Update engine from 3.5 to 3.6 (if hosted engine might be > >> >> > > trickier, > >> >> > > not > >> >> > > sure > >> >> > > haven't played with hosted engine). > >> >> > > 2. Create a new 3.6 cluster. > >> >> > > 3. Put 1 host in maintenance (which will migrate the VMs to the > >> >> > > other > >> >> > > hosts). > >> >> > > 4. Remove the host from the DC. > >> >> > > 5. Install C7.2 on the host > >> >> > > 6. Add that host to the new 3.6 cluster. > >> >> > > 7. Optional (you can cross cluster live migrate some VMs from 6 > to > >> >> > > 7 > >> >> > > (just > >> >> > > not > >> >> > > the other way around, so once the VM is moved its stuck in the > new > >> >> > > cluster). > >> >> > > 8. Go to 3 until all hosts are moved. > >> >> > > 9. Your 3.5 cluster should now be empty, and can be removed. > >> >> > > 10. Upgrade your DC to 3.6 (Can't upgrade if any lower clusters > >> >> > > exist). > >> >> > > > >> >> > > If you can have downtime, then just shut down the VMs running on > >> >> > > the > >> >> > > host > >> >> > > in > >> >> > > step 3 before putting it in maintenance. Once the host is moved > to > >> >> > > the > >> >> > > new > >> >> > > cluster you can start the VMs. > >> >> > > > >> >> > > Alexander > >> >> > > _______________________________________________ > >> >> > > Users mailing list > >> >> > > [email protected] > >> >> > > http://lists.ovirt.org/mailman/listinfo/users > >> >> > >> > > >> > > >> > > >> > -- > >> > Met vriendelijke groeten / With kind regards, > >> > Johan Kooijman > >> > > >> > _______________________________________________ > >> > Users mailing list > >> > [email protected] > >> > http://lists.ovirt.org/mailman/listinfo/users > >> > > >> > >> > >> > >> -- > >> Didi > > > > > > > > > > -- > > Met vriendelijke groeten / With kind regards, > > Johan Kooijman > > > > -- > Didi > -- Met vriendelijke groeten / With kind regards, Johan Kooijman
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
