Hi,

I checked the self-hosted doc and I see that High-Availability is provided by additional "self-hosted" capable hosts and a dedicated shared Storage Domain to store the engine VM.

What about the "upgrade-gone-wrong" case ?

I mean, before any important upgrade of any VM, we take a snapshot and revert to it if required.

We had a similar case when upgrading the engine from 4.3 to 4.4, where a mismatched cluster CPU type prevented starting VMs.
We were even working with two different engine VMs rather than snapshots because 4.3 was on OL7 et 4.4 is on OL8.
We had to revert for a while to the 4.3 engine waiting for the fix.

What's the plan w/ a self-hosted engine ?

Laurent Duparchy

ESRF - The European Synchrotron
MIS Unit
04 76 88 22 56

Michal Skrivanek wrote on 04/11/2022 15:43:

On 4. 11. 2022, at 15:03, duparchy@esrf.fr wrote:

Thanks for your reply

with oVirt or elsewhere?

That was with XEN,  OCFS2 cluster context, which is more prone to instabilities.
Anyway, loosing the manager/engine when things start going wrong is just worsening the situation.

Yes, but oVirt does that quite differently. Despite the challenges around deployment I believe it's a way safer solution than trying to run this independently/manually.

Thanks,
michal

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/MR72VXWOPYNSNKBT2DUCKRYUOQWGHMTJ/