--- /dev/null
+../user/cwl/federated/federated.cwl
\ No newline at end of file
--- /dev/null
+../user/cwl/federated/shards.yml
\ No newline at end of file
SPDX-License-Identifier: CC-BY-SA-3.0
{% endcomment %}
-Arvados supports federated workflows, where different step of a running workflow execute on different clusters. This supports running analysis on geographically dispersed data (avoiding expensive data transfers by sending the computation to the data) or in "hybrid cloud" configurations where an on-premise cluster can expand its capabilities by sending work to a cloud-base cluster.
+Arvados supports federated workflows, where different steps of a running workflow may execute on different clusters. Arvados manages data transfer and delegation of credentials, so this as easy as simply adding cluster target hints to your existing workflow. This supports 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-base cluster.
h2. Federated scatter/gather example
-<pre>
-</pre>
+{% codeblock as yaml %}
+{% include 'federated_cwl' %}
+{% endcodeblock %}
-<pre>
-</pre>
+{% codeblock as yaml %}
+{% include 'shards_yml' %}
+{% endcodeblock %}
DockerRequirement:
dockerPull: arvados/fed-test:scatter-gather
ScatterFeatureRequirement: {}
+ StepInputExpressionRequirement: {}
SchemaDefRequirement:
types:
- name: FileOnCluster
--- /dev/null
+file-on-clsr1.dat
--- /dev/null
+file-on-clsr2.dat
--- /dev/null
+file-on-clsr3.dat
- cluster: clsr1
file:
class: File
- location: file-on-clsr1.dat
+ location: keep:485df2c5cec3207a32f49c42f1cdcca9+61/file-on-clsr1.dat
+
- cluster: clsr2
file:
class: File
- location: file-on-clsr2.dat
+ location: keep:ae6e9c3e9bfa52a0122ecb489d8198ff+61/file-on-clsr2.dat
+
- cluster: clsr3
file:
class: File
- location: file-on-clsr3.dat
+ location: keep:0b43a0ef9ea592d5d7b299978dfa8643+61/file-on-clsr3.dat