Skip to content
Snippets Groups Projects
Commit 0b59e56e authored by Marco Del Tufo's avatar Marco Del Tufo
Browse files

Update jupiterhub-for-openbis.md

parent cd3965be
No related branches found
No related tags found
1 merge request!40SSDM-13578 : 2PT : Database and V3 Implementation - include the new AFS "free"...
Hide whitespace changes
Inline Side-by-side
docs/user-documentation/advance-features/jupiterhub-for-openbis.md
+ 124
− 109
View file @ 0b59e56e
...@@ -54,30 +54,25 @@ execute the images. ...@@ -54,30 +54,25 @@ execute the images.
locally like any other Docker Hub image. locally like any other Docker Hub image.
3. **openBIS installation** (optional). 3. **openBIS installation** (optional).
How to run the official JupyterHub for openBIS image in your local machine How to run the official JupyterHub for openBIS image in your local machine
-------------------------------------------------------------------------- --------------------------------------------------------------------------
1. After downloading the jupyterhub-openbis, find the id of your image.
1\. After downloading the jupyterhub-openbis, find the id of your image.
```bash ```bash
$ docker images $ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE REPOSITORY TAG IMAGE ID CREATED SIZE
openbis/jupyterhub-openbis-sis-20180405 latest 585a9adf333b 23 hours ago 4.75GB openbis/jupyterhub-openbis-sis-20180405 latest 585a9adf333b 23 hours ago 4.75GB
``` ```
2\. Run the image with one of the two following commands: 2. Run the image with one of the two following commands:
a\. if you want to connect to your productive openBIS instance (e.g. a. if you want to connect to your productive openBIS instance (e.g.
https://openbis-elnlims.ch), use the following command: https://openbis-elnlims.ch), use the following command:
docker run -e OPENBIS_URL=https://openbis-elnlims.ch -e JUPYTERHUB_INTEGRATION_SERVICE_PORT=8002 -e JUPYTERHUB_PORT=8000 -e CERTIFICATE_KEY=/vagrant/config/certificates/default.key -e CERTIFICATE_CRT=/vagrant/config/certificates/default.crt -p 8000:8000 -p 8081:8081 -p 8001:8001 -p 8002:8002 585a9adf333b ./vagrant/initialize/start_jupyterhub.sh docker run -e OPENBIS_URL=https://openbis-elnlims.ch -e JUPYTERHUB_INTEGRATION_SERVICE_PORT=8002 -e JUPYTERHUB_PORT=8000 -e CERTIFICATE_KEY=/vagrant/config/certificates/default.key -e CERTIFICATE_CRT=/vagrant/config/certificates/default.crt -p 8000:8000 -p 8081:8081 -p 8001:8001 -p 8002:8002 585a9adf333b ./vagrant/initialize/start_jupyterhub.sh
b\. if you have a local openBIS installation for testing, you can run b. if you have a local openBIS installation for testing, you can run
the following command: the following command:
docker run -v /Users/juanf/jupyterhub-local/home:/home -v /Users/juanf/jupyterhub-local/config/certificates:/vagrant/config/certificates -e OPENBIS_URL=https://129.132.228.42:8443 -e JUPYTERHUB_INTEGRATION_SERVICE_PORT=8002 -e JUPYTERHUB_PORT=8000 -e CERTIFICATE_KEY=/vagrant/config/certificates/default.key -e CERTIFICATE_CRT=/vagrant/config/certificates/default.crt -p 8000:8000 -p 8081:8081 -p 8001:8001 -p 8002:8002 585a9adf333b ./vagrant/initialize/start_jupyterhub.sh docker run -v /Users/juanf/jupyterhub-local/home:/home -v /Users/juanf/jupyterhub-local/config/certificates:/vagrant/config/certificates -e OPENBIS_URL=https://129.132.228.42:8443 -e JUPYTERHUB_INTEGRATION_SERVICE_PORT=8002 -e JUPYTERHUB_PORT=8000 -e CERTIFICATE_KEY=/vagrant/config/certificates/default.key -e CERTIFICATE_CRT=/vagrant/config/certificates/default.crt -p 8000:8000 -p 8081:8081 -p 8001:8001 -p 8002:8002 585a9adf333b ./vagrant/initialize/start_jupyterhub.sh
...@@ -115,7 +110,9 @@ It can probably be done but we are currently not supporting it. ...@@ -115,7 +110,9 @@ It can probably be done but we are currently not supporting it.
### Check Available Octave Libraries ### Check Available Octave Libraries
pkg list ```bash
pkg list
```
![image info](img/232.png) ![image info](img/232.png)
...@@ -125,15 +122,15 @@ It can probably be done but we are currently not supporting it. ...@@ -125,15 +122,15 @@ It can probably be done but we are currently not supporting it.
### Check Available Python 3 Libraries ### Check Available Python 3 Libraries
pip freeze ```bash
pip freeze
```
![image info](img/244.png) ![image info](img/244.png)
### Add Python 3 Library ### Add Python 3 Library
1\. Use pip install as you would normally do. The Python 3 kernel often 1. Use pip install as you would normally do. The Python 3 kernel often
doesn't need to be restarted to pick up new libraries, but is doesn't need to be restarted to pick up new libraries, but is
recommended to do so. recommended to do so.
...@@ -148,7 +145,7 @@ recommended to do so. ...@@ -148,7 +145,7 @@ recommended to do so.
### Add R Library ### Add R Library
1\. Use the install command as you would normally do. The R kernel needs 1. Use the install command as you would normally do. The R kernel needs
to be restarted to pick up new libraries. to be restarted to pick up new libraries.
![image info](img/266.png) ![image info](img/266.png)
...@@ -156,28 +153,34 @@ to be restarted to pick up new libraries. ...@@ -156,28 +153,34 @@ to be restarted to pick up new libraries.
Modify a currently running container - From Console (for admins) Modify a currently running container - From Console (for admins)
---------------------------------------------------------------- ----------------------------------------------------------------
1\. Find the container id of the image currently running. 1. Find the container id of the image currently running.
$ docker ps ```bash
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES $ docker ps
a2b76d1dd204 jupyterhub-openbis-sis-20180405 "./vagrant/initial..." 4 seconds ago Up 2 seconds 0.0.0.0:8000-8002->8000-8002/tcp, 0.0.0.0:8081->8081/tcp nervous_leakey CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a2b76d1dd204 jupyterhub-openbis-sis-20180405 "./vagrant/initial..." 4 seconds ago Up 2 seconds 0.0.0.0:8000-8002->8000-8002/tcp, 0.0.0.0:8081->8081/tcp nervous_leakey
```
2\. Log into the container. 2. Log into the container.
$ docker exec -it a2b76d1dd204 bash ```bash
$ docker exec -it a2b76d1dd204 bash
```
### Add Python Library ### Add Python Library
Add a new library to Python 3 Add a new library to Python 3
# First we should move to the environment used by JupyterHub ```bash
[root@a2b76d1dd204 /]# export PATH=/vagrant_installation/miniconda3/bin:$PATH # First we should move to the environment used by JupyterHub
[root@a2b76d1dd204 /]# export LC_ALL=en_US.utf8 [root@a2b76d1dd204 /]# export PATH=/vagrant_installation/miniconda3/bin:$PATH
[root@a2b76d1dd204 /]# export LANG=en_US.utf8 [root@a2b76d1dd204 /]# export LC_ALL=en_US.utf8
# Install a new python lib using pip [root@a2b76d1dd204 /]# export LANG=en_US.utf8
[root@a2b76d1dd204 /]# python --version # Install a new python lib using pip
Python 3.6.4 :: Anaconda, Inc. [root@a2b76d1dd204 /]# python --version
[root@a2b76d1dd204 /]# pip install prettytable Python 3.6.4 :: Anaconda, Inc.
[root@a2b76d1dd204 /]# pip install prettytable
```
This type of changes can be validated straightaway in JupyterHub, by This type of changes can be validated straightaway in JupyterHub, by
just starting a Python 3 notebook. Other changes could require to reboot just starting a Python 3 notebook. Other changes could require to reboot
...@@ -194,13 +197,15 @@ lost. ...@@ -194,13 +197,15 @@ lost.
Add a new library to R Add a new library to R
# First we should move to the environment used by JupyterHub ```bash
[root@a2b76d1dd204 /]# export PATH=/vagrant_installation/miniconda3/bin:$PATH # First we should move to the environment used by JupyterHub
[root@a2b76d1dd204 /]# export LC_ALL=en_US.utf8 [root@a2b76d1dd204 /]# export PATH=/vagrant_installation/miniconda3/bin:$PATH
[root@a2b76d1dd204 /]# export LANG=en_US.utf8 [root@a2b76d1dd204 /]# export LC_ALL=en_US.utf8
# Install a new r lib using conda [root@a2b76d1dd204 /]# export LANG=en_US.utf8
[root@a2b76d1dd204 /]# sudo conda list r- # Install a new r lib using conda
[root@a2b76d1dd204 /]# sudo conda install -c r -y r-base64enc [root@a2b76d1dd204 /]# sudo conda list r-
[root@a2b76d1dd204 /]# sudo conda install -c r -y r-base64enc
```
This type of changes can be validated straightaway in JupyterHub, by This type of changes can be validated straightaway in JupyterHub, by
just starting a R notebook. Other changes could require to reboot just starting a R notebook. Other changes could require to reboot
...@@ -210,26 +215,22 @@ JupyterHub. ...@@ -210,26 +215,22 @@ JupyterHub.
### Save the state of a running container as a new image ### Save the state of a running container as a new image
If you know that you have made significant changes that you want to keep If you know that you have made significant changes that you want to keep
until you build a new docker recipe, you have the option to save the until you build a new docker recipe, you have the option to save the
running container as a new image. running container as a new image.
```bash
bs-mbpr28:jupyterhub_reference_installation juanf$ docker ps
bs-mbpr28:jupyterhub_reference_installation juanf$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a2b76d1dd204 jupyterhub-openbis-sis-20180405 "./vagrant/initial..." 37 minutes ago Up 37 minutes 0.0.0.0:8000-8002->8000-8002/tcp, 0.0.0.0:8081->8081/tcp lucid_stonebraker
a2b76d1dd204 jupyterhub-openbis-sis-20180405 "./vagrant/initial..." 37 minutes ago Up 37 minutes 0.0.0.0:8000-8002->8000-8002/tcp, 0.0.0.0:8081->8081/tcp lucid_stonebraker
$ docker commit a2b76d1dd204 jupyterhub-openbis-sis-juanextensions-20180406
sha256:5dd0036664c75a21d6a62b80bf5780e70fcad345bb12a7ad248d01e29a3caa99
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
jupyterhub-openbis-sis-juanextensions-20180406 latest 5dd0036664c7 4 seconds ago 4.75GB
jupyterhub-openbis-sis-20180405 latest 585a9adf333b 23 hours ago 4.75GB
$ docker commit a2b76d1dd204 jupyterhub-openbis-sis-juanextensions-20180406
sha256:5dd0036664c75a21d6a62b80bf5780e70fcad345bb12a7ad248d01e29a3caa99
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
jupyterhub-openbis-sis-juanextensions-20180406 latest 5dd0036664c7 4 seconds ago 4.75GB
jupyterhub-openbis-sis-20180405 latest 585a9adf333b 23 hours ago 4.75GB
```
Extend a docker image using a docker recipe (for maintenance) Extend a docker image using a docker recipe (for maintenance)
------------------------------------------------------------- -------------------------------------------------------------
...@@ -240,13 +241,15 @@ latest official docker image distributed by SIS. ...@@ -240,13 +241,15 @@ latest official docker image distributed by SIS.
Using our last example, let's create a file called "Dockerfile" and with Using our last example, let's create a file called "Dockerfile" and with
the content shown below. the content shown below.
# vim:set ft=dockerfile: ```bash
FROM openbis/jupyterhub-openbis-sis-20180405 # vim:set ft=dockerfile:
## Adding Python 3 library FROM openbis/jupyterhub-openbis-sis-20180405
RUN export PATH=/vagrant_installation/miniconda3/bin:$PATH && \ ## Adding Python 3 library
export LC_ALL=en_US.utf8 && \ RUN export PATH=/vagrant_installation/miniconda3/bin:$PATH && \
export LANG=en_US.utf8 && \ export LC_ALL=en_US.utf8 && \
pip install prettytable export LANG=en_US.utf8 && \
pip install prettytable
```
Please change the name of the image in the file to the one you are Please change the name of the image in the file to the one you are
using. using.
...@@ -256,51 +259,56 @@ the official repository. ...@@ -256,51 +259,56 @@ the official repository.
> :warning: **It is best practice to include both the name of the user and the creation date in the image name. This will help when dealing with many versions created by different users at different times**. > :warning: **It is best practice to include both the name of the user and the creation date in the image name. This will help when dealing with many versions created by different users at different times**.
$ docker build -t jupyterhub-openbis-sis-juanextensions-recipe-20180406 . ```bash
Sending build context to Docker daemon 4.957GB $ docker build -t jupyterhub-openbis-sis-juanextensions-recipe-20180406 .
Step 1/2 : FROM openbis/jupyterhub-openbis-sis-20180405 Sending build context to Docker daemon 4.957GB
.... Step 1/2 : FROM openbis/jupyterhub-openbis-sis-20180405
Step 2/2 : RUN export PATH=/vagrant_installation/miniconda3/bin:$PATH && export LC_ALL=en_US.utf8 && export LANG=en_US.utf8 && pip install prettytable ....
.... Step 2/2 : RUN export PATH=/vagrant_installation/miniconda3/bin:$PATH && export LC_ALL=en_US.utf8 && export LANG=en_US.utf8 && pip install prettytable
Successfully tagged jupyterhub-openbis-sis-juanextensions-recipe-20180406:latest ....
Successfully tagged jupyterhub-openbis-sis-juanextensions-recipe-20180406:latest
The new image is now available and can be started as described above. The new image is now available and can be started as described above.
$ docker images $ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE REPOSITORY TAG IMAGE ID CREATED SIZE
jupyterhub-openbis-sis-juanextensions-recipe-20180406 latest a0106501b223 3 minutes ago 4.75GB jupyterhub-openbis-sis-juanextensions-recipe-20180406 latest a0106501b223 3 minutes ago 4.75GB
openbis/jupyterhub-openbis-sis-20180405 latest 585a9adf333b 23 hours ago 4.75GB openbis/jupyterhub-openbis-sis-20180405 latest 585a9adf333b 23 hours ago 4.75GB
```
How to start a jupyterhub-openbis docker image on a productive JupyterHub server How to start a jupyterhub-openbis docker image on a productive JupyterHub server
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
> :warning: **You can only have **ONE** jupyterhub-openbis image running on a server at one given time, since JupyterHub makes use of certain ports on the machine that are also configured in openBIS**. > :warning: **You can only have **ONE** jupyterhub-openbis image running on a server at one given time, since JupyterHub makes use of certain ports on the machine that are also configured in openBIS**.
1. Find the jupyterhub-openbis-start.sh file in your server (please ask 1. Find the jupyterhub-openbis-start.sh file in your server (please ask
your admin). your admin).
2\. Find the container id of the image that is currently running. 2. Find the container id of the image that is currently running.
$ docker ps $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a2b76d1dd204 jupyterhub-openbis-sis-20180405 "./vagrant/initial..." 4 seconds ago Up 2 seconds 0.0.0.0:8000-8002->8000-8002/tcp, 0.0.0.0:8081->8081/tcp nervous_leakey a2b76d1dd204 jupyterhub-openbis-sis-20180405 "./vagrant/initial..." 4 seconds ago Up 2 seconds 0.0.0.0:8000-8002->8000-8002/tcp, 0.0.0.0:8081->8081/tcp nervous_leakey
3\. Stop the current container. 3. Stop the current container.
$ docker kill a2b76d1dd204 $ docker kill a2b76d1dd204
a2b76d1dd204 a2b76d1dd204
4\. Edit the jupyterhub-openbis-start.sh file in your server and update 4. Edit the jupyterhub-openbis-start.sh file in your server and update
the name of the image it runs to the one of your choice the name of the image it runs to the one of your choice
docker run -v /Users/juanf/Documents/programming/git/jupyter-openbis-integration/jupyterhub_reference_installation/home:/home -v /Users/juanf/Documents/programming/git/jupyter-openbis-integration/jupyterhub_reference_installation/vagrant/config/certificates:/vagrant/config/certificates -e OPENBIS_URL=https://129.132.229.37:8443 -e JUPYTERHUB_INTEGRATION_SERVICE_PORT=8002 -e JUPYTERHUB_PORT=8000 -e CERTIFICATE_KEY=/vagrant/config/certificates/default.key -e CERTIFICATE_CRT=/vagrant/config/certificates/default.crt -p 8000:8000 -p 8081:8081 -p 8001:8001 -p 8002:8002 jupyterhub-openbis-sis-20180405 ./vagrant/initialize/start_jupyterhub.sh ```bash
docker run -v /Users/juanf/Documents/programming/git/jupyter-openbis-integration/jupyterhub_reference_installation/home:/home -v /Users/juanf/Documents/programming/git/jupyter-openbis-integration/jupyterhub_reference_installation/vagrant/config/certificates:/vagrant/config/certificates -e OPENBIS_URL=https://129.132.229.37:8443 -e JUPYTERHUB_INTEGRATION_SERVICE_PORT=8002 -e JUPYTERHUB_PORT=8000 -e CERTIFICATE_KEY=/vagrant/config/certificates/default.key -e CERTIFICATE_CRT=/vagrant/config/certificates/default.crt -p 8000:8000 -p 8081:8081 -p 8001:8001 -p 8002:8002 jupyterhub-openbis-sis-20180405 ./vagrant/initialize/start_jupyterhub.sh
```
5\. Start the new image. 5. Start the new image.
$ ./jupyterhub-openbis-start.sh ```bash
$ ./jupyterhub-openbis-start.sh
```
Other useful Docker commands Other useful Docker commands
---------------------------- ----------------------------
...@@ -309,31 +317,39 @@ Other useful Docker commands ...@@ -309,31 +317,39 @@ Other useful Docker commands
> :warning: **It is best practice to include both the name of the user and the creation date in the image name. This will help when dealing with many versions created by different users at different times**. > :warning: **It is best practice to include both the name of the user and the creation date in the image name. This will help when dealing with many versions created by different users at different times**.
$ docker save jupyterhub-openbis-sis-20180405 > jupyterhub-openbis-sis-20180405.tar ```bash
$ ls -lah $ docker save jupyterhub-openbis-sis-20180405 > jupyterhub-openbis-sis-20180405.tar
total 9681080 $ ls -lah
-rw-r--r-- 1 juanf 1029 4.6G Apr 5 15:38 jupyterhub-openbis-sis-20180405.tar total 9681080
-rw-r--r-- 1 juanf 1029 4.6G Apr 5 15:38 jupyterhub-openbis-sis-20180405.tar
```
### Load an image from a tar file ### Load an image from a tar file
$ docker load < jupyterhub-openbis-sis-20180405.tar ```bash
8feeda13d3ce: Loading layer [==================================================>] 27.65kB/27.65kB $ docker load < jupyterhub-openbis-sis-20180405.tar
622cd2c170f3: Loading layer [==================================================>] 152MB/152MB 8feeda13d3ce: Loading layer [==================================================>] 27.65kB/27.65kB
633fa40a6caa: Loading layer [==================================================>] 2.048kB/2.048kB 622cd2c170f3: Loading layer [==================================================>] 152MB/152MB
7219a9159e4f: Loading layer [==================================================>] 223.9MB/223.9MB 633fa40a6caa: Loading layer [==================================================>] 2.048kB/2.048kB
678b55e862c7: Loading layer [==================================================>] 4.377GB/4.377GB 7219a9159e4f: Loading layer [==================================================>] 223.9MB/223.9MB
Loaded image: jupyterhub-openbis-sis-20180405:latest 678b55e862c7: Loading layer [==================================================>] 4.377GB/4.377GB
$ docker images Loaded image: jupyterhub-openbis-sis-20180405:latest
REPOSITORY TAG IMAGE ID CREATED SIZE $ docker images
jupyterhub-openbis-sis-20180405 latest 585a9adf333b 24 hours ago 4.75GB REPOSITORY TAG IMAGE ID CREATED SIZE
jupyterhub-openbis-sis-20180405 latest 585a9adf333b 24 hours ago 4.75GB
```
### Remove an image ### Remove an image
$ docker rmi jupyterhub-openbis-sis-juanextensions-recipe-20180406 ```bash
$ docker rmi jupyterhub-openbis-sis-juanextensions-recipe-20180406
```
### Remove all stopped containers ### Remove all stopped containers
$ docker rm $(docker ps -aq) ```bash
$ docker rm $(docker ps -aq)
```
openBIS ELN Integration Configuration openBIS ELN Integration Configuration
------------------------------------- -------------------------------------
...@@ -342,32 +358,32 @@ On the openBIS end, what needs to be done is to append the following ...@@ -342,32 +358,32 @@ On the openBIS end, what needs to be done is to append the following
lines into your ELN instance profile: lines into your ELN instance profile:
servers/core-plugins/eln-lims/1/as/webapps/eln-lims/html/etc/InstanceProfile.js servers/core-plugins/eln-lims/1/as/webapps/eln-lims/html/etc/InstanceProfile.js
# Ansible yml syntax, replace the variables in the double curly braces by the appropriate values: ```js
this.jupyterIntegrationServerEndpoint = "https://{{ openbis_jupyterhub_hostname }}:{{ openbis_jupyterhub_communication_port }}"; # Ansible yml syntax, replace the variables in the double curly braces by the appropriate values:
this.jupyterEndpoint = "https://{{ openbis_jupyterhub_hostname }}/"; this.jupyterIntegrationServerEndpoint = "https://{{ openbis_jupyterhub_hostname }}:{{ openbis_jupyterhub_communication_port }}";
this.jupyterEndpoint = "https://{{ openbis_jupyterhub_hostname }}/";
# Example: # Example:
this.jupyterIntegrationServerEndpoint = "https://jupyterhub-demo.labnotebook.ch:80"; this.jupyterIntegrationServerEndpoint = "https://jupyterhub-demo.labnotebook.ch:80";
this.jupyterEndpoint = "https://jupyterhub-demo.labnotebook.ch/"; this.jupyterEndpoint = "https://jupyterhub-demo.labnotebook.ch/";
On the jupyterhub end, the docker command would then look as follows: On the jupyterhub end, the docker command would then look as follows:
docker run -e OPENBIS_URL=https://{{ openbis_public_hostname }} -e JUPYTERHUB_INTEGRATION_SERVICE_PORT=8002 -e JUPYTERHUB_PORT=8000 -e CERTIFICATE_KEY=/vagrant/config/certificates/default.key -e CERTIFICATE_CRT=/vagrant/config/certificates/default.crt -p 8000:8000 -p 8081:8081 -p 8001:8001 -p {{ openbis_jupyterhub_communication_port }}:8002 585a9adf333b ./vagrant/initialize/start_jupyterhub.sh docker run -e OPENBIS_URL=https://{{ openbis_public_hostname }} -e JUPYTERHUB_INTEGRATION_SERVICE_PORT=8002 -e JUPYTERHUB_PORT=8000 -e CERTIFICATE_KEY=/vagrant/config/certificates/default.key -e CERTIFICATE_CRT=/vagrant/config/certificates/default.crt -p 8000:8000 -p 8081:8081 -p 8001:8001 -p {{ openbis_jupyterhub_communication_port }}:8002 585a9adf333b ./vagrant/initialize/start_jupyterhub.sh
# Example: # Example:
openbis_public_hostname: openbis-test.ethz.ch openbis_public_hostname: openbis-test.ethz.ch
openbis_jupyterhub_hostname: jupyterhub-test.ethz.ch openbis_jupyterhub_hostname: jupyterhub-test.ethz.ch
openbis_jupyterhub_communication_port: 80 openbis_jupyterhub_communication_port: 80
The only port you need to open on your jupyterhub instance is the one The only port you need to open on your jupyterhub instance is the one
matching {{ openbis\_jupyterhub\_communication\_port }}. Using matching {{ openbis\_jupyterhub\_communication\_port }}. Using
firewall-cmd this would look as follows: firewall-cmd this would look as follows:
firewall-cmd --permanent --zone=public --add-rich-rule='rule family="ipv4" source address="{{ openbis_jupyterhub_openbis_hostname }}" port protocol="tcp" port="{{ openbis_jupyterhub_communication_port }}" accept' firewall-cmd --permanent --zone=public --add-rich-rule='rule family="ipv4" source address="{{ openbis_jupyterhub_openbis_hostname }}" port protocol="tcp" port="{{ openbis_jupyterhub_communication_port }}" accept'
```
Troubleshooting Connectivity to openBIS Troubleshooting Connectivity to openBIS
--------------------------------------- ---------------------------------------
...@@ -401,7 +417,6 @@ just log in to JupyterHub there is a new session available that needs to ...@@ -401,7 +417,6 @@ just log in to JupyterHub there is a new session available that needs to
be handed over to the Jupyter server. For that just stop and start it be handed over to the Jupyter server. For that just stop and start it
again. again.
Step 1 : Go to your control panel clicking on the button of the top Step 1 : Go to your control panel clicking on the button of the top
right corner. right corner.
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment