<div dir="ltr"><div class="gmail_quote"><div class="GmSign"><br><br></div><div dir="ltr">Op do 30 jun. 2016 om 21:17 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 Thu, Jun 30, 2016 at 9:46 PM, Paul Groeneweg | Pazion <<a href="mailto:paul@pazion.nl" target="_blank">paul@pazion.nl</a>> wrote:<br>
> Things are getting more clear to me, thanks!<br>
> And this whole upgrade is something I should prepare well and not try to do<br>
> in a few hours at night :)<br>
><br>
> Resuming, there are multiple solutions:<br>
><br>
> 1. upgrade el6 to el7<br>
> no go => I need to upgrade postgresql and redhat warns about upgrading 6.6<br>
> to 7 because of newer packages<br>
> 2. install a new HE on new Host new storage domain<br>
> a lot of work => I have to turn off VMs, import storage domain into new<br>
> setup and reinstall hosts.<br>
> 3. install a new HE on new Host existing storage domain<br>
> possibly not without issues => I have to manually update references to the<br>
> hosted storage or better wait till there is an upgrade tool.<br>
> 4. (re)install HE in current VMS container.<br>
> => I can keep my Hosts and reference to the storage domain.<br>
><br>
> So I guess my best bet is to go for option 4.<br>
><br>
> The flow I am planning to follow would be:<br>
><br>
> 1. Move to global maintenance ( keep VMs running )<br>
> 2. backup ( I have also a complete disk install of old hosted-engine )<br>
> 3. reboot with different conf, to boot from cd<br>
> 4. acces console and run install + import the backup in the engine vm<br>
> ? 5. run engine-setup to configure new install with engine restore data<br>
> 6. reboot hosted-engine<br>
> 7. Remove from global maintenance<br>
> 8. launch web gui and I should be able to manage all still running VMs<br>
> again.<br>
><br>
> Would above be working or am I missing something and I doubt step 5. Is<br>
> this needed?<br>
<br>
Yes.<br>
<br>
In a normal backup/restore flow, it's less important, although officially<br>
it's mandatory. But in above flow, it's not just backup/restore, but also<br>
upgrade from 3.6 to 4.0.<br>
<br>
In principle you can also do all of the above with 3.6, at least inside<br>
the engine, verify that all seems good, then upgrade to 4.0 later. See<br>
also:<br>
<br>
<a href="https://bugzilla.redhat.com/1332463" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1332463</a><br>
<br>
But I do not remember reports from people trying it.<br>
<br></blockquote><div>Good point, I planned to first get 3.6 running on el7 and from there upgrade hosted-engine to 4.0 ( between step 6 and 7 ). Altough this way I keep old 3.6 files on my fresh installl...what would you advice? directly install 4.0 on new el7 host? ( I am running 3.6.7, so above bug is probably fixed ).</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
One very important thing you did not mention: Try this on a test system,<br>
including rollback to your backup, after you finished everything and<br>
(supposedly) found out something broken. Better safe than sorry :-)<br></blockquote><div><br></div><div>A test setup might provide a good practice. But requires extra spare hosts...<span style="line-height:1.5">I do have a bare metal restore option. So I am able ( </span><span style="line-height:1.5">with cd boot and console mode</span><span style="line-height:1.5">) to restore hosted engine within an hour to previous state :-)</span></div><div><br></div><div>Thanks a lot for all info!</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Best,<br>
<br>
><br>
> Best Regards,<br>
> Paul<br>
><br>
><br>
><br>
> Op do 30 jun. 2016 om 14:44 schreef Simone Tiraboschi <<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>>:<br>
>><br>
>> On Thu, Jun 30, 2016 at 8:34 AM, Paul Groeneweg | Pazion <<a href="mailto:paul@pazion.nl" target="_blank">paul@pazion.nl</a>><br>
>> wrote:<br>
>> > Hi Yedidyah,<br>
>> ><br>
>> > Thank you for the comprehensive answers.<br>
>> ><br>
>> > I think I go for a complete reinstall ( read also OS upgrade tool is not<br>
>> > adviced on 6.6 or higher as there might be newer packages as on 7 ). No<br>
>> > doubting to re-use current VM or setup from scratch ( fresh host with<br>
>> > new<br>
>> > hosted-engine and existing storage domein ).<br>
>><br>
>> If you are planning to redeploy hosted-engien from scratch and<br>
>> restoring on the new engine DB a backup of the previous one, please<br>
>> carefully consider this:<br>
>> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21</a><br>
>><br>
>> So, if you choose that path you'll have also to manually remove any<br>
>> reference to the previous hosted-engine from the restored DB.<br>
>> I'd strongly suggest you to wait for the upgrade tool to be fixed<br>
>> since manually doing this upgrade can be really error prone.<br>
>><br>
>> > You explain the steps ( 1 to 6 ), but then don't talk about storage<br>
>> > domain<br>
>> > import.<br>
>> > Does it mean, when I reinstall the hosted-engine in the current he VM<br>
>> > and<br>
>> > restore an engine-backup ( step 5 ) I am able to start vm from Host and<br>
>> > it<br>
>> > is still connected to the master storage ( so no need for storage<br>
>> > import) ?<br>
>> ><br>
>> > Best Regards,<br>
>> > Paul Groeneweg<br>
>> ><br>
>> ><br>
>> > Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David<br>
>> > <<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>>:<br>
>> >><br>
>> >> 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<br>
>> >> > 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>
>> >> ><br>
>> >> ><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<br>
>> >> > 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<br>
>> >> > my<br>
>> >> > storage domain to the new hosted engine, but:<br>
>> >> ><br>
>> >> > - Do I need to restore my hosted engine database? ( like described<br>
>> >> > here:<br>
>> >> ><br>
>> >> ><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<br>
>> >> your<br>
>> >> storage. This will not keep other configuration, such as<br>
>> >> users/roles/permissions<br>
>> >> etc.<br>
>> >><br>
>> >> > - Can I directly install hosted-engine 4.0 and then import the<br>
>> >> > 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<br>
>> >> > import<br>
>> >> > my<br>
>> >> > old master storage domain?<br>
>> >><br>
>> >> No idea. Even if you do, you can create a small empty one and later<br>
>> >> remove<br>
>> >> it.<br>
>> >><br>
>> >> > - When importing the storage domain what is the risk it fails ( I<br>
>> >> > 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<br>
>> >> failures<br>
>> >> for this.<br>
>> >><br>
>> >> > - How long would import take? few minutes or hours? ( I want to keep<br>
>> >> > 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 )<br>
>> >> > or<br>
>> >> > 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<br>
>> >> to<br>
>> >> 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<br>
>> >> > hosted-engine<br>
>> >> > 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<br>
>> >> work,<br>
>> >> but at some point it was decided that one of the actions it does is<br>
>> >> risky<br>
>> >> and was blocked, thus the tool is broken currently.<br>
>> >><br>
>> >> You can invoke the tool by running: 'hosted-engine<br>
>> >> --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<br>
>> >> actions,<br>
>> >> no VMs in the middle of migration etc), all clusters are compat level<br>
>> >> 3.6,<br>
>> >> 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<br>
>> >> 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>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Users mailing list<br>
>> > <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
>> > <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
>> ><br>
<br>
<br>
<br>
--<br>
Didi<br>
</blockquote></div></div>