DNAstack/Google write up instructions on how to stand up the golden demo

[briandoconnor]

Two approaches:

• playground approach with non-controlled data
• or code to stand up the system under a users account

We heard interest in both

We heard interest in people using individual components: 1) compute, 2) discovery as a learning exercise

Assign to Ian, Brian O, anyone else?

[ianfore]

Note on components: my advocacy of the component approach is that e.g. as a FASP user I might use two (or more) different WES servers if the data I Discovered were in different locations.

Of the two approaches above, given that controlled access data is central to the FASP use case, showing this works from a users account seems key.

[mbarkley]

May 4, 2020 update:

Going to speak more offline with @ianfore about this. Will try to put aside some time each week to help with this work. Anyone else who is interested please comment here so we can include you in meetings.

@cdvoisin will also be assisting, providing some scripts that exist for some of the repos.

[mbarkley]

Relates to #97

[lpaglione]

I'd love to participate. My schedule gets full, so meetings may be difficult, but happy to help with the writing. (I've been spending some time trying to figure out how to do this on my side.)

[cdvoisin]

The Federated Access components deployment docs cover the Passport Broker, Passport Clearinghouse, and related "playground" components. This gives the capability to generate passports then evaluate them to recieve byte access to cloud buckets.

This repo is only part of the puzzle: it does not include integration with the biomedical platform, search capability, beacon discovery, WES and DRS, etc which exist in other repos. There are no longer current docs on how to use these test components in a stand-alone environment, but the test pages with a hint of "use 'Personal Playground' and 'NCI Researcher' across various prompts when logging in" will allow someone to figure it out. Better docs with screenshots would be good, even as stand-alone components for others to try.