On 2008-08-27T18:48:01, Andreas Mock <[EMAIL PROTECTED]> wrote:
> Despite that you have to emphasize the following:
> What do you do if the piece of code in the
> "do-it-after-resource-start/stop-hock"
> has an error? What do you send back as result code? What happens if the
> "do-it-after-resource-start/stop-hock" lets the whole script die?
Why, blame it on the upstream RA of course - which is exactly why we
don't have those hooks ;-)
> Using a "real" RA for that let's you use the full meachanisms of failure
> detection and appropriate reaction on this failures.
Right.
> Someone on this list once created a OCF-RA-Template/Wrapper which shall allow
> you to write a RA with less effort.
I tend to just start from one of the included ones as template. pingd is
reasonably trivial, for example.
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
