3 navsection: installguide
4 title: Install the cloud dispatcher
7 Copyright (C) The Arvados Authors. All rights reserved.
9 SPDX-License-Identifier: CC-BY-SA-3.0
12 # "Introduction":#introduction
13 # "Create compute node VM image":#create-image
14 # "Update config.yml":#update-config
15 # "Install arvados-dispatch-cloud":#install-packages
16 # "Start the service":#start-service
17 # "Restart the API server and controller":#restart-api
18 # "Confirm working installation":#confirm-working
20 h2(#introduction). Introduction
22 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.
24 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.
26 h2(#create-image). Create compute node VM image
28 Create a VM image following the steps "to set up a compute node":crunch2-slurm/install-compute-node.html
30 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:
33 10.20.30.40 ClusterID.example.com
36 h2(#update-config). Update config.yml
38 h3. Create a private key
40 Generate an SSH private key with no passphrase. Save it in the cluster configuration file (see @PrivateKey@ in the example below).
43 <pre><code>~$ <span class="userinput">ssh-keygen -N '' -f ~/.ssh/id_dispatcher</span>
44 Generating public/private rsa key pair.
45 Your identification has been saved in /home/user/.ssh/id_dispatcher.
46 Your public key has been saved in /home/user/.ssh/id_dispatcher.pub.
47 The key fingerprint is:
49 ~$ <span class="userinput">cat ~/.ssh/id_dispatcher</span>
50 -----BEGIN RSA PRIVATE KEY-----
51 MIIEpQIBAAKCAQEAqXoCzcOBkFQ7w4dvXf9B++1ctgZRqEbgRYL3SstuMV4oawks
52 ttUuxJycDdsPmeYcHsKo8vsEZpN6iYsX6ZZzhkO5nEayUTU8sBjmg1ZCTo4QqKXr
54 oFyAjVoexx0RBcH6BveTfQtJKbktP1qBO4mXo2dP0cacuZEtlAqW9Eb06Pvaw/D9
55 foktmqOY8MyctzFgXBpGTxPliGjqo8OkrOyQP2g+FL7v+Km31Xs61P8=
56 -----END RSA PRIVATE KEY-----
60 You can delete the key files after you have copied the private key to your configuration file.
63 <pre><code>~$ <span class="userinput">rm ~/.ssh/id_dispatcher ~/.ssh/id_dispatcher.pub</span>
67 h3. Configure CloudVMs
69 Add or update the following portions of your cluster configuration file, @/etc/arvados/config.yml@. Refer to "config.defaults.yml":{{site.baseurl}}/admin/config.html for information about additional configuration options.
75 "http://localhost:9006": {}
78 # BootProbeCommand is a shell command that succeeds when an instance is ready for service
79 BootProbeCommand: "sudo systemctl status docker"
81 <b># --- driver-specific configuration goes here --- see Amazon and Azure examples below ---</b>
84 -----BEGIN RSA PRIVATE KEY-----
85 MIIEpQIBAAKCAQEAqXoCzcOBkFQ7w4dvXf9B++1ctgZRqEbgRYL3SstuMV4oawks
86 ttUuxJycDdsPmeYcHsKo8vsEZpN6iYsX6ZZzhkO5nEayUTU8sBjmg1ZCTo4QqKXr
87 FJ+amZ7oYMDof6QEdwl6KNDfIddL+NfBCLQTVInOAaNss7GRrxLTuTV7HcRaIUUI
88 jYg0Ibg8ZZTzQxCvFXXnjseTgmOcTv7CuuGdt91OVdoq8czG/w8TwOhymEb7mQlt
89 lXuucwQvYgfoUgcnTgpJr7j+hafp75g2wlPozp8gJ6WQ2yBWcfqL2aw7m7Ll88Nd
91 oFyAjVoexx0RBcH6BveTfQtJKbktP1qBO4mXo2dP0cacuZEtlAqW9Eb06Pvaw/D9
92 foktmqOY8MyctzFgXBpGTxPliGjqo8OkrOyQP2g+FL7v+Km31Xs61P8=
93 -----END RSA PRIVATE KEY-----
96 ProviderType: x1.medium
102 ProviderType: x1.large
105 IncludedScratch: 128GB
110 h4. Minimal configuration example for Amazon EC2
113 <pre><code> Containers:
115 ImageID: ami-01234567890abcdef
118 AccessKeyID: XXXXXXXXXXXXXXXXXXXX
119 SecretAccessKey: YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
122 SubnetID: subnet-0123abcd
125 AdminUsername: arvados
129 h4. Minimal configuration example for Azure
132 <pre><code> Containers:
134 ImageID: "https://zzzzzzzz.blob.core.windows.net/system/Microsoft.Compute/Images/images/zzzzz-compute-osDisk.55555555-5555-5555-5555-555555555555.vhd"
137 SubscriptionID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
138 ClientID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
139 ClientSecret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
140 TenantID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
141 CloudEnvironment: AzurePublicCloud
145 Subnet: zzzzz-subnet-private
146 StorageAccount: example
148 DeleteDanglingResourcesAfter: 20s
149 AdminUsername: arvados
153 Get the @SubscriptionID@ and @TenantID@:
159 "cloudName": "AzureCloud",
160 "id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX",
162 "name": "Your Subscription",
164 "tenantId": "YYYYYYYY-YYYY-YYYY-YYYYYYYY",
166 "name": "you@example.com",
173 You will need to create a "service principal" to use as a delegated authority for API access.
176 $ 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 <Your_Password>
177 $ az ad sp create "<appId>"
178 (appId is part of the response of the previous command)
179 $ az role assignment create --assignee "<objectId>" --role Owner --scope /subscriptions/{subscriptionId}/
180 (objectId is part of the response of the previous command)
183 @ClientID@ is the 'appId' value.
185 @ClientSecret@ is what was provided as <Your_Password>.
187 h3. Test your configuration
189 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.
192 <pre><code>~$ <span class="userinput">arvados-server cloudtest && echo "OK!"</span>
196 Refer to the "cloudtest tool documentation":../admin/cloudtest.html for more information.
198 {% assign arvados_component = 'arvados-dispatch-cloud' %}
200 {% include 'install_packages' %}
202 {% include 'start_service' %}
204 {% include 'restart_api' %}
206 h2(#confirm-working). Confirm working installation
208 On the dispatch node, start monitoring the arvados-dispatch-cloud logs:
211 <pre><code>~$ <span class="userinput">sudo journalctl -o cat -fu arvados-dispatch-cloud.service</span>
215 "Make sure to install the arvados/jobs image.":install-jobs-image.html
217 Submit a simple container request:
220 <pre><code>shell:~$ <span class="userinput">arv container_request create --container-request '{
222 "state": "Committed",
224 "container_image": "arvados/jobs:latest",
225 "command": ["echo", "Hello, Crunch!"],
226 "output_path": "/out",
233 "runtime_constraints": {
241 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.
243 The @arvados-dispatch-cloud@ API a list of queued and running jobs. For example:
246 <pre><code>~$ <span class="userinput">curl ...</span>
250 When the container finishes, the dispatcher will log it.
252 After the container finishes, you can get the container record by UUID *from a shell server* to see its results:
255 <pre><code>shell:~$ <span class="userinput">arv get <b>zzzzz-dz642-hdp2vpu9nq14tx0</b></span>
259 "log":"a01df2f7e5bc1c2ad59c60a837e90dc6+166",
260 "output":"d41d8cd98f00b204e9800998ecf8427e+0",
267 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:
270 <pre><code>~$ <span class="userinput">arv keep ls <b>a01df2f7e5bc1c2ad59c60a837e90dc6+166</b></span>
274 ~$ <span class="userinput">arv-get <b>a01df2f7e5bc1c2ad59c60a837e90dc6+166</b>/stdout.txt</span>
275 2016-08-05T13:53:06.201011Z Hello, Crunch!
279 If the container does not dispatch successfully, refer to the @arvados-dispatch-cloud@ logs for information about why it failed.