On 01/18/2017 03:49 AM, Ferenc Wágner wrote:
> Ken Gaillot writes:
>
>> * When you move the VM, the cluster detects that it is not running on
>> the node you told it to keep it running on. Because there is no
>> "Stopped" monitor, the cluster doesn't immediately realize that
Ken Gaillot writes:
> * When you move the VM, the cluster detects that it is not running on
> the node you told it to keep it running on. Because there is no
> "Stopped" monitor, the cluster doesn't immediately realize that a new
> rogue instance is running on another node.
On 01/17/2017 10:05 AM, Oscar Segarra wrote:
> Hi,
>
> * It is also possible to configure a monitor to ensure that the resource
> is not running on nodes where it's not supposed to be (a monitor with
> role="Stopped"). You don't have one of these (which is fine, and common).
>
> Can you provide
Hi,
* It is also possible to configure a monitor to ensure that the resource
is not running on nodes where it's not supposed to be (a monitor with
role="Stopped"). You don't have one of these (which is fine, and common).
Can you provide more information/documentation about role="Stopped"
And,
On 01/17/2017 08:52 AM, Ulrich Windl wrote:
Oscar Segarra schrieb am 17.01.2017 um 10:15 in
> Nachricht
> :
>> Hi,
>>
>> Yes, I will try to explain myself better.
>>
>> *Initially*
>> On node1
. Januar 2017 15:53
An: users@clusterlabs.org
Betreff: [ClusterLabs] Antw: Re: VirtualDomain started in two hosts
>>> Oscar Segarra <oscar.sega...@gmail.com> schrieb am 17.01.2017 um
>>> 10:15 in
Nachricht
<cajq8tag8vhx5j1xqpqmrq-9omfnxkhqs54mbzz491_6df9a...@mail.gm
>>> Oscar Segarra schrieb am 17.01.2017 um 10:15 in
Nachricht
:
> Hi,
>
> Yes, I will try to explain myself better.
>
> *Initially*
> On node1 (vdicnode01-priv)
>>virsh list
> ==
> vdicdb01