[ClusterLabs] fence agent configuration (was: fencing on iscsi device not working)

[wferi at niif.hu]

Ken Gaillot <kgaillot at redhat.com> writes:

> I edited it so that the default and description are combined:
>
> How to determine which machines are controlled by the device. Allowed
> values:
>
> * +static-list:+ check the +pcmk_host_list+ or +pcmk_host_map+
> attribute (this is the default if either one of those is set)
>
> * +dynamic-list:+ query the device via the "list" command (this is
> otherwise the default if the fence device supports the list action)
>
> * +status:+ query the device via the "status" command (this is
> otherwise the default if the fence device supports the status action)
>
> * +none:+ assume every device can fence every machine (this is
> otherwise the default)

Before getting to typography: how can the status command help
determining which machines are controlled by the device?

Ignoring that, the explanation could be simplified by stating upfront
that pcmk_host_check is ignored if pcmk_host_list or pcmk_host_map is
set, and pcmk_host_list is ignored if pcmk_host_map is set (maybe start
issuing a warning now and forbid these outright later).  Heck, if not
for status, pcmk_host_check could be dropped altogether by doing:

1. use pcmk_host_map if defined
2. use pcmk_host_list if defined
3. query the device if it supports the list command
4. assume that the device is universal

It should also been clarified whether Pacemaker passes the port or the
nodename attribute to the fence agent in the above cases.
https://github.com/ClusterLabs/fence-agents/blob/master/doc/FenceAgentAPI.md
-- 
Thanks,
Feri