[Pacemaker] questions about expected behaviour stonith:meatware

[Jelle de Jong]

Hello everybody,

I was doing some testing/experiments with stonith:meatware using the
following configuration: http://paste.debian.net/119991/

question 1: does somebody know if I should add a pingd location to the
meatware stonith (see configuration)

question 2: I had my resources running on node hennessy, pulled out all
network cables to see what happens next...

The viktoriya node detects hennessy is gone and sends out the following
distress call:

info: client tengine [pid: 1776] requests a STONITH operation RESET on
node hennessy
info: stonith_operate_locally::2713: sending fencing op RESET for
hennessy to stonith_hennessy (meatware) (pid=8029)
CRIT: OPERATOR INTERVENTION REQUIRED to reset hennessy.
CRIT: Run "meatclient -c hennessy" AFTER power-cycling the machine.

So I am waiting and waiting until viktoriya starts its kvm guests but
nothing happens it just sits there... http://paste.debian.net/119984/

_until_ I executed meatclient -c hennessy (y) and the kvm guests started

Is this what stonith:meatware is expected to do? I was hoping viktoriya
would start the kvm guests, sent out distress and will fence hennessy
and expect the administrator to get hennessy back in a usable state and
then execute the meatclient -c hennessy command so AFTER a reboot.

The only documentation I could find:
less -S /usr/share/doc/cluster-glue/stonith/README.meatware

Thanks in advance,

Kind regards,

Jelle de Jong