X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/7458c097e5ecdbb8836be941f03a5de4943f1eff..4d0ab09acfd9aed9c4b2cf6c1a85a9538e9c969d:/doc/install/crunch2-slurm/install-test.html.textile.liquid diff --git a/doc/install/crunch2-slurm/install-test.html.textile.liquid b/doc/install/crunch2-slurm/install-test.html.textile.liquid index 647995a8ca..ffd75a7793 100644 --- a/doc/install/crunch2-slurm/install-test.html.textile.liquid +++ b/doc/install/crunch2-slurm/install-test.html.textile.liquid @@ -10,7 +10,7 @@ SPDX-License-Identifier: CC-BY-SA-3.0 {% endcomment %} {% include 'notebox_begin_warning' %} -crunch-dispatch-slurm is only relevant for on premises clusters that will spool jobs to Slurm. Skip this section if you are installing a cloud cluster. +@crunch-dispatch-slurm@ is only relevant for on premises clusters that will spool jobs to Slurm. Skip this section if you use LSF or if you are installing a cloud cluster. {% include 'notebox_end' %} h2. Test compute node setup @@ -26,38 +26,28 @@ If it works, this command should print @OK@ (it may also show some status messag h2. Test the dispatcher +Make sure all of your compute nodes are set up with "Docker":../crunch2/install-compute-node-docker.html or "Singularity":../crunch2/install-compute-node-singularity.html. + On the dispatch node, start monitoring the crunch-dispatch-slurm logs: -
~$ sudo journalctl -o cat -fu crunch-dispatch-slurm.service
+
# journalctl -o cat -fu crunch-dispatch-slurm.service
 
-Submit a simple container request: +In another terminal window, use the diagnostics tool to run a simple container. -
shell:~$ arv container_request create --container-request '{
-  "name":            "test",
-  "state":           "Committed",
-  "priority":        1,
-  "container_image": "arvados/jobs:latest",
-  "command":         ["echo", "Hello, Crunch!"],
-  "output_path":     "/out",
-  "mounts": {
-    "/out": {
-      "kind":        "tmp",
-      "capacity":    1000
-    }
-  },
-  "runtime_constraints": {
-    "vcpus": 1,
-    "ram": 8388608
-  }
-}'
+
# arvados-client sudo diagnostics
+INFO       5: running health check (same as `arvados-server check`)
+INFO      10: getting discovery document from https://zzzzz.arvadosapi.com/discovery/v1/apis/arvados/v1/rest
+...
+INFO     160: running a container
+INFO      ... container request submitted, waiting up to 10m for container to run
 
-This command should return a record with a @container_uuid@ field. Once @crunch-dispatch-slurm@ polls the API server for new containers to run, you should see it dispatch that same container. It will log messages like: +Once @crunch-dispatch-slurm@ polls the API server for new containers to run, you should see it dispatch the new container. It will log messages like:
2016/08/05 13:52:54 Monitoring container zzzzz-dz642-hdp2vpu9nq14tx0 started