Introduction

The Interactive Notebooks Service is based on JupyterHub, enabling remote use of Jupyter Notebooks in a managed environment integrated with other services in EOSC and particularly in the EOSC EU Node.

Location and access

The preferred way of accessing the Interactive Notebooks service is 

Using the Underlying Components

For basic use, refer to user documentation of the component you are working with. Namely, the following building blocks are relevant to your work:

• Jupyter Notebooks Documentation for working with the notebooks

• JupyterLab Documentation for use of the integrated user environment (menus, working tabs, etc.)

• JupyterHub Documentation to manage your remote resources (starting and stopping servers, collaborative sharing, etc.)

• Documentation for your core programming languages:

  • Python

  • Julia

  • R

  • Octave

Additional Features and Integrations

The JupyterHub service is integrated with additional components in the EOSC EU Node ecosystem. The most notable ones relevant to the use of interactive notebooks are:

• Authentication and Authorization -- Interactive Notebooks users need to secure access through the EOSC Portal, and obtain credits for notebooks resource use. Once logged into the environment, a token is available for you to access additional services (compute or data sources) within the ecosystem.

• Sync’n’share storage -- a shared network drive is mounted as your home in Interactive Notebooks, so that your data are always kept safe even if you interrupt your work.

• Add-ons and extensions installed in the environment

  • elyra -- AI Centric extensions to JupyterLab

  • jupyter-resource-usage -- Jupyter Extension to show resource usage

  • nb_conda_kernels -- Launch Jupyter kernels for any installed conda environment

  • nbgitpuller -- Jupyter Extension to do one-way synchronization of git repositories

• Software and libraries

  • An extended list of libraries pre-installed in the environment is provided as a separate document.

FAQ

Certain frequently asked questions are documented in a separate page of FAQs. There is also a common knowledge base for the EOSC EU Node.