Federation implementation roadmap » History » Version 9

Tom Clegg, 08/21/2018 06:30 PM

1 1 Tom Clegg
h1. Federation implementation roadmap
2 1 Tom Clegg
3 6 Tom Clegg
Use a remote-hosted workflow #13493
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 5 Tom Clegg
Mount remote-hosted collection (read-only) - [[Federated collections]]
8 1 Tom Clegg
9 7 Peter Amstutz
* (controller) fetch remote-hosted container by UUID (similar to workflow case) (#13993)
10 7 Peter Amstutz
* (controller) rewrite locators in manifest to indicate remote cluster  (#13993)
11 7 Peter Amstutz
* (keepstore) if locator indicates remote cluster and data does not exist locally (or local signature is not supplied), fetch from remote using salted token (#13994)
12 5 Tom Clegg
13 5 Tom Clegg
Mount remote-hosted collection (read-only) in a container
14 5 Tom Clegg
15 8 Tom Clegg
* When creating a container to satisfy a CR, Rails API assumes any PDH appearing in the CR mounts is OK.
16 8 Tom Clegg
* When running the container, arv-mount (and any other client) will go through the controller to get the collection, and the controller will search the federation for any PDH not found (or not readable by the acting user) in the local DB.
17 1 Tom Clegg
18 1 Tom Clegg
Run some portions of a CWL workflow on a remote cluster
19 1 Tom Clegg
20 9 Tom Clegg
* When submitting container requests, a-c-r follows workflow/commandline/input UUID hints to choose a cluster.
21 9 Tom Clegg
* a-c-r submits CRs to its default cluster with "submit to cluster X" flag, and the controller proxies those requests to remote clusters.