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 {% include 'notebox_begin_warning' %}
13 arvados-dispatch-cloud is only relevant for cloud installations. Skip this section if you are installing a on premise cluster that will spool jobs to Slurm.
14 {% include 'notebox_end' %}
16 # "Introduction":#introduction
17 # "Create compute node VM image":#create-image
18 # "Update config.yml":#update-config
19 # "Install arvados-dispatch-cloud":#install-packages
20 # "Start the service":#start-service
21 # "Restart the API server and controller":#restart-api
22 # "Confirm working installation":#confirm-working
24 h2(#introduction). Introduction
26 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.
28 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.
30 h2(#create-image). Create compute node VM image
32 Create a VM image following the steps "to set up a compute node":crunch2-slurm/install-compute-node.html
34 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:
36 <notextile><pre><code>10.20.30.40 <span class="userinput">ClusterID.example.com</span>
37 </code></pre></notextile>
39 h2(#update-config). Update config.yml
41 h3. Create a private key
43 Generate an SSH private key with no passphrase. Save it in the cluster configuration file (see @PrivateKey@ in the example below).
46 <pre><code>~$ <span class="userinput">ssh-keygen -N '' -f ~/.ssh/id_dispatcher</span>
47 Generating public/private rsa key pair.
48 Your identification has been saved in /home/user/.ssh/id_dispatcher.
49 Your public key has been saved in /home/user/.ssh/id_dispatcher.pub.
50 The key fingerprint is:
52 ~$ <span class="userinput">cat ~/.ssh/id_dispatcher</span>
53 -----BEGIN RSA PRIVATE KEY-----
54 MIIEpQIBAAKCAQEAqXoCzcOBkFQ7w4dvXf9B++1ctgZRqEbgRYL3SstuMV4oawks
55 ttUuxJycDdsPmeYcHsKo8vsEZpN6iYsX6ZZzhkO5nEayUTU8sBjmg1ZCTo4QqKXr
57 oFyAjVoexx0RBcH6BveTfQtJKbktP1qBO4mXo2dP0cacuZEtlAqW9Eb06Pvaw/D9
58 foktmqOY8MyctzFgXBpGTxPliGjqo8OkrOyQP2g+FL7v+Km31Xs61P8=
59 -----END RSA PRIVATE KEY-----
63 You can delete the key files after you have copied the private key to your configuration file.
66 <pre><code>~$ <span class="userinput">rm ~/.ssh/id_dispatcher ~/.ssh/id_dispatcher.pub</span>
70 h3. Configure CloudVMs
72 Add or update the following portions of your cluster configuration file, @config.yml@. Refer to "config.defaults.yml":{{site.baseurl}}/admin/config.html for information about additional configuration options.
78 "http://localhost:9006": {}
81 # BootProbeCommand is a shell command that succeeds when an instance is ready for service
82 BootProbeCommand: "sudo systemctl status docker"
84 <b># --- driver-specific configuration goes here --- see Amazon and Azure examples below ---</b>
87 -----BEGIN RSA PRIVATE KEY-----
88 MIIEpQIBAAKCAQEAqXoCzcOBkFQ7w4dvXf9B++1ctgZRqEbgRYL3SstuMV4oawks
89 ttUuxJycDdsPmeYcHsKo8vsEZpN6iYsX6ZZzhkO5nEayUTU8sBjmg1ZCTo4QqKXr
90 FJ+amZ7oYMDof6QEdwl6KNDfIddL+NfBCLQTVInOAaNss7GRrxLTuTV7HcRaIUUI
91 jYg0Ibg8ZZTzQxCvFXXnjseTgmOcTv7CuuGdt91OVdoq8czG/w8TwOhymEb7mQlt
92 lXuucwQvYgfoUgcnTgpJr7j+hafp75g2wlPozp8gJ6WQ2yBWcfqL2aw7m7Ll88Nd
94 oFyAjVoexx0RBcH6BveTfQtJKbktP1qBO4mXo2dP0cacuZEtlAqW9Eb06Pvaw/D9
95 foktmqOY8MyctzFgXBpGTxPliGjqo8OkrOyQP2g+FL7v+Km31Xs61P8=
96 -----END RSA PRIVATE KEY-----
99 ProviderType: x1.medium
102 IncludedScratch: 64GB
105 ProviderType: x1.large
108 IncludedScratch: 128GB
113 h4. Minimal configuration example for Amazon EC2
116 <pre><code> Containers:
118 ImageID: ami-01234567890abcdef
121 AccessKeyID: XXXXXXXXXXXXXXXXXXXX
122 SecretAccessKey: YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
125 SubnetID: subnet-0123abcd
128 AdminUsername: arvados
132 h4. Minimal configuration example for Azure
135 <pre><code> Containers:
137 ImageID: "https://zzzzzzzz.blob.core.windows.net/system/Microsoft.Compute/Images/images/zzzzz-compute-osDisk.55555555-5555-5555-5555-555555555555.vhd"
140 SubscriptionID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
141 ClientID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
142 ClientSecret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
143 TenantID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
144 CloudEnvironment: AzurePublicCloud
148 Subnet: zzzzz-subnet-private
149 StorageAccount: example
151 DeleteDanglingResourcesAfter: 20s
152 AdminUsername: arvados
156 Get the @SubscriptionID@ and @TenantID@:
162 "cloudName": "AzureCloud",
163 "id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX",
165 "name": "Your Subscription",
167 "tenantId": "YYYYYYYY-YYYY-YYYY-YYYYYYYY",
169 "name": "you@example.com",
176 You will need to create a "service principal" to use as a delegated authority for API access.
178 <notextile><pre><code>$ az ad app create --display-name "Arvados Dispatch Cloud (<span class="userinput">ClusterID</span>)" --homepage "https://arvados.org" --identifier-uris "https://<span class="userinput">ClusterID.example.com</span>" --end-date 2299-12-31 --password <span class="userinput">Your_Password</span>
179 $ az ad sp create "<span class="userinput">appId</span>"
180 (appId is part of the response of the previous command)
181 $ az role assignment create --assignee "<span class="userinput">objectId</span>" --role Owner --scope /subscriptions/{subscriptionId}/
182 (objectId is part of the response of the previous command)
183 </code></pre></notextile>
185 Now update your @config.yml@ file:
187 @ClientID@ is the 'appId' value.
189 @ClientSecret@ is what was provided as <span class="userinput">Your_Password</span>.
191 h3. Test your configuration
193 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.
196 <pre><code>~$ <span class="userinput">arvados-server cloudtest && echo "OK!"</span>
200 Refer to the "cloudtest tool documentation":../admin/cloudtest.html for more information.
202 {% assign arvados_component = 'arvados-dispatch-cloud' %}
204 {% include 'install_packages' %}
206 {% include 'start_service' %}
208 {% include 'restart_api' %}
210 h2(#confirm-working). Confirm working installation
212 On the dispatch node, start monitoring the arvados-dispatch-cloud logs:
215 <pre><code>~$ <span class="userinput">sudo journalctl -o cat -fu arvados-dispatch-cloud.service</span>
219 "Make sure to install the arvados/jobs image.":install-jobs-image.html
221 Submit a simple container request:
224 <pre><code>shell:~$ <span class="userinput">arv container_request create --container-request '{
226 "state": "Committed",
228 "container_image": "arvados/jobs:latest",
229 "command": ["echo", "Hello, Crunch!"],
230 "output_path": "/out",
237 "runtime_constraints": {
245 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.
247 The @arvados-dispatch-cloud@ API a list of queued and running jobs. For example:
250 <pre><code>~$ <span class="userinput">curl ...</span>
254 When the container finishes, the dispatcher will log it.
256 After the container finishes, you can get the container record by UUID *from a shell server* to see its results:
259 <pre><code>shell:~$ <span class="userinput">arv get <b>zzzzz-dz642-hdp2vpu9nq14tx0</b></span>
263 "log":"a01df2f7e5bc1c2ad59c60a837e90dc6+166",
264 "output":"d41d8cd98f00b204e9800998ecf8427e+0",
271 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:
274 <pre><code>~$ <span class="userinput">arv keep ls <b>a01df2f7e5bc1c2ad59c60a837e90dc6+166</b></span>
278 ~$ <span class="userinput">arv-get <b>a01df2f7e5bc1c2ad59c60a837e90dc6+166</b>/stdout.txt</span>
279 2016-08-05T13:53:06.201011Z Hello, Crunch!
283 If the container does not dispatch successfully, refer to the @arvados-dispatch-cloud@ logs for information about why it failed.