[ClusterLabs] ocf:pacemaker:ping works strange

[Artem]

Dear Ken and other experts.

How can I leverage pingd to speedup failover? Or may be it is useless and
we should leverage monitor/start timeouts and
migration-threshold/failure-timeout ?

I have preference like this for normal operations:
> pcs constraint location FAKE3 prefers lustre3=100
> pcs constraint location FAKE3 prefers lustre4=90
> pcs constraint location FAKE4 prefers lustre3=90
> pcs constraint location FAKE4 prefers lustre4=100
> pcs resource defaults update resource-stickiness=110
And I need a rule to decrease preference score on a node where pingd fails.
I'm checking it by VM being powered off with pacemaker unaware of it (no
agents on ESXi/vCenter).

On Mon, 11 Dec 2023 at 19:00, Ken Gaillot <kgaillot at redhat.com> wrote:

> > Question #1) Why I cannot see accumulated score from pingd in
> > crm_simulate output? Only location score and stickiness.
>
> ping scores aren't added to resource scores, they're just set as node
> attribute values. Location constraint rules map those values to
> resource scores (in this case any defined ping score gets mapped to
> 125).
> --
> Ken Gaillot <kgaillot at redhat.com>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20231212/1de8d392/attachment.htm>