Hi Darell, Sorry for my late reply. I've been able to test the 2 different scenarios : - Host not responding => Host fenced => HA VMs restarted on another Host. - Host not operational => Host not fenced, resilience policy configured to "Migrate Virtual Machines" => All VMs migrated to another Host. Thank you very much for your answer. Kind regards, Le 2015-03-17 14:59, Darrell Budic a écrit :
Resilience policy refers to migration behavior only. if VDSM on a host node detects a storage or network problem, for instance, it will migrate All, HA, or no VMs to a new node.
Sounds like you’re thinking in terms of “I want Ovirt to restart these VMs if the host dies”, for that, set HA on the VMs you want it to restart if the VM dies for whatever reason.
On Mar 16, 2015, at 3:34 PM, Guillaume Penin <guillaume@onlineacid.com> wrote:
Hi all,
I'm building a test ovirt (3.5.1) infrastructure, based on 3 ovirt nodes and 1 ovirt engine.
Everything runs (almost) fine, but i don't exactly understand the interaction between resilience policy (Cluster) and HA (VM).
=> What I understand, in case of host failure :
- Setting resilience policy to :
- Migrate Virtual Machines => All VMs (HA and non HA) will be started on another host. - Migrate only Highly Available Virtual Machines => HA VMs only will be started on another host. - Do Not Migrate Virtual Machines => HA and non HA VMs won't be started on another host.
=> In practice :
- No matter what parameter i use in resilience policy, HA VMs only will be started on another host in case of a host failure.
Is this the expected behaviour ? Am I misunderstanding the way it works ?
Kind regards, _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users