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 h4. NVIDIA GPU support
79 To specify instance types with NVIDIA GPUs, you must include an additional @CUDA@ section:
85 ProviderType: g4dn.xlarge
88 IncludedScratch: 125GB
92 HardwareCapability: "7.5"
97 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.
99 h4. Minimal configuration example for Amazon EC2
101 The <span class="userinput">ImageID</span> value is the compute node image that was built in "the previous section":install-compute-node.html#aws.
104 <pre><code> Containers:
106 ImageID: <span class="userinput">ami-01234567890abcdef</span>
109 # If you are not using an IAM role for authentication, specify access
110 # credentials here. Otherwise, omit or set AccessKeyID and
111 # SecretAccessKey to an empty value.
112 AccessKeyID: XXXXXXXXXXXXXXXXXXXX
113 SecretAccessKey: YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
117 SubnetID: subnet-0123abcd
120 AdminUsername: arvados
124 h4. Minimal configuration example for Azure
128 The <span class="userinput">ImageID</span> value is the compute node image that was built in "the previous section":install-compute-node.html#azure.
131 <pre><code> Containers:
133 ImageID: <span class="userinput">"zzzzz-compute-v1597349873"</span>
135 # (azure) managed disks: set MaxConcurrentInstanceCreateOps to 20 to avoid timeouts, cf
136 # https://docs.microsoft.com/en-us/azure/virtual-machines/linux/capture-image
137 MaxConcurrentInstanceCreateOps: 20
140 SubscriptionID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
141 ClientID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
142 ClientSecret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
143 TenantID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
145 # Data center where VMs will be allocated
148 # The resource group where the VM and virtual NIC will be
151 NetworkResourceGroup: yyyyy # only if different from ResourceGroup
153 Subnet: xxxxx-subnet-private
155 # The resource group where the disk image is stored, only needs to
156 # be specified if it is different from ResourceGroup
157 ImageResourceGroup: aaaaa
162 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.
164 Using an image from a shared image gallery:
167 <pre><code> Containers:
169 ImageID: <span class="userinput">"shared_image_gallery_image_definition_name"</span>
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
192 # (azure) shared image gallery: the name of the gallery
193 SharedImageGalleryName: "shared_image_gallery_1"
194 # (azure) shared image gallery: the version of the image definition
195 SharedImageGalleryImageVersion: "0.0.1"
200 Using unmanaged disks (deprecated):
202 The <span class="userinput">ImageID</span> value is the compute node image that was built in "the previous section":install-compute-node.html#azure.
205 <pre><code> Containers:
207 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>
211 SubscriptionID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
212 ClientID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
213 ClientSecret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
214 TenantID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
216 # Data center where VMs will be allocated
219 # The resource group where the VM and virtual NIC will be
222 NetworkResourceGroup: yyyyy # only if different from ResourceGroup
224 Subnet: xxxxx-subnet-private
226 # Where to store the VM VHD blobs
227 StorageAccount: example
233 Get the @SubscriptionID@ and @TenantID@:
239 "cloudName": "AzureCloud",
240 "id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX",
242 "name": "Your Subscription",
244 "tenantId": "YYYYYYYY-YYYY-YYYY-YYYYYYYY",
246 "name": "you@example.com",
253 You will need to create a "service principal" to use as a delegated authority for API access.
255 <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>
256 $ az ad sp create "<span class="userinput">appId</span>"
257 (appId is part of the response of the previous command)
258 $ az role assignment create --assignee "<span class="userinput">objectId</span>" --role Owner --scope /subscriptions/{subscriptionId}/
259 (objectId is part of the response of the previous command)
260 </code></pre></notextile>
262 Now update your @config.yml@ file:
264 @ClientID@ is the 'appId' value.
266 @ClientSecret@ is what was provided as <span class="userinput">Your_Password</span>.
268 h3. Test your configuration
270 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.
273 <pre><code>~$ <span class="userinput">arvados-server cloudtest && echo "OK!"</span>
277 Refer to the "cloudtest tool documentation":../../admin/cloudtest.html for more information.
279 {% assign arvados_component = 'arvados-dispatch-cloud' %}
281 {% include 'install_packages' %}
283 {% include 'start_service' %}
285 {% include 'restart_api' %}
287 h2(#confirm-working). Confirm working installation
289 On the dispatch node, start monitoring the arvados-dispatch-cloud logs:
292 <pre><code>~$ <span class="userinput">sudo journalctl -o cat -fu arvados-dispatch-cloud.service</span>
296 "Make sure to install the arvados/jobs image.":../install-jobs-image.html
298 Submit a simple container request:
301 <pre><code>shell:~$ <span class="userinput">arv container_request create --container-request '{
303 "state": "Committed",
305 "container_image": "arvados/jobs:latest",
306 "command": ["echo", "Hello, Crunch!"],
307 "output_path": "/out",
314 "runtime_constraints": {
322 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.
324 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:
327 <pre><code>~$ <span class="userinput">curl -sH "Authorization: Bearer $token" http://localhost:9006/arvados/v1/dispatch/containers</span>
332 "uuid": "zzzzz-dz642-hdp2vpu9nq14tx0",
335 "scheduling_parameters": {
337 "preemptible": false,
341 "runtime_status": null,
346 "Name": "Standard_D2s_v3",
347 "ProviderType": "Standard_D2s_v3",
350 "Scratch": 16000000000,
351 "IncludedScratch": 16000000000,
362 A similar request can be made to the @http://localhost:9006/arvados/v1/dispatch/instances@ endpoint.
364 When the container finishes, the dispatcher will log it.
366 After the container finishes, you can get the container record by UUID *from a shell server* to see its results:
369 <pre><code>shell:~$ <span class="userinput">arv get <b>zzzzz-dz642-hdp2vpu9nq14tx0</b></span>
373 "log":"a01df2f7e5bc1c2ad59c60a837e90dc6+166",
374 "output":"d41d8cd98f00b204e9800998ecf8427e+0",
381 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:
384 <pre><code>~$ <span class="userinput">arv keep ls <b>a01df2f7e5bc1c2ad59c60a837e90dc6+166</b></span>
388 ~$ <span class="userinput">arv-get <b>a01df2f7e5bc1c2ad59c60a837e90dc6+166</b>/stdout.txt</span>
389 2016-08-05T13:53:06.201011Z Hello, Crunch!
393 If the container does not dispatch successfully, refer to the @arvados-dispatch-cloud@ logs for information about why it failed.