Hi,
Can anybody recommend me best practice upgrade path for an upgrade from
oVirt 3.5 on C6 to 3.6 on C7.2?
--
Met vriendelijke groeten / With kind regards,
Johan Kooijman
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/u
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
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
On Mon, Feb 15, 2016 at 3:37 PM, Alexander Wels wrote:
> On Monday, February 15, 2016 02:40:47 PM Johan
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 infor
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
w
On Tue, Feb 16, 2016 at 9:30 AM, Johan Kooijman 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
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?
On Tue, Feb 16, 2016 at 8:45 AM, Yedidyah Bar David wrote:
> On Tue
On Tue, Feb 16, 2016 at 11:58 AM, Johan Kooijman 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?
Ack, thx.
On Tue, Feb 16, 2016 at 11:46 AM, Yedidyah Bar David
wrote:
> On Tue, Feb 16, 2016 at 11:58 AM, Johan Kooijman
> 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 recomme
On Tuesday, February 16, 2016 12:36:58 PM Johan Kooijman wrote:
> Ack, thx.
>
> On Tue, Feb 16, 2016 at 11:46 AM, Yedidyah Bar David
>
> wrote:
> > On Tue, Feb 16, 2016 at 11:58 AM, Johan Kooijman
> >
> > wrote:
> > > Didi,
> > >
> > > Ok, the piece of information on engine still supported on
16.02.2016, 16:31, "Alexander Wels" :On Tuesday, February 16, 2016 12:36:58 PM Johan Kooijman wrote: Ack, thx. On Tue, Feb 16, 2016 at 11:46 AM, Yedidyah Bar David wrote: > On Tue, Feb 16, 2016 at 11:58 AM, Johan Kooijman > > wrote: > > Didi, > > > > O
On Wed, Feb 17, 2016 at 9:09 AM, Николаев Алексей
wrote:
> You must not configure firewall in backup restore procedure. Because EL6
> backup uses iptables instead EL7 fresh install uses firewalld.
Thanks for pointing that out!
Does this mean you actually tried this and that was the only issue?
17.02.2016, 10:36, "Yedidyah Bar David" :On Wed, Feb 17, 2016 at 9:09 AM, Николаев Алексей wrote: You must not configure firewall in backup restore procedure. Because EL6 backup uses iptables instead EL7 fresh install uses firewalld.Thanks for pointing that out!Does
13 matches
Mail list logo