[ARVADOS] updated: 1.3.0-714-g0e640f9da

[Git user]

Summary of changes:
 doc/admin/manage-containers.html.textile.liquid | 10 +++++-----
 doc/api/methods/containers.html.textile.liquid  |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

       via  0e640f9dae3500a280c60d0a7eeed3b39e55970f (commit)
      from  2ab088f74a672910751fd5d9927ddef2b58c4a57 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 0e640f9dae3500a280c60d0a7eeed3b39e55970f
Author: Eric Biagiotti <ebiagiotti at veritasgenetics.com>
Date:   Wed Apr 17 16:23:10 2019 -0400

    15002: Improves documentation for container state changing
    
    Arvados-DCO-1.1-Signed-off-by: Eric Biagiotti <ebiagiotti at veritasgenetics.com>

diff --git a/doc/admin/manage-containers.html.textile.liquid b/doc/admin/manage-containers.html.textile.liquid
index fe409cb6c..fe8466677 100644
--- a/doc/admin/manage-containers.html.textile.liquid
+++ b/doc/admin/manage-containers.html.textile.liquid
@@ -1,7 +1,7 @@
 ---
 layout: default
 navsection: admin
-title: Managing container state
+title: Controlling container reuse
 ...
 
 {% comment %}
@@ -10,12 +10,12 @@ Copyright (C) The Arvados Authors. All rights reserved.
 SPDX-License-Identifier: CC-BY-SA-3.0
 {% endcomment %}
 
-This page describes how to change the state of a container from @Complete@ to @Cancelled at . This can be useful to avoid reusing a specific completed container without disabling reuse for the corresponding step in a workflow. For example, if a container exited successfully but produced bad output, it may not be worth updating the workflow to use a new image/version. Instead, changing the state of a container to @Cancelled@ will disable reuse of the specific container.
+This page describes how to control container reuse using the @arv@ command. This can be utilized to avoid reusing a completed container without disabling reuse for the corresponding step in your workflow. For example, if a container exited successfully but produced bad output, it may not be feasible to update the workflow immediately. Meanwhile, changing the state of the container from @Completed@ to @Cancelled@ will disable reuse as the workflow continues to run.
 
-If a container is in the @Complete@ state, the following @arv@ command will change it's state to @Cancelled@, where @-u@ is the @UUID@ of the container:
+If a container is in the @Complete@ state, the following @arv@ command will change its state to @Cancelled@, where @xxxxx-xxxxx-xxxxxxxxxxxxxxx@ is the @UUID@ of the container:
 
 <pre>arv container update -u xxxxx-xxxxx-xxxxxxxxxxxxxxx -c '{"state":"Cancelled"}'</pre>
 
-Use the following command to list all containers that have been cancelled after completion:
+Use the following command to list all containers that exited with 0 and were then cancelled:
 
-<pre>arv container list --filters='[["state", "=", "Cancelled"], ["exit_code", "=", 0]]'</pre>See the "arv CLI tool overview":{{site.baseurl}}/sdk/cli/index.html for more details about using the @arv@ command.
\ No newline at end of file
+<pre>arv container list --filters='[["state", "=", "Cancelled"], ["exit_code", "=", 0]]'</pre>See the "arv CLI tool overview":{{site.baseurl}}/sdk/cli/index.html for more details about using the @arv@ command.
diff --git a/doc/api/methods/containers.html.textile.liquid b/doc/api/methods/containers.html.textile.liquid
index 8058123d0..2ddb00c68 100644
--- a/doc/api/methods/containers.html.textile.liquid
+++ b/doc/api/methods/containers.html.textile.liquid
@@ -65,7 +65,7 @@ table(table table-bordered table-condensed).
 |Queued|Waiting for a dispatcher to lock it and try to run the container.|Locked, Cancelled|
 |Locked|A dispatcher has "taken" the container and is allocating resources for it. The container has not started yet.|Queued, Running, Cancelled|
 |Running|Resources have been allocated and the contained process has been started (or is about to start). Crunch-run _must_ set state to Running _before_ there is any possibility that user code will run in the container.|Complete, Cancelled|
-|Complete|Container was running, and the contained process/command has exited.|Cancelled (admin only)|
+|Complete|Container was running, and the contained process/command has exited.|Cancelled|
 |Cancelled|The container did not run long enough to produce an exit code. This includes cases where the container didn't even start, cases where the container was interrupted/killed before it exited by itself (e.g., priority changed to 0), and cases where some problem prevented the system from capturing the contained process's exit status (exit code and output).|-|
 
 See "Managing container state":{{site.baseurl}}/admin/manage-containers.html for details about changing state from @Complete@ to @Cancelled@

-----------------------------------------------------------------------


hooks/post-receive
--