WIP: Start, stop, and supervise gwcelery with systemd

Provide support for starting, stopping, and supervising GWCelery using systemd, the service manager for Linux. Systemd is present on many Linux systems including apparently all LDG cluster nodes and is responsible for bootstrapping userspace and bringing up system services.

The main advantage of using systemd instead of the existing htcondor technique is systemd can stop and restart the components of GWCelery in the proper sequence to minimize downtime and reduce the chances of losing in-flight tasks.

See the file systemd/README.rst included in this patch for instructions.

systemd/gwcelery-worker.service

@@ -10,23 +10,23 @@ Environment=CELERY_BROKER_URL=redis+socket://%t/gwcelery/redis.sock
 ExecStart=/usr/bin/env \
     gwcelery multi start \
     celery openmp exttrig superevent \
-    --queues %%n \
-    --concurrency:openmp,exttrig,superevent 1 \
-    --pidfile %t/gwcelery/%%n.pid \
-    --logfile %L/gwcelery/%%n.log \
-    --loglevel INFO
+    --queues=%%n \
+    --concurrency:openmp,exttrig,superevent=1 \
+    --pidfile=%t/gwcelery/%%n.pid \
+    --logfile=%L/gwcelery/%%n.log \
+    --loglevel=INFO
 ExecStop=/usr/bin/env \
     gwcelery multi stopwait \
     celery openmp exttrig superevent \
-    --pidfile %t/gwcelery/%%n.pid
+    --pidfile=%t/gwcelery/%%n.pid
 ExecReload=/usr/bin/env \
     gwcelery multi reload \
     celery openmp exttrig superevent \
-    --queues %%n \
-    --concurrency openmp,exttrig,superevent:1 \
-    --pidfile %t/gwcelery/%%n.pid \
-    --logfile %L/gwcelery/%%n.log \
-    --loglevel INFO
+    --queues=%%n \
+    --concurrency:openmp,exttrig,superevent=1 \
+    --pidfile=%t/gwcelery/%%n.pid \
+    --logfile=%L/gwcelery/%%n.log \
+    --loglevel=INFO
 
 [Install]
 WantedBy=multi-user.target