<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 11 November 2015 at 12:52, Simone Tiraboschi <span dir="ltr"><<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Nov 11, 2015 at 6:01 PM, Alastair Neil <span dir="ltr"><<a href="mailto:ajneil.tech@gmail.com" target="_blank">ajneil.tech@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi <div><br></div><div>I am in the process of upgrading my ovirt DC to 3.6. I would like to migrate to hosted-engine with gluster replica 3 storage in the process. The engine has been upgraded and I have installed 3 of the VM hosts in one cluster using the ovirt-node iso. I have three other VM hosts in a separate cluster to upgrade. </div><div><br></div><div>I see an option to configure the hosted engine through the node admin login tui, however I have not found any up to date instructions on how to perform a migration to hosted using the ovirt-node. I thought I'd ask a few questions before I started:</div><div><br></div><div>Should I connect and approve the node in the current engine prior to configuring the hosted engine?</div><div>Does the node hosted-engine-setup provide a pause to restore the engine db from the external engine? Or even better a facility to upload the database backup file?</div></div></blockquote><div><br></div></span><div><a href="http://www.ovirt.org/Migrate_to_Hosted_Engine" target="_blank">http://www.ovirt.org/Migrate_to_Hosted_Engine</a></div></div></div></div></blockquote><div><br></div><div>Yes I am familiar with these instructions, however they are quite old and have not been updated to include any information about how to perform this in the case of using the 3.6 ovirt-node image as the host and the ovirt-live installation image as the VM installation.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>hosted-engine-setup has to be run on the host.</div><div>engine-setup has to be run on the engine VM.</div><div>The DB restore from you previous setup has to be performed on the engine VM. If you are using the ready to use oVirt engine appliance and you choose to automatically execute engine-setup on your VM it will not wait for you to replace the engine DB so you have just to avoid that and manually execute engine-setup on the engine VM. </div></div></div></div></blockquote><div> </div><div>This is the crux: if the hosted-engine-setup using the live image allows you to pause the setup and do a manual engine-setup. Its seems like it is probably a quite common thing for people to want to do so I thought I'd check. If it has not been attempted and/or documented then I will try it.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>In this way you have all the time to perform your import.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><div dir="ltr"><div><br></div><div>Any feedback gratefully received.</div><div><br></div><div>Thanks, Alastair</div><div><br></div></div>
<br></span>_______________________________________________<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></blockquote></div><br></div></div>
</blockquote></div><br></div></div>