To support running analysis on geographically dispersed data (avoiding expensive data transfers by sending the computation to the data), and “hybrid cloud” configurations where an on-premise cluster can expand its capabilities by delegating work to a cloud-hosted cluster, Arvados supports federated workflows. In a federated workflow, different steps of a workflow may execute on different clusters. Arvados manages data transfer and delegation of credentials, so that all that is required is adding arv:ClusterTarget hints to your existing workflow.
For more information, visit the architecture and admin sections about Arvados federation.
The tutorial files are located in the documentation section of the Arvados source repository: or see below
~$ git clone https://github.com/curoverse/arvados ~$ cd arvados/doc/user/cwl/federated
At this time, remote steps of a workflow on Workbench are not displayed. As a workaround, you can find the UUIDs of the remote steps in the live logs of the workflow runner (the “Logs” tab). You may visit the remote cluster’s workbench and enter the UUID into the search box to view the details of the remote step. This will be fixed in a future version of workbench.
Run it like any other workflow:
~$ arvados-cwl-runner federated.cwl shards.cwl
You can also run a workflow on a remote federated cluster .
In this following example, an analysis task is executed on three different clusters with different data, then the results are combined to produce the final output.
Example input document:
shards: - cluster: clsr1 project: clsr1-j7d0g-qxc4jcji7n4lafx file: class: File location: keep:485df2c5cec3207a32f49c42f1cdcca9+61/file-on-clsr1.dat - cluster: clsr2 project: clsr2-j7d0g-ivdrm1hyym21vkq file: class: File location: keep:ae6e9c3e9bfa52a0122ecb489d8198ff+61/file-on-clsr2.dat - cluster: clsr3 project: clsr3-j7d0g-e3njz2s53lyb0ka file: class: File location: keep:0b43a0ef9ea592d5d7b299978dfa8643+61/file-on-clsr3.dat
The content of this documentation is licensed under the
Commons Attribution-Share Alike 3.0 United States licence.
Code samples in this documentation are licensed under the Apache License, Version 2.0.