[Pacemaker] Another question about fencing/stonithing

[Digimer]

Andrew might know the trick. In theory, putting your agent into the 
/usr/sbin or /sbin directory (where ever the other agents are) should 
"just work". You're sure the exit codes are appropriate? I am sure they 
are, but just thinking out loud about too-obvious-to-see possible issues.

On 05/07/13 11:17, Andreas Mock wrote:
> Hi Digimer,
>
> sorry I forget to mention that I implemented the metadata-call
> accordingly. But it may be the "registration" thing which
> is necessary to make it know to the stonith/fencing daemon.
>
> I don't know. I'm wondering a little bit that there is no
> pointer how to do it.
>
> Thank you for your answer!
>
> Best regards
> Andreas Mock
>
>
> -----Ursprüngliche Nachricht-----
> Von: Digimer [mailto:lists at alteeve.ca]
> Gesendet: Freitag, 5. Juli 2013 16:52
> An: The Pacemaker cluster resource manager
> Cc: Andreas Mock; Marek Grac
> Betreff: Re: [Pacemaker] Another question about fencing/stonithing
>
> On 05/07/13 03:34, Andreas Mock wrote:
>> Hi all,
>>
>> I just wrote a stonith agent which IMHO implements the
>> API spec found at https://fedorahosted.org/cluster/wiki/FenceAgentAPI.
>>
>> But it seems it has a problem when used as pacemaker stonith device.
>>
>> What has to be done, to have a stonith/fencing agent which implements
>> both roles. I'm pretty sure something is missing.
>> It's just a guess that it has something to do with listing "registered"
>> agents.
>>
>> What is a registered stonith agent and what is done while registering it?
>>
>> When I configure my own fencing agent as packemaker stonith device
>> and try to do a "stonith_admin --list=nodename" I get a "no such device"
>> error.
>>
>> Any pointer appreciated.
>>
>> Best regards
>> Andreas Mock
>
> The API doesn't (yet) cover the metadata action. The agents now have to
> print out XML validation of valid attributes and elements for your
> agent. If you call any existing fence_* agent with just -o metadata, you
> will see the format.
>
> I know rhcs can be forced to see the new agent by putting it in the same
> directory as the other agents and then running 'ccs_update_schema'. If
> pacemaker doesn't immediately see it, then there might be an equivalent
> command you can run.
>
> I will try to get the API updated. I'm not a cardinal source, but
> something is better than nothing. Marek (who I have cc'ed) is, so I can
> run the changes by him when done to ensure they're accurate.
>


-- 
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?