10:29 a.m.
This is a multi-part message in MIME format.
--------------080008030808040800040009
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
can oVirt 3.6 manage hypervizors with 3.5 version ?
Meaning during cluster upgrade step by step.
( A) oVirt mgmt , B) 1st.hypervizor, C) 2nd hypervizor, .... .. )
If oVirt DB converted from 3.5.5 -> 3.5.5.upg.3.6 -> final 3.6
regs. Paf1
--------------080008030808040800040009
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
</head>
<body text="#000066" bgcolor="#FFFFFF">
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>
</body>
</html>
--------------080008030808040800040009--
11:24 a.m.
Hi,
yes, this is correct way how to do the upgrade:
1. Upgrade engine
2. Put each host into maintenance and upgrade it
3. When all hosts in cluster are upgraded you can raise
cluster level
DB upgrade is done during upgrade engine part automatically:
1. Add 3.6 repos
2. yum update 'ovirt-engine-setup*'
3. engine-setup
Martin Perina
----- Original Message -----
From: paf1(a)email.cz
To: users(a)ovirt.org
Sent: Friday, November 6, 2015 10:29:22 AM
Subject: [ovirt-users] can oVirt 3.6 manage 3.5 hypervizor
Hi,
can oVirt 3.6 manage hypervizors with 3.5 version ?
Meaning during cluster upgrade step by step.
( A) oVirt mgmt , B) 1st.hypervizor, C) 2nd hypervizor, .... .. )
If oVirt DB converted from 3.5.5 -> 3.5.5.upg.3.6 -> final 3.6
regs. Paf1
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
8:33 p.m.
New subject: can oVirt 3.6 manage 3.5 hypervizor
On Nov 6, 2015 12:24, "Martin Perina" <mperina(a)redhat.com> wrote:
Hi,
yes, this is correct way how to do the upgrade:
1. Upgrade engine
2. Put each host into maintenance and upgrade it
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.
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.
3. When all hosts in cluster are upgraded you can raise
cluster level
DB upgrade is done during upgrade engine part automatically:
1. Add 3.6 repos
2. yum update 'ovirt-engine-setup*'
3. engine-setup
Martin Perina
----- Original Message -----
> From: paf1(a)email.cz
> To: users(a)ovirt.org
> Sent: Friday, November 6, 2015 10:29:22 AM
> Subject: [ovirt-users] can oVirt 3.6 manage 3.5 hypervizor
>
> Hi,
> can oVirt 3.6 manage hypervizors with 3.5 version ?
> Meaning during cluster upgrade step by step.
> ( A) oVirt mgmt , B) 1st.hypervizor, C) 2nd hypervizor, .... .. )
> If oVirt DB converted from 3.5.5 -> 3.5.5.upg.3.6 -> final 3.6
> regs. Paf1
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:17 p.m.
New subject: can oVirt 3.6 manage 3.5 hypervizor
On Fri, Nov 6, 2015 at 8:33 PM, Oved Ourfali <oourfali(a)redhat.com> wrote:
On Nov 6, 2015 12:24, "Martin Perina" <mperina(a)redhat.com> wrote:
>
> Hi,
>
> yes, this is correct way how to do the upgrade:
>
> 1. Upgrade engine
> 2. Put each host into maintenance and upgrade it
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.
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.
Martin, Oved, can you please amend
http://www.ovirt.org/OVirt_3.6_Release_Notes#Install_.2F_Upgrade_from_pre...
with host upgrade?
> 3. When all hosts in cluster are upgraded you can raise
> cluster level
>
> DB upgrade is done during upgrade engine part automatically:
>
> 1. Add 3.6 repos
> 2. yum update 'ovirt-engine-setup*'
> 3. engine-setup
>
> Martin Perina
>
> ----- Original Message -----
> > From: paf1(a)email.cz
> > To: users(a)ovirt.org
> > Sent: Friday, November 6, 2015 10:29:22 AM
> > Subject: [ovirt-users] can oVirt 3.6 manage 3.5 hypervizor
> >
> > Hi,
> > can oVirt 3.6 manage hypervizors with 3.5 version ?
> > Meaning during cluster upgrade step by step.
> > ( A) oVirt mgmt , B) 1st.hypervizor, C) 2nd hypervizor, .... .. )
> > If oVirt DB converted from 3.5.5 -> 3.5.5.upg.3.6 -> final 3.6
> > regs. Paf1
> >
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
_______________________________________________
Users mailing list
Users(a)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
3096
days inactive
3099
days old
3 comments
4 participants
participants (4)
-
Martin Perina -
Oved Ourfali -
paf1＠email.cz -
Sandro Bonazzola