Re: [ovirt-users] Ovirt resilience policy / HA

2015-03-18 Thread Guillaume Penin

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 
 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


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Ovirt resilience policy / HA

2015-03-18 Thread Guillaume Penin

Le 2015-03-18 11:18, Omer Frenkel a écrit :

- Original Message -

From: "Guillaume Penin" 
To: users@ovirt.org
Sent: Monday, March 16, 2015 10:34:54 PM
Subject: [ovirt-users] Ovirt resilience policy / HA

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

?



there are 2 types of host failure:
1 - power/network/vdsm service.. - these leads to a state where engine
and host cannot communicate, host will move to 'non-responsive' and
will be fenced (power mgmt action)
in this case, only HA vms will be restarted, once the engine is sure it 
is safe.


2 - software issues like storage connectivity - in this case, engine
can communicate with the host, and decide it is not fulfilling the
cluster/dc requirements
the host will move to 'not operational' then the engine will
live-migrate (not restart) vms according to your choice of resilience
policy

so what did you do when you tested 'host failure'?
according to your question i assume number 1, and this is what you got

let me know if it helps
Omer.


Hi Omer,

Indeed, I only tested the "Non responsive" scenario with a power 
failure. The host was fenced and only HA VMs were restarted which was, 
as you said, the correct behaviour in this case.


I've just tested the "Not operational" scenario by "ifdowning" a network 
interface. Resilience policy was configured to "Migrate Virtual 
Machines" and as expected, all VMs have been migrated to another host.


Thank you very much for that clarification.


Kind regards,
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Ovirt resilience policy / HA

2015-03-18 Thread Omer Frenkel


- Original Message -
> From: "Guillaume Penin" 
> To: users@ovirt.org
> Sent: Monday, March 16, 2015 10:34:54 PM
> Subject: [ovirt-users] Ovirt resilience policy / HA
> 
> 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
> ?
>

there are 2 types of host failure:
1 - power/network/vdsm service.. - these leads to a state where engine and host 
cannot communicate, host will move to 'non-responsive' and will be fenced 
(power mgmt action)
in this case, only HA vms will be restarted, once the engine is sure it is safe.

2 - software issues like storage connectivity - in this case, engine can 
communicate with the host, and decide it is not fulfilling the cluster/dc 
requirements
the host will move to 'not operational' then the engine will live-migrate (not 
restart) vms according to your choice of resilience policy 

so what did you do when you tested 'host failure'?
according to your question i assume number 1, and this is what you got

let me know if it helps
Omer.

> Kind regards,
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Ovirt resilience policy / HA

2015-03-16 Thread Guillaume Penin

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