X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/3e8f849f40aed8fe2f6ce7e41c674195d177c52b..9d47c912d10ba901521fd74e2d1a8918c2f733c3:/doc/install/install-dispatch-cloud.html.textile.liquid
diff --git a/doc/install/install-dispatch-cloud.html.textile.liquid b/doc/install/install-dispatch-cloud.html.textile.liquid
index 772ba548c6..5709e5aaa5 100644
--- a/doc/install/install-dispatch-cloud.html.textile.liquid
+++ b/doc/install/install-dispatch-cloud.html.textile.liquid
@@ -9,21 +9,29 @@ Copyright (C) The Arvados Authors. All rights reserved.
SPDX-License-Identifier: CC-BY-SA-3.0
{% endcomment %}
+# "Introduction":#introduction
+# "Create compute node VM image":#create-image
# "Update config.yml":#update-config
# "Install arvados-dispatch-cloud":#install-packages
+# "Start the service":#start-service
+# "Restart the API server and controller":#restart-api
# "Confirm working installation":#confirm-working
+h2(#introduction). Introduction
+
The cloud dispatch service is for running containers on cloud VMs. It works with Microsoft Azure and Amazon EC2; future versions will also support Google Compute Engine.
The cloud dispatch service can run on any node that can connect to the Arvados API service, the cloud provider's API, and the SSH service on cloud VMs. It is not resource-intensive, so you can run it on the API server node.
-*Only one dispatch process should be running at a time.* If you are migrating a system that currently runs @crunch-dispatch-slurm@, it is safest to remove the @crunch-dispatch-slurm@ service entirely before installing @arvados-dispatch-cloud@.
+h2(#create-image). Create compute node VM image
-
-~$ sudo systemctl --now disable crunch-dispatch-slurm
-~$ sudo apt-get remove crunch-dispatch-slurm
-
-
+Create a VM image following the steps "to set up a compute node":crunch2-slurm/install-compute-node.html
+
+On the compute VM image, add the API server's internal IP address to @/etc/hosts@, this will ensure that it contacts the API server on the private network and not through the public interface. For example:
+
+
+10.20.30.40 ClusterID.example.com
+
h2(#update-config). Update config.yml
@@ -99,7 +107,7 @@ Add or update the following portions of your cluster configuration file, @/etc/a
-Minimal configuration example for Amazon EC2:
+h4. Minimal configuration example for Amazon EC2
Containers:
@@ -107,18 +115,18 @@ Minimal configuration example for Amazon EC2:
ImageID: ami-01234567890abcdef
Driver: ec2
DriverParameters:
- AccessKeyID: EALMF21BJC7MKNF9FVVR
- SecretAccessKey: yKJAPmoCQOMtYWzEUQ1tKTyrocTcbH60CRvGP3pM
+ AccessKeyID: XXXXXXXXXXXXXXXXXXXX
+ SecretAccessKey: YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
SecurityGroupIDs:
- sg-0123abcd
SubnetID: subnet-0123abcd
Region: us-east-1
EBSVolumeType: gp2
- AdminUsername: debian
+ AdminUsername: arvados
-Minimal configuration example for Azure:
+h4. Minimal configuration example for Azure
Containers:
@@ -128,7 +136,7 @@ Minimal configuration example for Azure:
DriverParameters:
SubscriptionID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
ClientID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
- ClientSecret: 2WyXt0XFbEtutnf2hp528t6Wk9S5bOHWkRaaWwavKQo=
+ ClientSecret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
TenantID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
CloudEnvironment: AzurePublicCloud
ResourceGroup: zzzzz
@@ -142,6 +150,40 @@ Minimal configuration example for Azure:
+Get the @SubscriptionID@ and @TenantID@:
+
+
+$ az account list
+[
+ {
+ "cloudName": "AzureCloud",
+ "id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX",
+ "isDefault": true,
+ "name": "Your Subscription",
+ "state": "Enabled",
+ "tenantId": "YYYYYYYY-YYYY-YYYY-YYYYYYYY",
+ "user": {
+ "name": "you@example.com",
+ "type": "user"
+ }
+ }
+]
+
+
+You will need to create a "service principal" to use as a delegated authority for API access.
+
+
+$ az ad app create --display-name "Arvados Dispatch Cloud (ClusterID)" --homepage "https://arvados.org" --identifier-uris "https://ClusterID.example.com" --end-date 2299-12-31 --password
+$ az ad sp create ""
+(appId is part of the response of the previous command)
+$ az role assignment create --assignee "" --role Owner --scope /subscriptions/{subscriptionId}/
+(objectId is part of the response of the previous command)
+
+
+@ClientID@ is the 'appId' value.
+
+@ClientSecret@ is what was provided as .
+
h3. Test your configuration
Run the @cloudtest@ tool to verify that your configuration works. This creates a new cloud VM, confirms that it boots correctly and accepts your configured SSH private key, and shuts it down.
@@ -153,38 +195,85 @@ Run the @cloudtest@ tool to verify that your configuration works. This creates a
Refer to the "cloudtest tool documentation":../admin/cloudtest.html for more information.
-h2. Install arvados-dispatch-cloud
+{% assign arvados_component = 'arvados-dispatch-cloud' %}
+
+{% include 'install_packages' %}
-{% include 'notebox_begin' %}
+{% include 'start_service' %}
-The arvados-dispatch-cloud package includes configuration files for systemd. If you're using a different init system, configure a service to start and stop an @arvados-dispatch-cloud@ process as desired.
+{% include 'restart_api' %}
-{% include 'notebox_end' %}
+h2(#confirm-working). Confirm working installation
-h3. Centos 7
+On the dispatch node, start monitoring the arvados-dispatch-cloud logs:
-# yum install arvados-dispatch-cloud
+~$ sudo journalctl -o cat -fu arvados-dispatch-cloud.service
-h3. Debian and Ubuntu
+"Make sure to install the arvados/jobs image.":install-jobs-image.html
+
+Submit a simple container request:
-# apt-get --no-install-recommends install arvados-dispatch-cloud
+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": 1048576
+ }
+}'
-h2(#confirm-working). Confirm working installation
+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.
-Use your @ManagementToken@ to test the dispatcher's metrics endpoint.
+The @arvados-dispatch-cloud@ API a list of queued and running jobs. For example:
-~$ token="xyzzy"
-~$ curl -H "Authorization: Bearer $token" http://localhost:9006/metrics
-# HELP arvados_dispatchcloud_containers_running Number of containers reported running by cloud VMs.
-# TYPE arvados_dispatchcloud_containers_running gauge
-arvados_dispatchcloud_containers_running 0
-[...]
+~$ curl ...
+
+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:
+
+
+shell:~$ arv get zzzzz-dz642-hdp2vpu9nq14tx0
+{
+ ...
+ "exit_code":0,
+ "log":"a01df2f7e5bc1c2ad59c60a837e90dc6+166",
+ "output":"d41d8cd98f00b204e9800998ecf8427e+0",
+ "state":"Complete",
+ ...
+}
+
+
+
+You can use standard Keep tools to view the container's output and logs from their corresponding fields. For example, to see the logs from the collection referenced in the @log@ field:
+
+
+~$ arv keep ls a01df2f7e5bc1c2ad59c60a837e90dc6+166
+./crunch-run.txt
+./stderr.txt
+./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 @arvados-dispatch-cloud@ logs for information about why it failed.