[Pacemaker] updating an external stonith plugin?

[Ashley Pittman]

On Fri, 2012-06-01 at 04:44 -0700, Digimer wrote:
> One new thing that is not mentioned on the API page is the new '-o
> metadata' output. This is needed now for validating the configuration of
> the fence agent.
> 
> If you run 'fence_<pick_a_few> -o metadata' you will see what the output
> should look like. It's pretty simple XML show what options are valid.
> All resource and fence agents need this now.

This is the same as 'echo option=metadata | fence_<agent>' I assume?  It
seems to be from what's installed.  I have the XML there anyway but can
add the new way to access it as well.

One thing that I did find, initially my code was putting a extra newline
before the XML started, with it like this I could add resources and the
stonith agent would be called correctly if required, I got errors in the
logs about extra output in the xml stream though.  When I remove the
newline this went away which looks to me like it's parsing the XML in
two different places with different parsers.

Attached is what I've come up with so far, I found I had to configure it
with pcmk_host_list=<hostname> and set the hostname of the ipmi card as
an attribute, then define one stonith resource per host.  I also had to
list "start" and "stop" actions or I would get errors when I tried to
configure the resource, even though I don't implement them.

The reason for the delays is we on some systems we use shared-port IPMI
cards and the interfaces go off-line for a time whilst the node is
rebooting and going through the BIOS.

Ashley.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: fence_ddn_ipmi
Type: text/x-python
Size: 4547 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120601/e92f24b0/attachment-0004.py>