X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/7213d3096cdb5d5e03b559a04f88fcd22a835076..73c880171652a0fd41e38b47de02fc79e4ae05d2:/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 4d101ee86c..647995a8ca 100644
--- a/doc/install/crunch2-slurm/install-test.html.textile.liquid
+++ b/doc/install/crunch2-slurm/install-test.html.textile.liquid
@@ -1,19 +1,28 @@
---
layout: default
navsection: installguide
-title: Test SLURM dispatch
+title: Test Slurm dispatch
...
+{% comment %}
+Copyright (C) The Arvados Authors. All rights reserved.
+
+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.
+{% include 'notebox_end' %}
h2. Test compute node setup
-You should now be able to submit SLURM jobs that run in Docker containers. On the node where you're running the dispatcher, you can test this by running:
+You should now be able to submit Slurm jobs that run in Docker containers. On the node where you're running the dispatcher, you can test this by running:
~$ sudo -u crunch srun -N1 docker run busybox echo OK
-If it works, this command should print @OK@ (it may also show some status messages from SLURM and/or Docker). If it does not print @OK@, double-check your compute node setup, and that the @crunch@ user can submit SLURM jobs.
+If it works, this command should print @OK@ (it may also show some status messages from Slurm and/or Docker). If it does not print @OK@, double-check your compute node setup, and that the @crunch@ user can submit Slurm jobs.
h2. Test the dispatcher
@@ -24,7 +33,7 @@ On the dispatch node, start monitoring the crunch-dispatch-slurm logs:
-*On your shell server*, submit a simple container request:
+Submit a simple container request:
shell:~$ arv container_request create --container-request '{
@@ -48,7 +57,7 @@ On the dispatch node, start monitoring the crunch-dispatch-slurm logs:
-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:
+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:
2016/08/05 13:52:54 Monitoring container zzzzz-dz642-hdp2vpu9nq14tx0 started
@@ -57,9 +66,7 @@ This command should return a record with a @container_uuid@ field. Once crunch-
-If you do not see crunch-dispatch-slurm try to dispatch the container, double-check that it is running and that the API hostname and token in @/etc/arvados/crunch-dispatch-slurm/config.json@ are correct.
-
-Before the container finishes, SLURM's @squeue@ command will show the new job in the list of queued and running jobs. For example, you might see:
+Before the container finishes, Slurm's @squeue@ command will show the new job in the list of queued and running jobs. For example, you might see:
~$ squeue --long
@@ -101,9 +108,9 @@ You can use standard Keep tools to view the container's output and logs from the
./crunch-run.txt
./stderr.txt
./stdout.txt
-~$ arv keep get a01df2f7e5bc1c2ad59c60a837e90dc6+166/stdout.txt
+~$ arv-get a01df2f7e5bc1c2ad59c60a837e90dc6+166/stdout.txt
2016-08-05T13:53:06.201011Z Hello, Crunch!
-If the container does not dispatch successfully, refer to the crunch-dispatch-slurm logs for information about why it failed.
+If the container does not dispatch successfully, refer to the @crunch-dispatch-slurm@ logs for information about why it failed.