...
- transfer (if necessary) each dataset to existing cloud architecture - in progress?
- discover mount points for each large dataset within existing cloud architecture - in progress?
- spin up a Docker-enabled host and mount nearby datasets (NFS, direct mount, etc.) - in progress?
- using docker-compose, bring up provided girder-dev on each Docker host - pending
- extend existing ToolManager to receive site metadata - in progress
- modify girder-dev to POST site metadata on startup - in progress
- extend existing ToolManager to delegate tmpnb jobs to remote instances of Girder using existing /notebook API endpoint
- wrap existing ToolManager in a simple auth mechanism
- we simply need to collect an e-mail address (identity) to run things on their behalf
- could we possibly import existing users from Girder using their API? probably not, due to security
- we could callback to Girder when sites push their metadata (assuming this can be done as Girder comes online)
- modify existing ToolManager UI to list off collections in connected Girder instance
- Add a "Launch Notebook" button next to each dataset where no notebook is running
- Add a "Stop Notebook" button next to each dataset where a notebook has been launched
- run a centralized ToolManager instance on Nebula for the purposes of the demo
Using the above we would be able to show:
...