Serge's Services: Difference between revisions

From DISI
Jump to navigation Jump to search
(adding some guidelines)
(jupyterhub instructions)
Line 8: Line 8:


== How to start a service manually ==
== How to start a service manually ==
Do this if you can't perform it through gitlab automation tools.
Do this if you can't perform it through gitlab automation tools or if the tools don't exist yet.


=== Jupyter-Hub ===
=== Jupyter-Hub ===
1. Log into cluster 7 (login01) and SSH into a cpu node:
<code>
ssh <username>@169.230.26.173
(enter your password)
ssh cpu02 (can be a different cpu node, check nodes with sinfo.)
</code>
2. Navigate to the following folder:
<code>
/nfs/home/sstrizhov/jupyter-hub
</code>
3. Run the following script:
<code>
./startup.sh
</code>
This should automatically build and get the docker container running for you at "https://cpu02:8888" unless 8888 as a socket is already in use.


=== cdk/depict ===
=== cdk/depict ===

Revision as of 17:45, 2 September 2026

These are the services that I'm running as of September 2nd, 2026.

  • qsar - cluster2(epyc:4545)
  • datagrok - cluster2(epyc:8080)

How to start a service manually

Do this if you can't perform it through gitlab automation tools or if the tools don't exist yet.

Jupyter-Hub

1. Log into cluster 7 (login01) and SSH into a cpu node:

ssh <username>@169.230.26.173 (enter your password) ssh cpu02 (can be a different cpu node, check nodes with sinfo.)

2. Navigate to the following folder:

/nfs/home/sstrizhov/jupyter-hub

3. Run the following script:

./startup.sh

This should automatically build and get the docker container running for you at "https://cpu02:8888" unless 8888 as a socket is already in use.


cdk/depict