<div dir="ltr"><div class="gmail_quote"><div class="GmSign">Hi Yedidyah,</div><div class="GmSign"><br></div><div class="GmSign">Thank you for the comprehensive answers.</div><div class="GmSign"><br></div><div class="GmSign">I think I go for a complete reinstall ( read also OS upgrade tool is not adviced on 6.6 or higher as there might be newer packages as on 7 ). No doubting to re-use current VM or setup from scratch ( fresh host with new hosted-engine and existing storage domein ).</div><div class="GmSign"><br></div><div class="GmSign">You explain the steps ( 1 to 6 ), but then don't talk about storage domain import.</div><div class="GmSign">Does it mean, when I reinstall the hosted-engine in the current he VM and <span style="line-height:1.5">restore an engine-backup ( step 5 ) I am able to start vm from Host and it is still connected to the master storage ( so no need for storage import) ?</span></div><div class="GmSign"><br></div><div class="GmSign">Best Regards,</div><div class="GmSign">Paul Groeneweg</div><div class="GmSign"><br><br></div><div dir="ltr">Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David <<a href="mailto:didi@redhat.com">didi@redhat.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion<br>
<<a href="mailto:paul@pazion.nl" target="_blank">paul@pazion.nl</a>> wrote:<br>
><br>
> I am looking for a way to get my hosted-engine running on el7 so I can<br>
> upgrade to oVirt 4.0. Currently my hosts already run el7, but my<br>
> hosted-engine is still el6.<br>
><br>
> I read<br>
> <a href="https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/" rel="noreferrer" target="_blank">https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/</a><br>
> but this is only about the hosts.<br>
><br>
> I read <a href="https://www.ovirt.org/documentation/how-to/hosted-engine/" rel="noreferrer" target="_blank">https://www.ovirt.org/documentation/how-to/hosted-engine/</a>, but it<br>
> only mentions upgrade of the hosted-engine software, not the OS.<br>
><br>
> I understood I can do a fresh hosted-engine install, and then import my<br>
> storage domain to the new hosted engine, but:<br>
><br>
> - Do I need to restore my hosted engine database? ( like described here:<br>
> <a href="http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/" rel="noreferrer" target="_blank">http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/</a><br>
> )<br>
<br>
You might not have to, if you only care about the imported VMs from your<br>
storage. This will not keep other configuration, such as users/roles/permissions<br>
etc.<br>
<br>
> - Can I directly install hosted-engine 4.0 and then import the storage<br>
> domain? Or should I install same hosted-engine version?<br>
<br>
AFAIK 4.0 engine can import 3.6 storage domains without problem.<br>
<br>
> - Do I first need another master storage domain or can I directly import my<br>
> old master storage domain?<br>
<br>
No idea. Even if you do, you can create a small empty one and later remove it.<br>
<br>
> - When importing the storage domain what is the risk it fails ( I have<br>
> backups, but it would cost a day to restore all )<br>
<br>
No idea, but IIRC we got many successful reports and at most few failures<br>
for this.<br>
<br>
> - How long would import take? few minutes or hours? ( I want to keep down<br>
> time as low as possible ).<br>
<br>
Again no idea. Perhaps do some test?<br>
<br>
><br>
> Another option would be upgrade the OS ( with redhat-upgrade-tool ) or is<br>
> this a path for disaster?<br>
<br>
Didn't work for us well, so we decided to not support it. If you decide to try,<br>
make sure you test carefully beforehand. From ovirt's POV:<br>
1. You'll need to handle postgresql upgrade.<br>
2. Right after OS upgrade, you'll still have (I think) el6 packages<br>
of the engine. It will hopefully be in a good-enough state for upgrade<br>
to 4.0, but we didn't test this.<br>
3. Specifically, if upgrade fails, rollback will most likely not work,<br>
so you'll have to manually handle this - take a full vm backup and make<br>
sure you can restore it.<br>
<br>
><br>
> I hope someone can tell me how I can smoothly upgrade my hosted-engine up to<br>
> el7 and run oVirt 4.<br>
<br>
We are working on a tool/wizard to help with this process. It used to work,<br>
but at some point it was decided that one of the actions it does is risky<br>
and was blocked, thus the tool is broken currently.<br>
<br>
You can invoke the tool by running: 'hosted-engine --upgrade-appliance'.<br>
As noted above, this is currently broken.<br>
<br>
There are several open bugs about it, e.g.:<br>
<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1319457" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1319457</a><br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1343425" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1343425</a><br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1343593" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1343593</a> (closed, this is<br>
what broke the tool)<br>
<br>
Basically, you can manually do what the tool is supposed to do:<br>
1. Make sure state is clean and stable (no running/pending storage actions,<br>
no VMs in the middle of migration etc), all clusters are compat level 3.6, etc.<br>
2. Move to global maintenance<br>
3. backup the engine using engine-backup and keep the backup elsewhere<br>
4. Reinstall engine vm with el7 and 4.0 engine (the tool will use the engine<br>
appliance, you might too but not sure how exactly).<br>
5. Restore the backup and run engine-setup.<br>
6. If all looks ok, leave global maintenance.<br>
<br>
If you manually keep a full backup of the engine vm before step 4,<br>
you might be able to restore this backup if there are problems.<br>
Doing this in the provided tool is currently the main blocking issue<br>
for it. Hopefully will be provided in 4.0.1.<br>
<br>
Best,<br>
--<br>
Didi<br>
</blockquote></div></div>