Removed all incorrect references to celery

doc/adv-manual/general.rst

@@ -944,9 +944,9 @@ existing code.
 Another tricky point in cluster situations is that we need
 to transfer gigabytes of data, i.e. the large arrays coming from
 scientific calculations, rather than lots of small
-messages. Hence, since recent versions of the engine, we are returning
+messages. Hence, we are returning
 data from the tasks via zeromq instead of using celery/rabbitmq as we
-did in the past. This
+did in the remote past. This
 is hidden from the user, but internally the engine keeps track of all
 tasks that were submitted and waits until they send the message that
 they finished. If one task runs out of memory badly and never sends

doc/glossary.md

@@ -45,9 +45,7 @@
 
 * **worker process**
 
-  A process which is dedicated to task execution. Worker process are simply celeryd processes which are configured to execute OpenQuake Engine task code.
-
-  For more information about Celery, see http://celeryproject.org/.
+  A process which is dedicated to task execution.
 
 * **worker machine**
 

doc/hardware-suggestions.md

@@ -21,7 +21,7 @@ Our cluster master node "wilson" is a Dell® PowerEdge™ R720 with 16 Xeon core
 
 For our largest calculations on a continental or global scale we use a cluster composed of "wilson" (see above) acting as a "master" and two clusters composed by 5 worker nodes (Dell® PowerEdge™ M915 blades) each with 4x 16 cores AMD® Opteron™ and 128GB of RAM for the first and 4 Dell® PowerEdge™ M630 blades (2x 20t/10c Intel® Xeon™ E5-2640v4, 128GB RAM each) for the second cluster.  Worker nodes do not need much disk since the data is stored in the master filesystem.
 
-Network is made with a link aggregation between two 10 gigabit connections; however, up to a couple hundred celery workers a single gigabit connection is enough.
+Network is made with a link aggregation between two 10 gigabit connections; however, up to a couple hundred workers a single gigabit connection is enough.
 
 Windows is not supported for large scale deployments.
 

doc/installing/ubuntu.md

@@ -30,8 +30,6 @@ sudo apt install python3-oq-engine
 The package installs three system service managed through [systemd](https://www.freedesktop.org/software/systemd/man/systemctl.html):
 - `openquake-dbserver`: provides the database for the OpenQuake Engine and must be started before running any `oq engine` command
 - `openquake-webui`: provides the WebUI and is optional
-- `openquake-celery`: used only on a multi-node setup, not used in a default setup
-
 `openquake-dbserver` and `openquake-webui` are started by default at boot.
 
 To manually start, stop or restart a service run

doc/sphinx/baselib.rst

@@ -3,8 +3,8 @@ openquake.baselib
 =================
 
 `openquake.baselib` is a collection of utilities to run large numeric
-simulations. It includes support for parallel computing (via multiprocessing,
-celery, zmq or dask), performance monitoring and a serialization library
+simulations. It includes support for parallel computing (via multiprocessing
+or zmq), performance monitoring and a serialization library
 from Python objects to HDF5 files and viceversa.
 
 Development and support

openquake/baselib/tests/parallel_test.py

@@ -26,11 +26,6 @@
 import numpy
 from openquake.baselib import parallel, general, hdf5, performance
 
-try:
-    import celery
-except ImportError:
-    celery = None
-
 
 def get_length(data, monitor):
     return {'n': len(data)}

utils/reset-db

@@ -89,7 +89,6 @@ echo ''
 echo "!! ${BOLD}This script is going to remove the OpenQuake Engine data${NORMAL}"
 echo '!!'
 echo -e "!! \t*  Make sure no calculations are running"
-echo -e "!! \t*  Make sure Celery is stopped, if used"
 echo -e "!! \t*  The OpenQuake Engine datastores located in /home/[user]/oqdata will be removed"
 echo -e "!! \t*  The OpenQuake Engine database will be dropped"
 echo -e "!! \t   All the old data contained will be lost"