Federation implementation roadmap » History » Revision 2
Revision 1 (Tom Clegg, 04/04/2018 03:53 PM) → Revision 2/16 (Peter Amstutz, 07/20/2018 02:29 PM)
h1. Federation implementation roadmap Use a remote-hosted workflow * 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) Mount remote-hosted collection (read-only) in a container * When creating a container to satisfy a CR, API searches for server notices collection PDH UUID in cr.mounts across federated nodes, is remote, and fetches it with salted token (instead of looking in local DB) Run some portions of a CWL workflow on a remote cluster * When submitting container requests, a-c-r follows workflow/commandline/input UUID hints to choose a cluster * 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