[rabbitmq-discuss] [PATCH 07 of 10] OCF resource agent: add status operation

Florian Haas florian.haas at linbit.com
Tue May 11 18:09:44 BST 2010


# HG changeset patch
# User Florian Haas <florian.haas at linbit.com>
# Date 1273594291 -7200
# Node ID b3e53e4d8fefabe130b4340a7efaebb14edd1b68
# Parent  26aaf9c7bf34750b15b272f4cbf096abaf7acca6
OCF resource agent: add status operation

Even when it is identical to monitor, a status operation should still
be advertised.

diff -r 26aaf9c7bf34 -r b3e53e4d8fef packaging/common/rabbitmq-server.ocf
--- a/packaging/common/rabbitmq-server.ocf	Tue May 11 18:07:53 2010 +0200
+++ b/packaging/common/rabbitmq-server.ocf	Tue May 11 18:11:31 2010 +0200
@@ -162,6 +162,7 @@
 <actions>
 <action name="start"        timeout="600" />
 <action name="stop"         timeout="120" />
+<action name="status"       timeout="20" interval="10" />
 <action name="monitor"      timeout="20" interval="10" depth="0" start-delay="0" />
 <action name="validate-all" timeout="30" />
 <action name="meta-data"    timeout="5" />
@@ -172,7 +173,7 @@
 
 rabbit_usage() {
 	cat <<END
-usage: $0 {start|stop|monitor|validate-all|meta-data}
+usage: $0 {start|stop|status|monitor|validate-all|meta-data}
 
 Expects to have a fully populated OCF RA-compliant environment set.
 END
@@ -357,7 +358,7 @@
     stop)
 	rabbit_stop
         ;;
-    monitor)
+    status|monitor)
 	rabbit_monitor
         ;;
     validate-all)





More information about the rabbitmq-discuss mailing list