applied the fixes to 4.0.5.5.
-Original Message-
From: Yedidyah Bar David <d...@redhat.com>
Date: Tuesday 24 January 2017 at 23:51
To: Pavel Gashev <p...@acronis.com>
Cc: Karli Sjöberg <karli.sjob...@slu.se>, "users@ovirt.org" <users@ovirt.org>
Subject: Re: [o
ob...@slu.se>
> Date: Tuesday 24 January 2017 at 15:24
> To: "fernando.fredi...@upx.com.br" <fernando.fredi...@upx.com.br>, Pavel
> Gashev <p...@acronis.com>, "users@ovirt.org" <users@ovirt.org>
> Subject: Re: [ovirt-users] 4.0 x 4.1
>
> On Tue, 2017-01-24
017 at 15:24
To: "fernando.fredi...@upx.com.br" <fernando.fredi...@upx.com.br>, Pavel Gashev
<p...@acronis.com>, "users@ovirt.org" <users@ovirt.org>
Subject: Re: [ovirt-users] 4.0 x 4.1
On Tue, 2017-01-24 at 11:06 +, Pavel Gashev wrote:
> I'd li
On Tue, Jan 24, 2017 at 3:15 PM, Fernando Frediani
wrote:
> Sounds reasonable.
>
> Out of curiosity what people use or do in order to rollback a failed upgrade
Usually engine-setup rolls back fine if it fails after it started
changing the system.
You can also
Sounds reasonable.
Out of curiosity what people use or do in order to rollback a failed
upgrade or an upgrade that can bring instability in the control or
operation of the cluster ? In VMware as vCenter used to run within a
Virtual Machine I used to take a snapshot before starting the
ased
> soon. Thus, I’d start with 4.0 and upgrade to 4.1 when 4.2 is
> released.
>
> -Original Message-
> From: <users-boun...@ovirt.org> on behalf of Fernando Frediani ndo.fredi...@upx.com.br>
> Date: Monday 23 January 2017 at 22:36
> To: "users@ovirt.or
: Tuesday 24 January 2017 at 13:38
To: Fernando Frediani <fernando.fredi...@upx.com.br>, "users@ovirt.org"
<users@ovirt.org>
Subject: Re: [ovirt-users] 4.0 x 4.1
I started with oVirt 3.6. It became stable since 3.6.7 just when 4.0 is
released. Also I use 4.0. The
Message-
From: <users-boun...@ovirt.org> on behalf of Fernando Frediani
<fernando.fredi...@upx.com.br>
Date: Monday 23 January 2017 at 22:36
To: "users@ovirt.org" <users@ovirt.org>
Subject: [ovirt-users] 4.0 x 4.1
I am deploying a oVirt environment which will not get
On Mon, Jan 23, 2017 at 9:36 PM, Fernando Frediani
wrote:
> I am deploying a oVirt environment which will not get production data
> immediately.
>
> Obviously I would rather use 4.1 RC due the many changes and fixes present.
> Later when 4.1 becomes stable then
I am deploying a oVirt environment which will not get production data
immediately.
Obviously I would rather use 4.1 RC due the many changes and fixes
present. Later when 4.1 becomes stable then upgrade to it.
Does anyone see any problem in doing that way or would it be more
advisable to start
10 matches
Mail list logo