[ARVADOS] updated: 1.3.0-2824-gc9d7f6e5c

Git user git at public.arvados.org
Fri Jul 24 21:14:32 UTC 2020


Summary of changes:
 .../install-dispatch-cloud.html.textile.liquid     | 37 ++++++++++++++++++++--
 1 file changed, 35 insertions(+), 2 deletions(-)

       via  c9d7f6e5c734f58fa4b0574dfee40bbffbefdc8d (commit)
      from  dbd421c673da7199ceb3ed1d3398bd55d2707566 (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 c9d7f6e5c734f58fa4b0574dfee40bbffbefdc8d
Author: Ward Vandewege <ward at curii.com>
Date:   Fri Jul 24 17:13:49 2020 -0400

    documentation: arvados-dispatch-cloud: add missing curl command.
    
    No issue #
    
    Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <ward at curii.com>

diff --git a/doc/install/install-dispatch-cloud.html.textile.liquid b/doc/install/install-dispatch-cloud.html.textile.liquid
index ceb02c519..43cad2db8 100644
--- a/doc/install/install-dispatch-cloud.html.textile.liquid
+++ b/doc/install/install-dispatch-cloud.html.textile.liquid
@@ -255,13 +255,46 @@ Submit a simple container request:
 
 This command should return a record with a @container_uuid@ field.  Once @arvados-dispatch-cloud@ polls the API server for new containers to run, you should see it dispatch that same container.
 
-The @arvados-dispatch-cloud@ API a list of queued and running jobs.  For example:
+The @arvados-dispatch-cloud@ API provides a list of queued and running jobs and cloud instances. Use your @ManagementToken@ to test the dispatcher's endpoint. For example, when one container is running:
 
 <notextile>
-<pre><code>~$ <span class="userinput">curl ...</span>
+<pre><code>~$ <span class="userinput">curl -sH "Authorization: Bearer $token" http://localhost:9006/arvados/v1/dispatch/containers</span>
+{
+  "items": [
+    {
+      "container": {
+        "uuid": "zzzzz-dz642-hdp2vpu9nq14tx0",
+        ...
+        "state": "Running",
+        "scheduling_parameters": {
+          "partitions": null,
+          "preemptible": false,
+          "max_run_time": 0
+        },
+        "exit_code": 0,
+        "runtime_status": null,
+        "started_at": null,
+        "finished_at": null
+      },
+      "instance_type": {
+        "Name": "Standard_D2s_v3",
+        "ProviderType": "Standard_D2s_v3",
+        "VCPUs": 2,
+        "RAM": 8589934592,
+        "Scratch": 16000000000,
+        "IncludedScratch": 16000000000,
+        "AddedScratch": 0,
+        "Price": 0.11,
+        "Preemptible": false
+      }
+    }
+  ]
+}
 </code></pre>
 </notextile>
 
+A similar request can be made to the @http://localhost:9006/arvados/v1/dispatch/instances@ endpoint.
+
 When the container finishes, the dispatcher will log it.
 
 After the container finishes, you can get the container record by UUID *from a shell server* to see its results:

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


hooks/post-receive
-- 




More information about the arvados-commits mailing list