15467: Formatting fixes
authorPeter Amstutz <pamstutz@veritasgenetics.com>
Fri, 2 Aug 2019 15:03:50 +0000 (11:03 -0400)
committerPeter Amstutz <pamstutz@veritasgenetics.com>
Fri, 2 Aug 2019 19:01:26 +0000 (15:01 -0400)
Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <pamstutz@veritasgenetics.com>

doc/install/crunch2-slurm/install-dispatch.html.textile.liquid
doc/install/install-ws.html.textile.liquid

index 28817dd2955bd57212cebbc3942435f85af8d583..8ed6dc105a85463a3e995d95bbc2b2eac6daf1f8 100644 (file)
@@ -55,10 +55,10 @@ Clusters:
   zzzzz:
     Containers:
       SLURM:
-        KeepServices:
+        <span class="userinput">KeepServices:
           00000-bi6l4-000000000000000:
            InternalURLs:
-              "http://127.0.0.1:25107": {}
+              "http://127.0.0.1:25107": {}</span>
 </code></pre>
 </notextile>
 
@@ -75,7 +75,7 @@ Clusters:
 </code></pre>
 </notextile>
 
-h3(#PrioritySpread). PrioritySpread
+h3(#PrioritySpread). Containers.SLURM.PrioritySpread
 
 crunch-dispatch-slurm adjusts the "nice" values of its SLURM jobs to ensure containers are prioritized correctly relative to one another. This option tunes the adjustment mechanism.
 * If non-Arvados jobs run on your SLURM cluster, and your Arvados containers are waiting too long in the SLURM queue because their "nice" values are too high for them to compete with other SLURM jobs, you should use a smaller PrioritySpread value.
@@ -103,8 +103,8 @@ Clusters:
   zzzzz:
     Containers:
       SLURM:
-        SbatchArgumentsList:
-          - <b>"--partition=PartitionName"</b>
+        <code class="userinput">SbatchArgumentsList:
+          - <b>"--partition=PartitionName"</b></code>
 </pre>
 </notextile>
 
@@ -119,8 +119,8 @@ If your SLURM cluster uses the @task/cgroup@ TaskPlugin, you can configure Crunc
 Clusters:
   zzzzz:
     Containers:
-    <code class="userinput">CrunchRunArgumentsList:
-      - <b>"-cgroup-parent-subsystem=memory"</b></code>
+      <code class="userinput">CrunchRunArgumentsList:
+        - <b>"-cgroup-parent-subsystem=memory"</b></code>
 </pre>
 </notextile>
 
@@ -143,9 +143,9 @@ Older Linux kernels (prior to 3.18) have bugs in network namespace handling whic
 Clusters:
   zzzzz:
     Containers:
-    <code class="userinput">CrunchRunArgumentsList:
-      - <b>"-container-enable-networking=always"</b>
-      - <b>"-container-network-mode=host"</b></code>
+      <code class="userinput">CrunchRunArgumentsList:
+        - <b>"-container-enable-networking=always"</b>
+        - <b>"-container-network-mode=host"</b></code>
 </pre>
 </notextile>
 
index 1c3b357df8e0702bce2ea9a8afc33068d13abcc1..f6a4bb5fafcc60fda70f936501a25c2f48bb0a13 100644 (file)
@@ -51,15 +51,13 @@ Usage of arvados-ws:
 
 h3. Update cluster config
 
-Edit the cluster config at @/etc/arvados/config.yml@ and set @Services.Websocket.ExternalURL@ and @Services.Websocket.InternalURLs@.  Replace @zzzzz@ with your cluster id.  Expects that @SystemRootToken@, @Services.API@ and @PostgreSQL@ sections are already filled out.
+Edit the cluster config at @/etc/arvados/config.yml@ and set @Services.Websocket.ExternalURL@ and @Services.Websocket.InternalURLs@.  Replace @zzzzz@ with your cluster id.
 
 <notextile>
-<pre><code>
-Clusters:
+<pre><code>Clusters:
   zzzzz:
     Services:
-      <span class="userinput">
-      Websocket:
+      <span class="userinput">Websocket:
         ExternalURL: wss://ws.uuid_prefix.your.domain/websocket
         InternalURLs:
          "http://localhost:9003": {}