<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 19, 2016 at 8:11 PM, Scott <span dir="ltr"><<a href="mailto:romracer@gmail.com" target="_blank">romracer@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hi Sandvik,</p>
<p dir="ltr">I believe this ultimately is what the self hosted engine is planned to solve. It's up to you as to whether you feel comfortable with that idea currently.</p></blockquote><div><br></div><div>Indeed. And many in the community are using it.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr"> </p>
<p dir="ltr">Outside of that, I would point you to the Red Hat Cluster Suite in a RHEV/RHEL environment. The high availability component of that is based on Linux-HA but I have only used Red Hat's implementation.</p>
<p dir="ltr">Lastly, the poor man's solution if this isn't critical infrastructure would be a hot standby server. Keep the packages in sync between the two however you feel appropriate. Run engine-backup as frequently as needed and copy it to the second server. Have your engine address as a secondary address with appropriate DNS and move it between them in a fail over (or use a CNAME). Restore the backup in a fail over and run engine-setup. I think you get the idea.</p></blockquote><div><br></div><div>I don't like this approach very much - you always forget some configuration. (For example, we've had an issue with Kerberos database later on when migrating).</div><div>You are also 'wasting' a server. </div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr"> </p>
<p dir="ltr">Personally I use hosted engine in all but my main production cluster. That one will use it once I've upgraded those hosts to RHEL 7.</p>
<p dir="ltr">Hope that helps. </p>
<p dir="ltr">Scott</p>
<br><div class="gmail_quote"><div><div class="h5"><div dir="ltr">On Fri, Aug 19, 2016, 11:40 AM Sandvik Agustin <<a href="mailto:agustinsandvik@gmail.com" target="_blank">agustinsandvik@gmail.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hi Ovirt Users,<div><br></div><div>Do you have any documentation, tutorial, howto or workaround to perform or to have an ovirt-engine HA? Iv'e tried to google about this but I can't find any.</div><div><br></div><div>let's say I want to have two engine, engine1 is currently managing two hypervisor, then engin2 is my reserved engine, so I can still managed those vm that are running inside of my hypervisor if ever engine1 fails.</div><div><br></div><div>TIA :)</div><div>Sandvik</div></div></div></div>
______________________________<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/<wbr>mailman/listinfo/users</a><br>
</blockquote></div>
<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></blockquote></div><br></div></div>