Where to find ECMWF's JupyterHub?
Go to https://jupyterhub.ecmwf.int and log in with your ECMWF credentials. You will a second factor authentication Using Time-based One-Time Passwords
ECMWF offers the possibility of using a JupyterLab environment to authorised users. The options available to you will depend on the privileges granted to your user account.
JupyterLab on HPCF or ECS
Who can use it?
You may run a JupyterLab instance on HPCF or ECS if you have access to those services.
JupyterHub offers a novel way to access HPCF or ECS services, connecting you to an interactive JupyterLab session where you can run your Jupyter notebooks, manage your files, and much more.
JupyterLab would effectively run within a job on the Atos HPCF or ECS with dedicated resources on an allocated node for the job, and would allow you to conveniently interact with it from your browser without the need of any other connection to the HPCF using other methods.
Time limited singleton sessions
All JupyterLab sessions running on this service are time limited. When the time is up, the instance will be killed automatically along with any active processing that may be taking place.
You can only have one JupyterLab instance running. If you left one running, JupyterHub will connect you straight back into it.
First use: enabling access to your account from JupyterHub
This is only needed once
Before you can start using this service, you need to enable the access from JupyterHub into your account on the target platform.
A unique SSH key pair is created for this purpose, and you will need to append the generated public SSH key into your ~/.ssh/authorized_keys in your ECMWF HOME space.
You will need to access Atos HPCF, ECS or VDI services via other means. From a terminal in one of those systems, you can then:
$ grep -q $USER@jupyter ~/.ssh/authorized_keys || echo "ssh-ed25519 AAAA...." >> ~/.ssh/authorized_keys
Note you should replace "ssh-ed25519 AAAA...." by the actual value of your SSH key that appears in the JupyterHub portal.
Configuring your JupyterLab session
Select the desired profile in the profile dropdown:
Configure the resources and the time allocated for your session:
Debug output
By default, the session standard output will not be saved. If you run into problems starting JupyterLab, or something does not work as you would expect once within JupyterLab, you may enable the debug option to generate the job output in your HOME directory, which will be directed to a file called userid-jupyterhub-jobid.out.
When you are ready, click Start
You may need to wait between 30 seconds and several minutes for the system to schedule your new job and connect to your new JupyterLab session
After a few minutes, your session will be up and running. Take note of the finishing time at the top right corner of the page. Your session will be terminated automatically once that time is reached.
Stopping your JupyterLab
To stop your JupyterLab session, you may go to the top bar menu, and then click on File - Hub Control Panel
This will bring you back to your JupyterHub Home, from which you will be able to Stop your server (red button) or connect back to it (blue button)
JupyterHub and ecinteractive Jupyter sessions
Since it is also possible to start Jupyter sessions with ecinteractive, you should avoid running two JupyterLabs at the same time with each tool. They run on the same platform using the same HOME filesystem, so you may run into unexpected behaviour or Jupyter cache or configuration corruption.