...
- Transfer (if necessary) each dataset to existing cloud architecture - in progress?
- Spin up a Docker-enabled host and mount nearby datasets (NFS, direct mount, etc.) - in progress?
- Federated model
- Using docker-compose, bring up provided girder-dev environment on each Docker host - pending
- Develop the "resolver" REST API to to
- Receive site metadata - in progressin - done => POST to /datasets
- Delegate tmpnb requests to remote Girder instances using existing /notebook API endpoint - done => POST to /resolve/:id
- Add authentication:
- We simply need to collect an e-mail address (identity) to run things on their behalf
- Could 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)
- Extend UI to list off collections in connected Girder instance - doneish... very primitive, but styling it is trivial
- Add a "Launch Notebook" button next to each dataset where no notebook is running - doneish... prototype is working, once real metadata is in place this is trivial
- Add a "Stop Notebook" button next to each dataset where a notebook has been launched - TBD
- this is a slightly tougher problem, as we now need to call out to every Girder's /notebook endpoint
- Modify girder-dev to POST site metadata on startup (feder8)- in progress
- Run a centralized resolver instance on Nebula for the purposes of the demo
...