<p dir="ltr"><br>
On Nov 6, 2015 12:24, "Martin Perina" <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> yes, this is correct way how to do the upgrade:<br>
><br>
> 1. Upgrade engine<br>
> 2. Put each host into maintenance and upgrade it</p>
<p dir="ltr">Actually in 3.6 the upgrade button will be enabled when there is an upgrade available, and pressing it will also move the host to maintenance if needed. </p>
<p dir="ltr">As long as the cluster level is 3.5 (existing cluster level doesn't change after upgrade) you'll be able to work with 3.5 hosts. <br></p>
<p dir="ltr">> 3. When all hosts in cluster are upgraded you can raise<br>
> cluster level<br>
><br>
> DB upgrade is done during upgrade engine part automatically:<br>
><br>
> 1. Add 3.6 repos<br>
> 2. yum update 'ovirt-engine-setup*'<br>
> 3. engine-setup<br>
><br>
> Martin Perina<br>
><br>
> ----- Original Message -----<br>
> > From: <a href="mailto:paf1@email.cz">paf1@email.cz</a><br>
> > To: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
> > Sent: Friday, November 6, 2015 10:29:22 AM<br>
> > Subject: [ovirt-users] can oVirt 3.6 manage 3.5 hypervizor<br>
> ><br>
> > Hi,<br>
> > can oVirt 3.6 manage hypervizors with 3.5 version ?<br>
> > Meaning during cluster upgrade step by step.<br>
> > ( A) oVirt mgmt , B) 1st.hypervizor, C) 2nd hypervizor, .... .. )<br>
> > If oVirt DB converted from 3.5.5 -> 3.5.5.upg.3.6 -> final 3.6<br>
> > regs. Paf1<br>
> ><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">http://lists.ovirt.org/mailman/listinfo/users</a><br>
> ><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">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
><br>
</p>