Federation implementation roadmap » History » Version 3

Peter Amstutz, 08/01/2018 05:55 PM

1 1 Tom Clegg
h1. Federation implementation roadmap
2 1 Tom Clegg
3 1 Tom Clegg
Use a remote-hosted workflow
4 1 Tom Clegg
5 1 Tom Clegg
* When retrieving a workflow record for arvados-cwl-runner, API server notices workflow UUID is remote, and fetches it with salted token (instead of looking in local DB)
6 1 Tom Clegg
7 1 Tom Clegg
Mount remote-hosted collection (read-only) in a container
8 1 Tom Clegg
9 2 Peter Amstutz
* When creating a container to satisfy a CR, API searches for collection PDH in cr.mounts across federated nodes, and fetches it with salted token (instead of looking in local DB)
10 3 Peter Amstutz
* [[Federated collections]]
11 1 Tom Clegg
12 1 Tom Clegg
Run some portions of a CWL workflow on a remote cluster
13 1 Tom Clegg
14 1 Tom Clegg
* When submitting container requests, a-c-r follows workflow/commandline/input UUID hints to choose a cluster
15 1 Tom Clegg
* Either a-c-r handles the multi-cluster stuff itself, or it submits CRs with "submit to cluster X" flag, and the API server acts as a proxy