[Pacemaker] status and monitor - why the duplicity?

[Stallmann, Andreas]

Hi!

I figure that many ocf agents use either “status” or “monitor” and sometimes both.

What does Pacemaker / crm expect?

Some examples:


-          tomcat agent always returns OCF_SUCCESS on status: why ask, when you always get the same answer

-          tomcat agent returns OCF_NOT_RUNNING, OCF_ERR_* or OCF_SUCCESS on monitor

-          drbd does not use status at all but uses monitor (which returns NOT_RUNNING, SUCCESS, MASTER, ERR_*

-          mysql (master/slave) uses both, where status checks only if mysql has a running process and monitor checks the master/slave state etc.

I’m a little confused. What would be your advice, if you wrote your own resource agent?

Cheers,

Andreas


--
CONET Solutions GmbH
Andreas Stallmann,
Theodor-Heuss-Allee 19, 53773 Hennef
Tel.: +49 2242 939-677, Fax: +49 2242 939-393
Mobil: +49 172 2455051
Internet: http://www.conet.de, mailto: AStallmann at CONET.DE<mailto:AStallmann at CONET.DE>



----------------------------
CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef.
Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136)
Geschäftsführer/Managing Director: Anke Höfer

 ----------------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20120615/a32e2757/attachment.html>