On 1 Aug 2014, at 2:04 pm, Andrew Beekhof wrote:
>
> On 1 Aug 2014, at 7:47 am, Andrew Beekhof wrote:
>
>>
>> On 31 Jul 2014, at 4:46 pm, Cédric Dufour - Idiap Research Institute
>> wrote:
>>
>>> On 31/07/14 00:17, Andrew Beekhof wrote:
On 31 Jul 2014, at 2:48 am, Cédric Dufour - Idi
On 1 Aug 2014, at 7:47 am, Andrew Beekhof wrote:
>
> On 31 Jul 2014, at 4:46 pm, Cédric Dufour - Idiap Research Institute
> wrote:
>
>> On 31/07/14 00:17, Andrew Beekhof wrote:
>>> On 31 Jul 2014, at 2:48 am, Cédric Dufour - Idiap Research Institute
>>> wrote:
>>>
After packaging pac
On 31 Jul 2014, at 4:46 pm, Cédric Dufour - Idiap Research Institute
wrote:
> On 31/07/14 00:17, Andrew Beekhof wrote:
>> On 31 Jul 2014, at 2:48 am, Cédric Dufour - Idiap Research Institute
>> wrote:
>>
>>> After packaging pacemaker 1.1.12 for Debian/Wheezy (along corosync 1.4.6
>>> and li
On 31 Jul 2014, at 6:05 pm, philipp.achmuel...@arz.at wrote:
> hi,
>
> is it possible to set up different move types for VM?
>
> - infinity colocation with pingd-clone -> when failing on one node, live
> migrate VM(s) to remaining nodes
> - infinity colocation to LVM-clone -> when failing o
On 31 Jul 2014, at 8:20 pm, Liron Amitzi wrote:
>>> When I run "service pacemaker stop" it takes a long time, I see that it
>>> stops all the resources, then starts them on the other node, and only then
>>> the "stop" command is completed.
>>
>> Ahhh! It was the DC.
>>
>> It appears to be de
>> When I run "service pacemaker stop" it takes a long time, I see that it
>> stops all the resources, then starts them on the other node, and only then
>> the "stop" command is completed.
>
>Ahhh! It was the DC.
>
>It appears to be deliberate, I found this commit from 2008 where the behaviour
>
hi,
is it possible to set up different move types for VM?
- infinity colocation with pingd-clone -> when failing on one node, live
migrate VM(s) to remaining nodes
- infinity colocation to LVM-clone -> when failing on one node, cold
migration (stop/restart) VM(s) on remaining nodes
thank you!
