<div dir="ltr">I believe that is the required setup - dedicated storage domain for HE. It's certainly the case on 4.0, I haven't played with 4.1 yet.<div><br></div><div>For docs you can always check the RHV set, they are generally applicable to oVirt.</div><div><br></div><div><a href="https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1-beta/html/self-hosted_engine_guide/" target="_blank">https://access.redhat.com/<wbr>documentation/en-us/red_hat_<wbr>virtualization/4.1-beta/html/<wbr>self-hosted_engine_guide/</a><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 30 March 2017 at 18:17, Charles Tassell <span dir="ltr"><<a href="mailto:charles@islandadmin.ca" target="_blank">charles@islandadmin.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
Are there any more recent install docs than what's on the website? Those all seem to be back from the 3.x days and don't really deal with the modern setup of using a hosted engine.<br>
<br>
More specifically, I've noticed that when deploying a hosted engine I can't import the storage domain that the engine is on. When I try I get errors like "Can't import the storage domain, connection already exists" Because I can't import my storage domain, I can't initialize the cluster, so I can't really get anywhere with the setup. I had this same problem on 4.0 (using 4.1 now) and I "fixed" it by wiping the cluster and creating two sets of storage: a small 50G one that holds the hosted engine, and then another one that holds all my VMs. I don't want to do that with my new cluster if I can at all avoid it.<br>
<br>
<br>
______________________________<wbr>_________________<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<wbr>/listinfo/users</a><br>
</blockquote></div><br></div>