If you deployed with wizard the hosted engine should already be HA and can
run on any host. I’d you look at GUI you will see a crown beside each host
that is capable of running the hostess engine.

On Sat, Mar 20, 2021 at 5:14 PM David White via Users <users@ovirt.org>
wrote:

> I just finished deploying oVirt 4.4.5 onto a 3-node hyperconverged cluster
> running on Red Hat 8.3 OS.
>
> Over the course of the setup, I noticed that I had to setup the storage
> for the engine separately from the gluster bricks.
>
> It looks like the engine was installed onto /rhev/data-center/ on the
> first host, whereas the gluster bricks for all 3 hosts are on
> /gluster_bricks/.
>
> I fear that I may already know the answer to this, but:
> Is it possible to make the engine highly available?
>
> Also, thinking hypothetically here, what would happen to my VMs that are
> physically on the first server, if the first server crashed? The engine is
> what handles the high availability, correct? So what if a VM was running on
> the first host? There would be nothing to automatically "move" it to one of
> the remaining healthy hosts.
>
> Or am I misunderstanding something here?
>
>
> Sent with ProtonMail <https://protonmail.com> Secure Email.
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/L6MMZSMSGIK7BTUSUECU65VZRMS4N33L/
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Q2KHQ4XA4H2FZ3C73CAYES3IOXI7YWTV/

Reply via email to