JupyterHub has the ability to run with end-to-end SSL if your spawners support it. What spawners currently in use at HPC and user facilities are configured this way and can we see examples of how to handle it?
How can we enable more detailed audit? There seem to be places in notebook and terminado that could be used to log commands to syslog; there’s at least one potential PR about this in notebook I think. Is it feasible to identify all these points where code is going to kernels (in whatever language) and log those?
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
An extension to track HPC system activity - job state, run time, queues, etc.
Tools to interact with jobs - our (DoE KBase) users have a range of backgrounds and needs, and just giving terminal access doesn’t always serve them best.
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.