[Pacemaker] Full API description for Fence Agent

[Andreas Mock]

Hi Digimer, hi all,

there is a little thing in the API doc which is also unclear to me.
It says:

"[...]
status - this is not implemented by most agents nor used by fenced at this
time. Return values:

    0 if the fence device is reachable and the port is in the on state
    1 if the fence device could not be contacted
    2 if the fence device is reachable but is in the off state
[...]"

What is meant with return code 2? Does it mean I could contact the fence
device
and it says that the PORT is in off state?
How do I have to understand the state "fence device in off state"?

Best regards
Andreas Mock



-----Ursprüngliche Nachricht-----
Von: Andreas Mock [mailto:andreas.mock at web.de] 
Gesendet: Donnerstag, 4. Juli 2013 11:25
An: 'Digimer'; 'The Pacemaker cluster resource manager'
Betreff: Re: [Pacemaker] Full API description for Fence Agent

Hi digimer,

I would like to take your offer and asking the following:

The API documents says nothing about the correct way
of giving messages back to the stonith daemon.
So, what is the right way to write error/warn/info messages.

Looking at the scripted agents available I can find a nice
mixture of using STDERR and STDOUT.
What is the rule here?
Can you give insights, whether STDOUT/STDERR is captured by
the calling program and logged somewher (and where)?

By the way: How is it going with merging the stonith/fencing API? ;-)

Best regards
Andreas

-----Ursprüngliche Nachricht-----
Von: Digimer [mailto:lists at alteeve.ca] 
Gesendet: Dienstag, 11. Juni 2013 15:34
An: The Pacemaker cluster resource manager
Cc: Andreas Mock
Betreff: Re: [Pacemaker] Full API description for Fence Agent

Hi Andreas,

   The metadata section of the document has not been added yet, but we 
are aware of it missing and are working to add it. The rest of the 
document is accurate though. If you build an agent to follow that API, 
it will work with red hat's cluster and pacemaker.

   In the meantime, it's not ideal, but if you call any other fence 
agent and pass '-o metadata', you will see the output that the cluster 
expects. It should be easy to adapt to your new agent.

   If you have any trouble, please don't hesitate to ask here and we 
will do our best to help.

digimer

On 06/11/2013 07:04 AM, Andreas Mock wrote:
> Hi all,
>
> we need to implement a fence_agent (stonith agent) for
> cman/corosync/pacemaker (RHEL 6.x). I found the following documentation
> https://fedorahosted.org/cluster/wiki/FenceAgentAPI
>
> But in this document the required metadata action is not
> described. Can anybody point me to a documentation which
> is complete?
>
> Where is the schema of the xml returned by 'metadata'?
>
> What has to be done that a fence_agent can also be used
> by pacemaker?
>
> What is the right return code of action 'metadata'?
>
> Is there some explanation how the stonith/fence parts
> play together?
>
> Best regards
> Andreas Mock
>
>
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>


-- 
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without 
access to education?


_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org