[ovirt-users] ovirt engine HA
Vincent Royer
vincent at epicenergy.ca
Tue Apr 3 05:01:34 UTC 2018
Same thing, the engine in this case is "self-hosted", as in, it runs in a
VM hosted on the cluster that it is managing. I am a beginner here, but
from my understanding, each node is always checking on the health of the
engine VM. If the engine is missing (ie, the host running it has gone
down), then another available, healthy host will spawn up the engine and
you will regain access.
In my experience this has worked very reliably. I have 2 hosts, both are
"able" to run the engine VM. If I take one host down, I am not able to
load the engine GUI. But if I wait a few minutes, then I regain access,
and see that the engine is now running on the remaining healthy host.
*Vincent Royer*
*778-825-1057*
<http://www.epicenergy.ca/>
*SUSTAINABLE MOBILE ENERGY SOLUTIONS*
On Mon, Apr 2, 2018 at 6:07 PM, <dhy336 at sina.com> wrote:
> what different between self-hosted engine and hosted engine? I find a
> project ovirt-hosted-engine-ha
> <https://github.com/oVirt/ovirt-hosted-engine-ha> https:
> //github.com/oVirt/ovirt-hosted-engine-ha
> ----- 原始邮件 -----
> 发件人:Vincent Royer <vincent at epicenergy.ca>
> 收件人:dhy336 at sina.com
> 抄送人:users <users at ovirt.org>
> 主题:Re: [ovirt-users] ovirt engine HA
> 日期:2018年04月03日 08点57分
>
> If your node running self-hosted engine crashes, the hosted engine will be
> started up on another node. It just takes a few minutes for this all to
> happen, but it works reliably in my experience.
>
>
>
> On Mon, Apr 2, 2018 at 5:42 PM, <dhy336 at sina.com> wrote:
>
> How to solute ovirt engine HA, I have a three node cluster, one of is
> deploy engine and node , others are node, if node that deplay engine and
> node crash, How to ensure my server is up?
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180402/b36da6de/attachment.html>
More information about the Users
mailing list