Add development service convenience runner "openqa-run"

Author: okurz

docs/Contributing.asciidoc

@@ -293,6 +293,17 @@ assets can need a big amount of disk space.
 
 WARNING: Be sure to *clear* that variable when running unit tests locally.
 
+For convenience you can use the `openqa-run` wrapper in to call openQA
+services with `OPENQA_BASEDIR` set to your local development environment with
+the appropriate service account. For example to start the openQA GRU service
+call:
+
+[source,sh]
+----
+tools/openqa-run script/openqa-gru
+----
+
+
 === Customize configuration directory
 It can be necessary during development to change the configuration.
 For example you have to edit `etc/openqa/database.ini` to use another database.

tools/openqa-run

@@ -0,0 +1,38 @@
+#!/bin/bash
+set -euo pipefail
+
+usage() {
+    cat << EOF
+Usage: openqa-run [OPTIONS...] OPENQA_SERVICE
+Call an openQA service OPENQA_SERVICE with appropriate user account and the
+base-dir set to the local working copy.
+
+Example:
+    openqa-run openqa-webui-daemon
+
+Options:
+ -h, --help         display this help
+EOF
+    exit "$1"
+}
+
+OPENQA_BASEDIR="${OPENQA_BASEDIR:-"$(dirname "$0")/../t/data"}"
+
+opts=$(getopt -o h --long help -n "$0" -- "$@") || usage 1
+eval set -- "$opts"
+while true; do
+    case "$1" in
+        -h | --help) usage 0 ;;
+        --)
+            shift
+            break
+            ;;
+        *) break ;;
+    esac
+done
+
+main() {
+    sudo -u geekotest OPENQA_BASEDIR="${OPENQA_BASEDIR}" "$@"
+}
+
+caller 0 > /dev/null || main "$@"