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 an on premises cluster that will spool jobs to Slurm or LSF.
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 More detail about the internal operation of the dispatcher can be found in the "architecture section":{{site.baseurl}}/architecture/dispatchcloud.html.
32 h2(#update-config). Update config.yml
34 h3. Configure CloudVMs
36 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. The @DispatchPrivateKey@ should be the *private* key generated in "the previous section":install-compute-node.html#sshkeypair.
42 "http://localhost:9006": {}
45 # BootProbeCommand is a shell command that succeeds when an instance is ready for service
46 BootProbeCommand: "sudo systemctl status docker"
48 <b># --- driver-specific configuration goes here --- see Amazon and Azure examples below ---</b>
51 -----BEGIN RSA PRIVATE KEY-----
52 MIIEpQIBAAKCAQEAqXoCzcOBkFQ7w4dvXf9B++1ctgZRqEbgRYL3SstuMV4oawks
53 ttUuxJycDdsPmeYcHsKo8vsEZpN6iYsX6ZZzhkO5nEayUTU8sBjmg1ZCTo4QqKXr
54 FJ+amZ7oYMDof6QEdwl6KNDfIddL+NfBCLQTVInOAaNss7GRrxLTuTV7HcRaIUUI
55 jYg0Ibg8ZZTzQxCvFXXnjseTgmOcTv7CuuGdt91OVdoq8czG/w8TwOhymEb7mQlt
56 lXuucwQvYgfoUgcnTgpJr7j+hafp75g2wlPozp8gJ6WQ2yBWcfqL2aw7m7Ll88Nd
58 oFyAjVoexx0RBcH6BveTfQtJKbktP1qBO4mXo2dP0cacuZEtlAqW9Eb06Pvaw/D9
59 foktmqOY8MyctzFgXBpGTxPliGjqo8OkrOyQP2g+FL7v+Km31Xs61P8=
60 -----END RSA PRIVATE KEY-----
63 ProviderType: x1.medium
69 ProviderType: x1.large
72 IncludedScratch: 128GB
77 h3(#GPUsupport). NVIDIA GPU support
79 To specify instance types with NVIDIA GPUs, you must include an additional @CUDA@ section:
82 <pre><code> InstanceTypes:
84 ProviderType: g4dn.xlarge
87 IncludedScratch: 125GB
91 HardwareCapability: "7.5"
96 The @DriverVersion@ is the version of the CUDA toolkit installed in your compute image (in X.Y format, do not include the patchlevel). The @HardwareCapability@ is the CUDA compute capability of the GPUs available for this instance type. The @DeviceCount@ is the number of GPU cores available for this instance type.
98 h3. AWS Credentials for Local Keepstore on Compute node
100 When @Containers/LocalKeepBlobBuffersPerVCPU@ is non-zero, the compute node will spin up a local Keepstore service for faster storage access. If Keep is backed by S3, the compute node will need to be able to access the S3 bucket.
102 If the AWS credentials for S3 access are configured in @config.yml@ (i.e. @Volumes/DriverParameters/AccessKeyID@ and @Volumes/DriverParameters/SecretAccessKey@), these credentials will be made available to the local Keepstore on the compute node to access S3 directly and no further configuration is necessary.
104 Alternatively, if an IAM role is configured in @config.yml@ (i.e. @Volumes/DriverParameters/IAMRole@), this role (or an equivalent role) needs be configured in the @CloudVMs/DriverParameters/IAMInstanceProfile@ parameter. That way, @arvados-dispatch-cloud@ can attach the appropriate instance profile to the compute node as it starts up and make the role available to the compute node.
106 h3. Minimal configuration example for Amazon EC2
108 The <span class="userinput">ImageID</span> value is the compute node image that was built in "the previous section":install-compute-node.html#aws.
111 <pre><code> Containers:
113 ImageID: <span class="userinput">ami-01234567890abcdef</span>
116 # If you are not using an IAM role for authentication, specify access
117 # credentials here. Otherwise, omit or set AccessKeyID and
118 # SecretAccessKey to an empty value.
119 AccessKeyID: XXXXXXXXXXXXXXXXXXXX
120 SecretAccessKey: YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
124 SubnetID: subnet-0123abcd
127 AdminUsername: arvados
131 Example policy for the IAM role used by the cloud dispatcher:
136 "Version": "2012-10-17",
137 "Id": "arvados-dispatch-cloud policy",
143 "ec2:DescribeKeyPairs",
146 "ec2:DescribeInstances",
148 "ec2:TerminateInstances"
157 h3. Minimal configuration example for Azure
161 The <span class="userinput">ImageID</span> value is the compute node image that was built in "the previous section":install-compute-node.html#azure.
164 <pre><code> Containers:
166 ImageID: <span class="userinput">"zzzzz-compute-v1597349873"</span>
168 # (azure) managed disks: set MaxConcurrentInstanceCreateOps to 20 to avoid timeouts, cf
169 # https://docs.microsoft.com/en-us/azure/virtual-machines/linux/capture-image
170 MaxConcurrentInstanceCreateOps: 20
173 SubscriptionID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
174 ClientID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
175 ClientSecret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
176 TenantID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
178 # Data center where VMs will be allocated
181 # The resource group where the VM and virtual NIC will be
184 NetworkResourceGroup: yyyyy # only if different from ResourceGroup
186 Subnet: xxxxx-subnet-private
188 # The resource group where the disk image is stored, only needs to
189 # be specified if it is different from ResourceGroup
190 ImageResourceGroup: aaaaa
195 Azure recommends using managed images. If you plan to start more than 20 VMs simultaneously, Azure recommends using a shared image gallery instead to avoid slowdowns and timeouts during the creation of the VMs.
197 Using an image from a shared image gallery:
200 <pre><code> Containers:
202 ImageID: <span class="userinput">"shared_image_gallery_image_definition_name"</span>
206 SubscriptionID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
207 ClientID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
208 ClientSecret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
209 TenantID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
211 # Data center where VMs will be allocated
214 # The resource group where the VM and virtual NIC will be
217 NetworkResourceGroup: yyyyy # only if different from ResourceGroup
219 Subnet: xxxxx-subnet-private
221 # The resource group where the disk image is stored, only needs to
222 # be specified if it is different from ResourceGroup
223 ImageResourceGroup: aaaaa
225 # (azure) shared image gallery: the name of the gallery
226 SharedImageGalleryName: "shared_image_gallery_1"
227 # (azure) shared image gallery: the version of the image definition
228 SharedImageGalleryImageVersion: "0.0.1"
233 Using unmanaged disks (deprecated):
235 The <span class="userinput">ImageID</span> value is the compute node image that was built in "the previous section":install-compute-node.html#azure.
238 <pre><code> Containers:
240 ImageID: <span class="userinput">"https://zzzzzzzz.blob.core.windows.net/system/Microsoft.Compute/Images/images/zzzzz-compute-osDisk.55555555-5555-5555-5555-555555555555.vhd"</span>
244 SubscriptionID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
245 ClientID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
246 ClientSecret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
247 TenantID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
249 # Data center where VMs will be allocated
252 # The resource group where the VM and virtual NIC will be
255 NetworkResourceGroup: yyyyy # only if different from ResourceGroup
257 Subnet: xxxxx-subnet-private
259 # Where to store the VM VHD blobs
260 StorageAccount: example
266 Get the @SubscriptionID@ and @TenantID@:
272 "cloudName": "AzureCloud",
273 "id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX",
275 "name": "Your Subscription",
277 "tenantId": "YYYYYYYY-YYYY-YYYY-YYYYYYYY",
279 "name": "you@example.com",
286 You will need to create a "service principal" to use as a delegated authority for API access.
288 <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>
289 $ az ad sp create "<span class="userinput">appId</span>"
290 (appId is part of the response of the previous command)
291 $ az role assignment create --assignee "<span class="userinput">objectId</span>" --role Owner --scope /subscriptions/{subscriptionId}/
292 (objectId is part of the response of the previous command)
293 </code></pre></notextile>
295 Now update your @config.yml@ file:
297 @ClientID@ is the 'appId' value.
299 @ClientSecret@ is what was provided as <span class="userinput">Your_Password</span>.
301 h3. Test your configuration
303 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.
306 <pre><code>~$ <span class="userinput">arvados-server cloudtest && echo "OK!"</span>
310 Refer to the "cloudtest tool documentation":../../admin/cloudtest.html for more information.
312 {% assign arvados_component = 'arvados-dispatch-cloud' %}
314 {% include 'install_packages' %}
316 {% include 'start_service' %}
318 {% include 'restart_api' %}
320 h2(#confirm-working). Confirm working installation
322 On the dispatch node, start monitoring the arvados-dispatch-cloud logs:
325 <pre><code>~$ <span class="userinput">sudo journalctl -o cat -fu arvados-dispatch-cloud.service</span>
329 "Make sure to install the arvados/jobs image.":../install-jobs-image.html
331 Submit a simple container request:
334 <pre><code>shell:~$ <span class="userinput">arv container_request create --container-request '{
336 "state": "Committed",
338 "container_image": "arvados/jobs:latest",
339 "command": ["echo", "Hello, Crunch!"],
340 "output_path": "/out",
347 "runtime_constraints": {
355 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.
357 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:
360 <pre><code>~$ <span class="userinput">curl -sH "Authorization: Bearer $token" http://localhost:9006/arvados/v1/dispatch/containers</span>
365 "uuid": "zzzzz-dz642-hdp2vpu9nq14tx0",
368 "scheduling_parameters": {
370 "preemptible": false,
374 "runtime_status": null,
379 "Name": "Standard_D2s_v3",
380 "ProviderType": "Standard_D2s_v3",
383 "Scratch": 16000000000,
384 "IncludedScratch": 16000000000,
395 A similar request can be made to the @http://localhost:9006/arvados/v1/dispatch/instances@ endpoint.
397 When the container finishes, the dispatcher will log it.
399 After the container finishes, you can get the container record by UUID *from a shell server* to see its results:
402 <pre><code>shell:~$ <span class="userinput">arv get <b>zzzzz-dz642-hdp2vpu9nq14tx0</b></span>
406 "log":"a01df2f7e5bc1c2ad59c60a837e90dc6+166",
407 "output":"d41d8cd98f00b204e9800998ecf8427e+0",
414 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:
417 <pre><code>~$ <span class="userinput">arv keep ls <b>a01df2f7e5bc1c2ad59c60a837e90dc6+166</b></span>
421 ~$ <span class="userinput">arv-get <b>a01df2f7e5bc1c2ad59c60a837e90dc6+166</b>/stdout.txt</span>
422 2016-08-05T13:53:06.201011Z Hello, Crunch!
426 If the container does not dispatch successfully, refer to the @arvados-dispatch-cloud@ logs for information about why it failed.