Bug 1188679

It has been decided that HE for 3.6 will be supported only on EL7 nodes.
We'll need to
 - provide a guide for migrating from HE 3.5 on EL6 to HE 3.6 on EL7.
 - cover this migration in QE test cases.
 - test the migration ensuring it works smoothly.

this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Can you provide content to start work on this guide?

(In reply to Yaniv Dary from comment #3)
> Can you provide content to start work on this guide?

We're discussing about possible paths.

1) add an el7 host to a new cluster in the same domain and let the agent, shutdown the vm on the el6 cluster and let the el7 one to start it having 3.6 an higer score than 3.5. Then migrate the remaining hosts.

2) create a brand new cluster and use backup on el6 / restore on el7 procedure.

Can QE assist testing the 2 paths?

Please provide the bug number that tracks the testing of this function(if there is one), and please need_info me once the work flow has been tested and is ready to be added to the 3.6 SHE Guide.

Kind regards,
Julie

(In reply to Sandro Bonazzola from comment #4)
> (In reply to Yaniv Dary from comment #3)
> > Can you provide content to start work on this guide?
> 
> We're discussing about possible paths.
> 
> 1) add an el7 host to a new cluster in the same domain and let the agent,
> shutdown the vm on the el6 cluster and let the el7 one to start it having
> 3.6 an higer score than 3.5. Then migrate the remaining hosts.
> 
> 2) create a brand new cluster and use backup on el6 / restore on el7
> procedure.
> 
> Can QE assist testing the 2 paths?

Pavel, do we have test cases for these paths?

(In reply to Yaniv Dary from comment #6)
> (In reply to Sandro Bonazzola from comment #4)
> > (In reply to Yaniv Dary from comment #3)
> > > Can you provide content to start work on this guide?
> > 
> > We're discussing about possible paths.
> > 
> > 1) add an el7 host to a new cluster in the same domain and let the agent,
> > shutdown the vm on the el6 cluster and let the el7 one to start it having
> > 3.6 an higer score than 3.5. Then migrate the remaining hosts.
> > 
> > 2) create a brand new cluster and use backup on el6 / restore on el7
> > procedure.
> > 
> > Can QE assist testing the 2 paths?
> 
> Pavel, do we have test cases for these paths?

Passing to Meital, her team is testing hosted engine.

We don't have test cases for these paths. 
Moran, I would like to get ordered flow of the HE upgrade from el6 to el7.

(In reply to meital avital from comment #8)
> We don't have test cases for these paths. 
> Moran, I would like to get ordered flow of the HE upgrade from el6 to el7.

Doron, what would be the supported way to do it. i would imagine some backup restore (migration) from el6 to el7?

To my understanding from talking to Meital today this should be included in the in-cluster upgrade path from el6 to el7 with a added step of re-deploying host on the el7 machine post installation.

There's already a documented way to move a deployment from el6 to el7.

Assuming it was performed and all hosts are el7, you will need to use the backup
utility in the hosted engine VM, and then restore it into a new el7 appliance.

(In reply to Doron Fediuck from comment #11)
> There's already a documented way to move a deployment from el6 to el7.
> 
> Assuming it was performed and all hosts are el7, you will need to use the
> backup
> utility in the hosted engine VM, and then restore it into a new el7
> appliance.

This bug is about moving the hosted engine 3.6 el6 appliance from EL6 hypervisor to EL7 hypervisor on 3.5. Please add details to how this should be done.

Assigning to Julie for review.

Julie, we can start by writing up the instructions provided, and work with QE to verify that the documented flow is correct.

Now finished writing a first draft of such a guide [1] for upstream docs. I'll shortly send a pull request to get it to the site. Comments are welcome.

[1] https://github.com/didib/ovirt-site/blob/master/source/documentation/how-to/hosted-engine-host-OS-upgrade.html.md

(In reply to Yedidyah Bar David from comment #18)
> Now finished writing a first draft of such a guide [1] for upstream docs.
> I'll shortly send a pull request to get it to the site. Comments are welcome.
> 
> [1]
> https://github.com/didib/ovirt-site/blob/master/source/documentation/how-to/
> hosted-engine-host-OS-upgrade.html.md

Please add steps that will not have error, this should be done with a modified answer file for first host and using it for later migration, not failing on every host add.

(In reply to Yaniv Dary from comment #19)
> (In reply to Yedidyah Bar David from comment #18)
> > Now finished writing a first draft of such a guide [1] for upstream docs.
> > I'll shortly send a pull request to get it to the site. Comments are welcome.
> > 
> > [1]
> > https://github.com/didib/ovirt-site/blob/master/source/documentation/how-to/
> > hosted-engine-host-OS-upgrade.html.md
> 
> Please add steps that will not have error, this should be done with a
> modified answer file for first host and using it for later migration, not
> failing on every host add.

I only wrote there things I tried.

I might have time next week to try that too and amend accordingly.

Others - if you try that, please comment here with details. Thanks.

Documentation Link:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Self-Hosted_Engine_Guide/Upgrading_the_Self-Hosted_Engine_from_6_to_7.html