You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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.

Jupyterlab would effectively run within a job on the Atos HPCF or ECS with certain resources on the 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 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. 

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.





  • No labels