You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://github.com/ClusterLabs/fence-agents/blob/master/doc/FenceAgentAPI.md is highly incomplete, i.e.: No-one is able to develop a fence agent using that information only.
For example stonith -n calls the agent with parameter getconfignames (found by stracing stonith).
When using stonith -m the parameters are getinfo-devdescr, getinfo-devid, and getinfo-xml.
None of those parameters is documented.
I also think that any fence agent should have a "not-really" (-n) option that prevents actually performing fencing operations.
Such would be very valuable when testing the parameter processing of the agent (once there is a tool like ocf-tester for fence agents).
The text was updated successfully, but these errors were encountered:
https://github.com/ClusterLabs/fence-agents/blob/master/doc/FenceAgentAPI.md is highly incomplete, i.e.: No-one is able to develop a fence agent using that information only.
For example
stonith -n
calls the agent with parametergetconfignames
(found by stracingstonith
).When using
stonith -m
the parameters aregetinfo-devdescr
,getinfo-devid
, andgetinfo-xml
.None of those parameters is documented.
I also think that any fence agent should have a "not-really" (
-n
) option that prevents actually performing fencing operations.Such would be very valuable when testing the parameter processing of the agent (once there is a tool like
ocf-tester
for fence agents).The text was updated successfully, but these errors were encountered: