Federation use cases » History » Version 2

Tom Clegg, 06/26/2017 03:29 PM

1 1 Tom Clegg
h1. Federation use cases
2 1 Tom Clegg
3 1 Tom Clegg
I can view/edit any Arvados object I want, just based on its UUID or PDH -- no mucking about with credentials / environment variables to select a specific cluster.
4 1 Tom Clegg
 
5 1 Tom Clegg
I can do a search on multiple sites at once, and show the combined results.
6 1 Tom Clegg
 
7 1 Tom Clegg
I can see a web dashboard with all the stuff I’m working on (even though it’s spread over various clusters).
8 1 Tom Clegg
 
9 1 Tom Clegg
I can move my “home” account from one cluster to another.
10 1 Tom Clegg
 
11 1 Tom Clegg
I can run a container on a private site that accesses data from both private and public sites.
12 1 Tom Clegg
 
13 1 Tom Clegg
On a public site, I can share files/objects with a user who has never logged into this site (but does have an arvados account somewhere else).
14 1 Tom Clegg
 
15 1 Tom Clegg
I can create a project that contains projects/items from various other clusters (so I can share/unshare all that stuff as one logical unit).  All of the contained items appear on the “show project” page even though they are from different clusters.
16 1 Tom Clegg
 
17 1 Tom Clegg
I can share files/objects on one cluster with a group that is defined on a different cluster.
18 1 Tom Clegg
 
19 1 Tom Clegg
I can develop a workflow on private site A, and easily move it to private site B when it’s ready.
20 1 Tom Clegg
 
21 1 Tom Clegg
I can browse/select/use a public workflow (site A) on a private site (B), using some private data from B and the public data on site A, without actually copying the data from A to B.
22 2 Tom Clegg
23 2 Tom Clegg
I can push code to a git repository on a public site and use it directly from a container running on a private site.