This thread is for brainstorming topics for breakout sessions.
In the end, we aim to coalesce around 4-5 topics. Let us consider suggestions here and then form separate Discourse Topics for each.
I’ll start with one topic on my mind:
Notebook sharing and distribution models
- ways for users to pass notebooks around that’s better than download/email/upload
- ways for scientists at user facilities to distribute examples and templates to their users
- ways for scientists at user facilities to “jump in” to a user’s server and provide support
Jupyterlab + Jupyterhub integration
There are some rough edges when trying to run Jupyterlab in a shared Jupyterhub environment. Start a discussion about solving some of these issues, including
- extensions need to be installed globally. how to support local user installed extensions
- jupyterlabhub UI quirks
- “home” dir access
Ideas for JL extensions that could solve some of our common problems
Improvements & Latest on SLURM spawner
I think there may be a “Binder for HPC resources” i.e. how do you implement Binder-like functionality with a more traditional HPC backend without some of the support for kubernetes etc.
Expanding on this, as I said in my talk, I would very much like to have a round-up on:
Status and future direction of batchspawner and friends
- evaluate needs and pain-points for current and prospective users
- strategies for sustainable development
Jupyter and remote execution models
What are the patterns, solutions or prototypes for spawning remote tasks from a notebook
- Existing models (e.g. Dask)
- Lamda functions
- code cell to remote execution
- Can containers help here?
- Interaction with batch/resource managers
(from Shane Canon, who hit the post limit)
- How should extensions interact with each other and the notebook canvas?
- Are there interface gaps or missing standards?