<div dir="ltr">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.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 15, 2016 at 9:21 PM, Alexander Wels <span dir="ltr"><<a href="mailto:awels@redhat.com" target="_blank">awels@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Monday, February 15, 2016 08:21:40 PM Johan Kooijman wrote:<br>
> Hi Alexander,<br>
><br>
> Thanks for the input! My 3.5 is running on C6 however:<br>
><br>
> Upgrade of All-in-One on EL6 is not supported in 3.6. VDSM and the packages<br>
> requiring it are not built anymore for EL6<br>
><br>
<br>
</span>Well that was a piece of information you forgot to mention in your initial<br>
email. So now I am not entirely sure what you are trying to do. Are you trying<br>
to save your existing VMs when you reinstall your machine?<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
> On Mon, Feb 15, 2016 at 3:37 PM, Alexander Wels <<a href="mailto:awels@redhat.com">awels@redhat.com</a>> wrote:<br>
> > On Monday, February 15, 2016 02:40:47 PM Johan Kooijman wrote:<br>
> > > Hi,<br>
> > ><br>
> > > Can anybody recommend me best practice upgrade path for an upgrade from<br>
> > > oVirt 3.5 on C6 to 3.6 on C7.2?<br>
> ><br>
> > The answer sort of depends on what you want. Do you want no downtime on<br>
> > your<br>
> > VMs or is downtime acceptable. Also are you running hosted engine or not?<br>
> ><br>
> > This is the basic plan which can be adjusted based on what your needs are:<br>
> ><br>
> > 1. Update engine from 3.5 to 3.6 (if hosted engine might be trickier, not<br>
> > sure<br>
> > haven't played with hosted engine).<br>
> > 2. Create a new 3.6 cluster.<br>
> > 3. Put 1 host in maintenance (which will migrate the VMs to the other<br>
> > hosts).<br>
> > 4. Remove the host from the DC.<br>
> > 5. Install C7.2 on the host<br>
> > 6. Add that host to the new 3.6 cluster.<br>
> > 7. Optional (you can cross cluster live migrate some VMs from 6 to 7 (just<br>
> > not<br>
> > the other way around, so once the VM is moved its stuck in the new<br>
> > cluster).<br>
> > 8. Go to 3 until all hosts are moved.<br>
> > 9. Your 3.5 cluster should now be empty, and can be removed.<br>
> > 10. Upgrade your DC to 3.6 (Can't upgrade if any lower clusters exist).<br>
> ><br>
> > If you can have downtime, then just shut down the VMs running on the host<br>
> > in<br>
> > step 3 before putting it in maintenance. Once the host is moved to the new<br>
> > cluster you can start the VMs.<br>
> ><br>
> > Alexander<br>
> > _______________________________________________<br>
> > Users mailing list<br>
> > <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Met vriendelijke groeten / With kind regards,<br>Johan Kooijman<br></div></div>
</div>