JupyterLab instance (3)

[huard]

Install and configure JupyterLab to work with PAVICS user accounts and get access to stored data.

• General info: https://blog.jupyter.org/jupyterlab-is-ready-for-users-5a6f039b8906
• Installation instructions: http://jupyterlab.readthedocs.io/en/stable/getting_started/installation.html
• Security: https://jupyter-notebook.readthedocs.io/en/stable/security.html
• Docker container: https://github.com/mikebirdgeneau/jupyterlab-docker

Authentication wish-list:

• JupyterLab and PAVICS share the same credential system, so that logging in one allows user to switch to other without reentering credentials.
• Access to JupyterLab is granted to users through Magpie interface (as another service).

Also install list of packages related to hydrology, and make sure relevant streamflow data is available.

[huard]

In discussion with Syzygy about this. Hold on work for the moment, we might be able to run it directly on CC.

[huard]

Syzygy offered to host a JupyterLab instance for ETS. Following up with ETS.

[huard]

@moulab88 Pas de nouvelles de Syzygy. Je suggère qu'on avance avec le plan de match initial: une instance de JupyterLab sur une machine à Ouranos qui a accès aux ressources de PAVICS.

[moulab88]

Ok, on va avancer avec le plan initial. De : David Huard <[email protected]> Envoyé : 16 octobre 2018 13:27 À : Ouranosinc/pavics-sdi <[email protected]> Cc : Labassi, Mourad <[email protected]>; Mention <[email protected]> Objet : Re: [Ouranosinc/pavics-sdi] JupyterLab instance (3) (#58) @moulab88<https://github.com/moulab88> Pas de nouvelles de Syzygy. Je suggère qu'on avance avec le plan de match initial: une instance de JupyterLab sur une machine à Ouranos qui a accès aux ressources de PAVICS. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#58 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AYFbuDa7likQnxVPYMAzgfBvsMPKOup7ks5ulhbOgaJpZM4UVb1d>.

[huard]

Mourad, est-ce que tu vas pouvoir installer https://github.com/bird-house/birdy dans l'environnement python disponible sur JupyterLab ? On va s'en servir pour interfacer avec les WPS sur PAVICS.

[moulab88]

Ok, je vais voir comment je peux l'installer.

[moulab88]

Birdy est maintenant installé sur:
https://medus.ouranos.ca:9443/hub/login
et
https://jphub.ouranos.ca/hub/login /* The Littlest JupyterHub */
Notebook: Python 3.6 (Birdy)

[tomLandry]

@huard next steps here? fully in scope of PAVICS-Hydro too, right?

[huard]

Next step would be to go from a jupyterhub to a jupyterlab installation that uses the same credentials as the main PAVICS platform.

[huard]

@tomLandry CRIM's mandate here would be to support the JupyterLab service in Magpie and hide it behind the twitcher proxy (to be validated by CRIM to make sure that makes sense).

[tomLandry]

@dbyrns C'est du travail à la fois utile (et facturable) sur PAVICS-Hydro et OGC-DOE dépendamment de où on part. Dans les deux cas, on veut livrer d'ici avril. David Caron serait bien placé pour réaliser une bonne partie des travaux.

[dbyrns]

Our latest version of Magpie is able to protect arbitrary endpoint without any particular protocol. So you can configure it to protect the endpoint hostname:port/path/to/jupiter/lab and give permission to it or not.
Is it enough for what you have in mind?

[dbyrns]

You can look at https://colibri.crim.ca/magpie/ui/services/access for example

[huard]

I think so. Great !
Link doesn't work for me.

[dbyrns]

David, you will need to log into magpie prior to access that section.

[dbyrns]

I talked to @fmigneault and the required feature has been introduce in version 0.6.1
Starting from master we would need to apply the following diff :
git diff master..786d7d9b22516eb7b3bf8ab387360de0a462887b (only twitcher/magpie related stuff).
The develop version of magpie (0.7.3) has breaking changes that would require update in the frontend but if this feature is required I would take the chance to test the 0.6.1 version.
Until the end of march it would be hard for us to help on that topic so you're welcome if you want to take the lead on that.

[huard]

Thanks! Ok, we first need to install a working JupyterLab instance on our end.

[tlvu]

@huard, @dbyrns: to close this issue, especially the part about the authentication wish-list:

• JupyterLab and PAVICS share the same credential system, so that logging in one allows user to switch to other without reentering credentials.
• Access to JupyterLab is granted to users through Magpie interface (as another service).

Are we aiming to deploy the current state of PAVICS of master branch (magpie 0.4.5) or develop branch (magpie 0.7.3)? Note a lot of other pieces are also different between master and develop branch.

Consider full PAVICS stack testing effort if we use the develop branch and/or magpie backport effort (Ouranosinc/Magpie#171, Ouranosinc/Magpie#172, possibly what will fall out of Ouranosinc/Magpie#174) if use the much older master branch.

[huard]

Ideally we would keep track of the upstream development at CRIM. We did not have the resources to do it so far, but we do now. Better spend time catching up than backporting.

[dbyrns]

Latest work has never been consolidated, so we expect some components incompatibility in their latest version. We should fix our priorities soon for the DACCS project and hopefully merge back all the pending branches to a working set. The fact that you have the resources on your side too is even better.

[tlvu]

Given the blocking issues with Magpie that prevent shared authentication between Magpie and JupiterHub, we will go forward with deploying JupyterHub on PAVICS but without authentication integration with Magpie. We will integrate JupyterHub authentication with Magpie at a later time.

[tlvu]

An instance of JupyterHub has been added to PAVICS. It has only 1 public user. Authentication integration with Magpie will be done at a later time once the blocking issues with Magpie can be resolved. No other components of PAVICS has been updated since JupyterHub so not need any changes in them.

All the jupyter notebooks in this pavics-sdi repo (docs/source/notebooks) can be run.

Closing this issue.