> On 28 Feb 2015, at 6:00 am, Покотиленко Костик wrote:
>
> В Чтв, 22/01/2015 в 14:59 +1100, Andrew Beekhof пишет:
>>> On 15 Jan 2015, at 12:54 am, Покотиленко Костик wrote:
>>>
>>> В Вто, 06/01/2015 в 16:27 +1100, Andrew Beekhof пишет:
> On 20 Dec 2014, at 6:21 am, Покотиленко Костик
>>
В Чтв, 22/01/2015 в 14:59 +1100, Andrew Beekhof пишет:
> > On 15 Jan 2015, at 12:54 am, Покотиленко Костик wrote:
> >
> > В Вто, 06/01/2015 в 16:27 +1100, Andrew Beekhof пишет:
> >>> On 20 Dec 2014, at 6:21 am, Покотиленко Костик
> >>> wrote:
> >>> Here are behaviors of different versions of pa
Andrew Beekhof writes:
>>> you'll want a recurring monitor with role=Stopped
>>>
>>
>> How is it done?
>
> I don't know the crmsh syntax. Sorry
>
>>
>> I've tried on 1.1.12 with:
>> primitive Nginx lsb:nginx \
>> op monitor interval=2s \
>> op monitor interval=3s role=Stopped
>>
>>
> On 15 Jan 2015, at 12:54 am, Покотиленко Костик wrote:
>
> В Вто, 06/01/2015 в 16:27 +1100, Andrew Beekhof пишет:
>>> On 20 Dec 2014, at 6:21 am, Покотиленко Костик wrote:
>>> Here are behaviors of different versions of pacemaker:
>>>
>>> 1.1.12:
>>>
>>> - stopping nginx on a node always ma
> On 20 Dec 2014, at 6:21 am, Покотиленко Костик wrote:
>
> Hi,
>
> Simple scenario, several floating IPs should be living on "front" nodes
> only if there is working Nginx. There are several reasons against Nginx
> being controlled by Pacemaker.
>
> So, decided to colocate FIPs with unmanaged
Hi,
Simple scenario, several floating IPs should be living on "front" nodes
only if there is working Nginx. There are several reasons against Nginx
being controlled by Pacemaker.
So, decided to colocate FIPs with unmanaged Nginx. This worked fine in
1.1.6 with some exceptions.
Later, on other cl
