<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 8, 2017 at 9:50 PM, Matt Simonsen <span dir="ltr"><<a href="mailto:matt@khoza.com" target="_blank">matt@khoza.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">Hello all,<br>
<br>
I read with Gluster using hyper-convergence that the engine must reside on the same LAN as the nodes. I guess this makes sense by definition - ie: using Gluster storage and replicating Gluster bricks across the web sounds awful.<br>
<br>
This got me wondering about best practices for the engine setup. We have multiple physical locations (co-location data centers).<br>
<br>
In my initial plan I had expected to have my oVirt engine hosted separately from each physical location so that in the event of trouble at a remote facility the engine would still be usable.<br>
<br>
In this case, our prod sites would not have a "hyper-converged" setup if we decide to run GlusterFS for storage at any particular physical site, but I believe it would still be possible to use Gluster. In this case oVirt would have a 3 node cluster, using GlusterFS storage, but not hyper-converged since the engine would be in a separate facility.<br>
<br>
Is there any downside in this setup to having the engine off-site?<br></blockquote><br>This is called a stretched cluster setup. You have pro and cons, for instance host fencing could become problematic.</div><div class="gmail_quote">VM leases could help: <a href="https://ovirt.org/develop/release-management/features/storage/vm-leases/">https://ovirt.org/develop/release-management/features/storage/vm-leases/</a></div><div class="gmail_quote"><br><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Rather than having an off-site engine, should I consider one engine per physical co-location space?<br></blockquote><div><br></div><div>This would be simpler but you are going to loose a few capabilities that can be relevant in a disaster recovery scenario.</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">
<br>
Thank you all for any feedback,<br>
<br>
Matt<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></div>