-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jupyter notebook support #574
Conversation
50c6704
to
1595a7c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not fully finished with this PR yet as I still have to test it out and have to review the k8s.py
but here are already my comments for the other files.
Many comments are related to the fact that you not only added jupyter as a tool but also provided a integration flag for it. I am not sure why this is needed and it feels like we can simply remove it, so I added a comment in all the files that would be affected by that (hopefully I didn't miss one).
backend/capellacollab/alembic/versions/61d36288afe9_define_jupyter_as_integration.py
Show resolved
Hide resolved
backend/capellacollab/alembic/versions/f3d2dedd7906_commit_message.py
Outdated
Show resolved
Hide resolved
...p/settings/core/tools-settings/tool-details/tool-integrations/tool-integrations.component.ts
Show resolved
Hide resolved
c5889f9
to
453a745
Compare
If not done yet: Please test it in our OpenShift development cluster.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Finished the review of the k8s operator but as the backend is currently not starting I can't really test the jupyter sessions. So please fix the backend issue first.
6f78534
to
8b3747d
Compare
Works. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Add release notes
- Restructure / Add user documentation. Right now, it'd focused on Capella sessions.
9128e5b
to
734fb80
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great addition, our list of supported tools starts growing 🥳
It has a lot of Capella specific parameters.
We should already be there.
Co-authored-by: dominik003 <[email protected]>
Co-authored-by: dominik003 <[email protected]>
Let's raise an error if the expected port is not found.
So we can use routes on openshift to expose Jupyter to users.
Needed for Jupyter session in OpenShift.
Makes more sense, since it's jupyter specific.
So it's version is in line with the Capella version.
Not needed for jupyter notebooks, and as it turns out, we also do not need it for our local (k3d) cluster setup.
They were separated in part, now the cut is even more clear.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is ready for merge. However, I'd wait until DSD-DBS/capella-dockerimages#108 is merged.
Thanks again for the implementation, @amolenaar! 😃
|
Add support for Jupyter notebooks
Changes include:
Postponed/to be picked up separately:
Requires: DSD-DBS/capella-dockerimages#108