-
Story
-
Resolution: Done
-
Critical
-
None
-
None
Scope of this issue is unclear for documentation. Samu and Andrew are the project leads. Juntao, Don Maros and Vaishnavi are developers as well.
A test day is planned for 21 Jul 2022 to further scope the changes needed. Details here: https://docs.google.com/document/d/1WQL3rKe8ylV6pXtvRfmBS_uzcKNi0eXaWIciXEizBV4/edit?usp=sharing
Some items that need doing:
- Any part of the upgrade that is not automatic or requires preparation to avoid losing data
- All mentions of "JupyterHub" need to change to "Jupyter" (or whatever branding is changed to), both in the documentation and in any UI tutorials / quick starts - we don't need to update the quickstart content, but we should provide review
- As per Kyle's mockup (https://marvelapp.com/prototype/90ii3fd/screen/87164834) the start/stop notebook function and the admin functions will move from JupyterHub into the RHODS Dashboard - the Hub Control Panel menu item should point to the RHODS Dashboard page (Notebook server control panel) - this will also potentially mean a different set of notebooks, Samu is investigating.
- How to access the JH Admin panel will change if we no longer use the JH Hub Control Panel, but not yet clear how this will work - may just be shared with the Notebook server control panel page, but admin functions visible.
- May have new troubleshooting pieces based on error messages, but the next step should be clear from the error message and the UI itself. May be able to review the error messages.
- rhods-notebooks namespace will be created for each user (e.g. rhods-notebooks-username) in order to create isolation - Samu will lodge an issue with the team because OpenShift doesn't operate well with thousands of namespaces, and these namespaces will be largely invisible to data scientist users, but may annoy an admin and will involve changes to instructions.
- STS installations on ROSA may now be supported (depending on resolution of
RHODS-3965) - There are issues declared in the release notes that, once the KF notebook controller has been implemented, could be removed from the known issues. Although clarification is needed.
- mentioned on
(1 mentioned on)