<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 12, 2017 at 7:57 AM, Yedidyah Bar David <span dir="ltr"><<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On Fri, Mar 10, 2017 at 3:43 PM, Devin A. Bougie<br>
<<a href="mailto:devin.bougie@cornell.edu">devin.bougie@cornell.edu</a>> wrote:<br>
> Hi, All. We have an ovirt 4.1 cluster setup using multiple paths to a single iSCSI LUN for the data storage domain. I would now like to migrate to a hosted engine.<br>
><br>
> I setup the new engine VM, shutdown and backed-up the old VM, and restored to the new VM using engine-backup. After updating DNS to change our engine's FQDN to point to the hosted engine, everything seems to work properly. However, when rebooting the entire cluster, the engine VM doesn't come up automatically.<br>
<br>
</span>I am aware that the above flow is technically possible - nothing stops<br>
you from doing it - but it's not the standard/supported/expected way<br>
to deploy a hosted-engine. You must use 'hosted-engine --deploy' for<br>
that.<br>
Nice try, though :-) Will be an interesting exercise to try and<br>
convert this to a fully-functioning hosted-engine, but I'd personally<br>
not try that on a production system.<br></blockquote><div><br></div><div>On the hosted-engine storage domain we have also the lockspace, metadata and configuration volumes.</div><div>They are created at setup time by ovirt-hosted-engine-setup</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class="gmail-"><br>
><br>
> Is there anything that now needs to be done to tell the cluster that it's now using a hosted engine?<br>
<br>
</span>Yes, but it's currently not possible to do this after the fact.<br>
<span class="gmail-"><br>
><br>
> I started with a standard engine setup, as I didn't see a way to specify multiple paths to a single iSCSI LUN when using "hosted-engine --deploy."<br>
<br>
</span>I think it's indeed not fully-supported yet [1], but can be done<br>
manually [2][3].<br>
<br>
Simone - are there updates for this? Perhaps we should add this to the<br>
hosted-engine howto page.<br>
<br>
[1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1193961" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1193961</a><br>
[2] <a href="http://lists.ovirt.org/pipermail/users/2015-March/032034.html" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>pipermail/users/2015-March/<wbr>032034.html</a><br>
[3] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1193961#c2" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1193961#c2</a><br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br></div></div></blockquote><div><br></div><div>Here we have two distinct things:</div><div>- use multiple iSCSI initiators on the host; the best way to achieve this is configuring an iSCSI bond from the engine once it's running. See 'Configuring iSCSI Multipathing' section on <a href="http://www.ovirt.org/documentation/admin-guide/chap-Storage/">http://www.ovirt.org/documentation/admin-guide/chap-Storage/</a></div><div>- get multipath connecting to multiple targets on the same SAN: this is currently not supported by hosted-engine-setup and ovirt-ha-agent</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5">
><br>
> Any tips would be greatly appreciated.<br>
><br>
> Many thanks,<br>
> Devin<br>
> ______________________________<wbr>_________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br>
<br>
<br>
</div></div><span class="gmail-HOEnZb"><font color="#888888">--<br>
Didi<br>
</font></span></blockquote></div><br></div></div>