[Pacemaker] a question on the `ping` RA

Riccardo Murri riccardo.murri at gmail.com
Mon Jun 2 05:05:22 EDT 2014

Hi Andrew,

thanks for your explanations.  One more question:

On 30 May 2014 02:38, Andrew Beekhof <andrew at beekhof.net> wrote:
> On 29 May 2014, at 9:19 pm, Riccardo Murri <riccardo.murri at gmail.com> wrote:
>> - or rather does the `ping` RA trigger failure events when even one of
>>  the nodes cannot be pinged?
> both.  it always triggers events when something changes and its up
> to the policy engine to look at your constraints and decide if
> things should be moved.

Would the following be the correct configuration snippet to have
pacemaker ignore occasional ping failures and only react when *no*
hosts can be pinged?

    primitive ping ocf:pacemaker:ping \
        params name=ping dampen=5s multiplier=10 host_list="..." \
        op start timeout=120 \
        op monitor timeout=60 interval=10 on-fail=ignore

    clone ping_clone ping \
        meta globally-unique=false clone-node-max=1


    location mgt-location mgt \
      rule -INFINITY: not_defined ping or ping number:lte 0


Riccardo Murri

Grid Computing Competence Centre
University of Zurich
Winterthurerstrasse 190, CH-8057 Zürich (Switzerland)
Tel: +41 44 635 4222
Fax: +41 44 635 6888

More information about the Pacemaker mailing list