On Wed, Jun 10, 2020 at 11:29 AM Joseph Goldman <joseph@goldman.id.au> wrote:

As the other response alluded to - proper HA ovirt engine is a hosted VM ovirt-engine.

But the way oVirt is designed is that it just pushes configuration to the hosts - if your ovirt-engine dies, redeploying from backup should be fairly quick and painless - just some features may be unavailable like hot migrate etc, but importantly your existing VM's will continue to run as they were until you can re-deploy your engine.

If you are worried about performance and resources - you could simply create a new cluster for just Hosted Engine stuff and deploy it there, so 2 servers in HA for engine separate from the rest of your VM clusters.

On 10/06/2020 4:20 pm, Vijay Sachdeva via Users wrote:

Hi All,

Is there a documentation on creating Ovirt-Manager in HA or is it possible to make the manager to run in HA environment. Since it seems to be a single point of failure..!!

In addition to what others (correctly) said, we heard also of a few setups using pacemaker etc. on bare-metal hosts for the engine. I'd say, if you or your team are comfortable with pacemaker, have conf/processes/experience around it, and can spare the extra hardware and rack space, it might be a valid option. Biggest con of ovirt-hosted-engine-ha, IMO, is the rather bad feeling some people have about having less control on the disk image, etc., what to do when it dies, how to debug/fix issues. Of course, if you are very experienced with oVirt's HA, know how to debug/fix corrupt disk images, VM boot problems, etc., and have no experience with pacemaker, oVirt HA will be better for you. In any case, for important setups, keep good backups (and test them routinely!). Best regards, -- Didi