add generic monitor framework

Instead of having a central file or group of files to
describe what data resources should be monitored.  The
content of these files will depend on what core system
monitoring is used ((e.g. Nagios or Monasca).

It's desirable to have each recipe describes what
it wants be monitored in generic way such that various system
monitors can understand and convert these into their format.

If a recipe wishes to register itself to system monitor, it
inherits monitor bbclass and use MONITOR_SERVICE_PACKAGES and
MONITOR_SERVICE_<package name> to indicate what processes
should should be monitored.  Also MONITOR_CHECKS_<package name>
variale can be used to pass list of scripts which will be run
on target and if any of these scripts fail then will report.

Eventually monitor.bbclass will be expanded to allow recipe
to describe more complicated information passed down to
system monitor (e.g. Nagios or Monasca)

Signed-off-by: Vu Tran <vu.tran@windriver.com>

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

1 files changed, 14 insertions, 0 deletions

diff --git a/meta-openstack/recipes-devtools/python/python-glanceclient/glance-api-check.sh b/meta-openstack/recipes-devtools/python/python-glanceclient/glance-api-check.sh
new file mode 100644
index 0000000..aa8340a
--- /dev/null
+++ b/meta-openstack/recipes-devtools/python/python-glanceclient/glance-api-check.sh
@@ -0,0 +1,14 @@
+#! /bin/bash
+
+CMD="glance image-list"
+
+data=$($CMD 2>&1)
+res=$?
+if [ ${res} -eq 127 ]; then
+    exit 0
+elif [ ${res} -ne 0 ]; then
+    echo "OpenStack \"glance api\" failed: "
+    echo $data
+    exit $res
+fi
+exit 0