Last modified by adietz on 2019/07/18 16:38
From version 3.2
edited by adietz
on 2019/07/18 16:38
Change comment: Added comment
To version 1.4
edited by villemai
on 2019/06/06 16:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.adietz
1 +XWiki.villemai
Content
... ... @@ -3,27 +3,8 @@
3 3  (% class="text-uppercase" %)Draft
4 4  )))
5 5  
6 -(% class="box infomessage" %)
7 -(((
8 -This document will address an initial release of jupyterlabs within the Collaboratory 2.0. In order to provide something quickly, this release will be limited in scope. Long term planning can be discussed [[here>>doc:Collabs.jupyter-user-group.Long term goals.WebHome]].
9 -)))
10 -
11 11  = JupyterHub Deployment Proposal =
12 12  
13 -This page describes the proposed JuptyerHub setup that will be offered as part of the "scientific release" of the Collaboratory 2.0 planned for Q3 2019.
14 -
15 -The initial release should allow users to run notebooks in the Collaboratory 2.0 environment. The following features should be available from the start:
16 -
17 -* integration with the drive should be available, providing access to notebooks and data which are stored there and accessible by the user;
18 -* integration with the user's IAM account and OAuth tokens;
19 -* example notebooks to showcase some possibilities;
20 -* notebook versioning (limited);
21 -* preinstalled scientific and neuroscience libraries in a notebook container image; (libraries TBD).
22 -
23 -The goal is to allow users to create new notebooks on the Collaboratory 2.0 platform and to migrate some, but not all, notebooks from the old Collaboratory to the new platform. Migrating notebooks might require some changes, especially with regards to the storage, but also with regards to the libraries used to access certain services and the access of services themselves.
24 -
25 -The new JupyterHub deployment will not be fully compatible with the old environment. The storage model will change significantly. Certain libraries will no longer be available. Python 2 support needs to be evaluated (see the note at the bottom).
26 -
27 27  == Architecture ==
28 28  
29 29  * Based on Kubernetes
... ... @@ -43,7 +43,7 @@
43 43  == Features ==
44 44  
45 45  * TBD: requirements management (how to manage python libraries and other dependencies).
46 -* TBD: Versioning of notebooks. Initially, this will only be through the versioning available in seafile.
27 +* TBD: Versioning of notebooks
47 47  * TBD: Workflows
48 48  
49 49  == Notes ==
XWiki.XWikiComments[0]
Date
... ... @@ -1,1 +1,0 @@
1 -2019-07-18 16:38:47.0
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.adietz
Comment
... ... @@ -1,20 +1,0 @@
1 -Question on the features:
2 -
3 -1. 'notebook versioning': How is that feature supposed to be implemented?
4 -
5 -A use case could be as follows:
6 - a) A user clones a notebook in a Collab to do some work
7 - b) The user wants to check if a newer version of the original notebook exists.
8 - c) Finally, the user might want to replace his cloned notebok by the new one
9 -
10 -
11 -2. 'preinstalled scientific and neuroscience libraries in a notebook container image;': What do I understand for that feature? Will the notebook be run in an virtual environment which the user can set up? That would be the best solution:
12 -
13 - - A user can use different notebooks with different library setups, without the need to re-install all libraries all the time he/she switched the notebook
14 - - When a different user uses a notebook from the first user, everything is set up, and the different user does not need to spend time on installing things.
15 -
16 -3. Will there be a guide or a tool that can be used to convert Collab1 notebooks to Collab2?
17 -
18 -4. It would be really useful if some basic features regarding the jupyter integration will be ready for end of November to be shown at the CodeJam.
19 -
20 -