On Fri, May 31, 2019 at 11:35 AM <raul.caballero.girol@gmail.com> wrote:

> On Fri, May 31, 2019 at 10:46 AM <raul.caballero.girol(a)gmail.com> wrote:
>
>
>
> You cannot create a VM lease for the hosted-engine VM because the
> hosted-engine VM is always already protected by a volume lease.
Sorry, I don't understand this. If the storage when is placed my manager down, it will startup in other storage?

HA mechanism for the engine VM is provided by ovirt-ha-agent service running on all the hosted-engine configured hosts (at least a couple on each site).

The hosted-engine configured hosts communicate via a whiteboard wrote on the hosted-engine storage domain so, if the storage devices on the two sites are in sync (it requires latency < 7ms), all the hosted-engine host can also see the status on the other site and eventually take over.

The volume lease is there to enforce, at storage level, that only one host at a time is able to run the engine VM (regardless of the site where is it since also the lock is in sync).

>
>
> Did you read
> https://ovirt.org/documentation/disaster-recovery-guide/active_active_ove...
> ?
Yes, and it's only say "Configure all virtual machines that need to failover as highly available, and ensure that the virtual machine has a lease on the target storage domain."
But the manager, It's configured for HA storage by default?. I have made a lab with 1 host and 2 storage domain replicated and, when I pull down the engine storage, It don't start up again.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/DMZYJB33D5KI5NHJFKCJ4SDNXFMHYST3/

Simone Tiraboschi

He / Him / His

Principal Software Engineer

Red Hat

stirabos@redhat.com

@redhatjobs redhatjobs @redhatjobs