A working slurm-web v2.4.0 on Ubuntu 20.04 announcement #222

daverona · 2022-03-28T06:39:27Z

This is not an issue but an announcement for working slurm-web v2.4.0 on Ubuntu 20.04
If this post causes any problem, I will gladly delete it.
But I thought I might share what I experienced.

The Docker image can be pulled:

docker login registry.gitlab.com --username <your-gitlab-account-name>
docker image pull registry.gitlab.com/daverona/docker/slurm-web:v2.4.0-p3
docker logout

The package versions used in the image:

pyslurm: 19-05-0 (https://github.com/pyslurm/pyslurm/tree/19-05-0)
opentypejs: 0.4.3-2 (https://github.com/edf-hpc/opentypejs/tree/debian/0.4.3-2)
libjs-bootstrap-typeahead: 0.11.1-1 (https://github.com/edf-hpc/libjs-bootstrap-typeahead/tree/debian/0.11.1-1)
libjs-bootstrap-tagsinput: 0.8.0-1 (https://github.com/edf-hpc/libjs-bootstrap-tagsinput/tree/debian/0.8.0-1)
slurm-web: v2.4.0 (https://github.com/edf-hpc/slurm-web/tree/v2.4.0)

Note that these packages are available as .deb files under /tmp directory in the image if you like to have them.

Then you need a configuration directory first from https://github.com/edf-hpc/slurm-web/tree/v2.4.0/conf
And please edit the files in the directory especially:

./racks.xml
./restapi.conf

Note. If you don't do this, you will get an empty page.

Assuming that

Your slurmctld is 19.05.05 (default, off-the-shelf package) on Ubuntu 20.04,
slurmctld is running on the host on which you are about to run a container, and
The configuration directory conf is under the current directory,

type the following to run a container:

docker container run \
  -d \
  -v /etc/passwd:/etc/passwd:ro \
  -v /etc/group:/etc/group:ro \
  -v /etc/munge:/etc/munge \
  -v /etc/slurm-llnl:/etc/slurm-llnl:ro \
  -v $(pwd)/conf:/etc/slurm-web:ro \
  -p 8080:80 \
  registry.gitlab.com/daverona/docker/slurm-web:v2.4.0-p3

Note that since slurm-web runs in Docker container, your slurm.conf should not use host address like localhost or loopback addresses.

Then visit http://localhost:8080

Note. If you plan to run the container on a different machine from the one running slurmctld, copy four files:

/etc/passwd
/etc/group
/etc/munge/munge.key
/etc/slurm-llnl/slurm.conf

to the machine you will run the container and mount them. It will work. (It's been tested.)

By editing ./dashboard/clusters.config.json and ./restapi.conf properly, you can observe multiple clusters on a single website. (It's been tested.)

The Dockerfile source is here: https://gitlab.com/daverona/docker/slurm-web/-/blob/v2.4.0-p3/Dockerfile

Note that pyslurm and slurm-web have patches in Dockerfile.

pyslurm: https://gitlab.com/daverona/docker/slurm-web/-/blob/v2.4.0-p3/Dockerfile#L55

slurm-web: https://gitlab.com/daverona/docker/slurm-web/-/blob/v2.4.0-p3/Dockerfile#L120

I hope this post will help someone who wishes to run slurm-web on Ubuntu 20.04.
And want to say thank you so much for this fabulous work!!

The text was updated successfully, but these errors were encountered:

Zorlin · 2022-03-29T21:30:44Z

Fantastic work! I might try and get this working on Slurm 21.08 if I can manage it.

rezib · 2022-03-31T06:34:30Z

Thank you very much for this sharing and the positive feedback! :)

daverona · 2022-04-02T08:16:51Z

Thank you very much for this sharing and the positive feedback! :)

No. Thank YOU! 😃

liu-shaobo · 2022-05-25T14:45:41Z

hi
Can I see your ./dashboard/clusters.config.json and ./restapi.con files

daverona · 2022-05-30T22:29:55Z

hi Can I see your ./dashboard/clusters.config.json and ./restapi.con files

I have three clusters and following is clusters.config.json of slurm.watch.example.com, where I can observe all three of them:

[
  {
    "name": "Cluster A (XXX internet data center)",
    "api": {
      "url": "http://slurm.space1.example.com:8080",
      "path": "/slurm-restapi"
    }
  },
  {
    "name": "Cluster B (Headquarter server room)",
    "api": {
      "url": "http://slurm.watch.example.com",
      "path": "/slurm-restapi"
    }
  },
  {
    "name": "Cluster C (XXX internet data center)",
    "api": {
      "url": "https://slurm.example.com",
      "path": "/slurm-restapi"
    }
  }
]

And the corresponding restapi.conf:

# configure here all parameters for the Slurm-web REST API

[cors]
# give here the list of the domains from where the origin is authorized,
# separated by commas
#
# example : authorized_origins = http://example1.com,http://example2.com
#authorized_origins = http://localhost,http://server.local:8000,http://192.168.90.121:8000
authorized_origins = http://localhost,http://slurm.watch.example.com

[config]
# Set to 'enable' to activate authentication.
# Authentication is based on LDAP, so an LDAP server and the good configuration
# for it, below in this file, are required.
#authentication = enable
authentication = disable
# Absolute path to the secret key file. This key is used to sign tokens
# on server-side and make sure they are not modified during network
# communications. The secret is required only if authentication is enabled.
# Make sure this file is readable by root and WCGI user only, and not
# world-readable.
#secret_key = /etc/slurm-web/secret.key
# Set to 'enable' to activate cache.
cache = enable
# Path for racks description (default to /etc/slurm-web/racks.xml).
racksxml = /etc/slurm-web/racks.xml

[roles]
# Allow guests users or not. Guests users have the 'all' role. Disabled by
# default.
# guests = disabled

# Trusted sources can be enabled to allow specific hosts to access the API and
# bypass the authentication. If enabled, the hosts must be declared in the
# roles members using the % prefix followed by the IP address or the hostname.
# This feature is disabled by default.
# trusted_sources = disabled

# The `all` role if for all users that do not either have the user or admin
# role, including guests. This role can be:
#
# - disabled: users with the all role cannot access the REST API
# - enabled: users with the all role can access the REST API
#
# Enabled by default.
#all = enabled

# The roles members can be defined with a list of groups (whose names
# are prefixed by @) and logins.
user = @chimistes
admin = @admin,pierre

# Give here restricted fields about jobs for each role, separated by commas
restricted_fields_for_all = command
restricted_fields_for_user = command
restricted_fields_for_admin =

[acl]
# You can set here an access control list for each view of the dashboard for
# this cluster.
# This feature requires authentication to be enabled.
# For each view, you can give a list of roles to define who can access to this
# view.
# If no ACL is provided for a view, every authenticated user can access to
# this view.
# i.e. ``jobs = admin`` implies that the jobs view will be available only for
# every user which has role of 'admin'.
# If you give an empty value for an entry (i.e. ``jobs =``), the corresponding
# view will not be accessible for anybody.
#
# Available views are : [
#   'jobs', 'jobsmap', 'partitions', 'reservations', 'qos', 'racks', '3dview',
#   'gantt', 'topology'
# ]

[ldap]
# Configure here settings to connect to your LDAP server.
uri = ldap://admin:389
base_people = ou=people,dc=cluster,dc=local
base_group = ou=group,dc=cluster,dc=local
# Optional path to CA certificate. Required only if ldaps protocol is used and
# CA certification not available in system certificates chain.
# cacert = /etc/ssl/certs/cacert.pem
expiration = 1296000

[cache]
# address for Redis server (default to host=localhost, port=6379)
redis_host = redis
redis_port = 6379
# TTL for jobs (default to 10 seconds)
jobs_expiration = 10
# TTL for other informations (default to 60 seconds)
global_expiration = 60

I don't use roles and ldap sections.

marks221b · 2022-06-09T02:24:15Z

hi so have anyway run slurm-web on centos 7.7 with docker? when i build over it seem like only white page

daverona · 2022-06-13T09:36:02Z

hi so have anyway run slurm-web on centos 7.7 with docker? when i build over it seem like only white page

I don't use CentOS. So I cannot answer to your question.

But the important part is to build Docker image with pyslurm working with Slurm installed on your CentOS.
pyslurm is picky about Slurm version and you may want to investigate which pyslurm would work with your Slurm first.

andrewssobral · 2022-08-19T22:39:20Z

Hello @daverona ,
Thank you for your excellent work.
I tried to follow your steps, but I am facing the following issue:

Do you know what is it?

For info my Slurm version is 19.05.5 and I'm running the container on the slurm controller (headnode).
Thanks in advance,
Andrews

andrewssobral · 2022-08-19T22:41:36Z

Related issue #183

daverona · 2022-08-20T01:30:38Z

Hi @andrewssobral,

Thanks for your kind words.

To answer your question, let me ask you a question:
Is your slurm-web (web part) trying to connect to another remote slurm-web (REST part) or just the same local slurm-web (REST part)?

If it is local, I suggest to check your local slurm-web's restapi.conf and make sure that authorized_origins includes non-localhost address. For instance, mine is: http://localhost,http://slurm.watch.example.com.

If it is remote (in this scenarios, you use your local slurm-web container (web part) for the remote slurm-web container (REST part)), check your remote slurm-web's restapi.conf and make sure that authorized_origins includes your local container's reachable server URL, i.e. http://slurm.watch.example.com in the above example. Best way to test this is to ping from remote container to your local container for reachability.

If everything is good, the second question to ask is:
Did you register all slurm-web containers (including your local one) in cluster.config.json?
For example, here's mine:

[
  {
    "name": "Brain (Hostway internet data center)",
    "api": {
      "url": "http://slurm.space1.example.com:8080",
      "path": "/slurm-restapi"
    }   
  },  
  {
    "name": "Dev (Headquarter server room)",
    "api": {
      "url": "http://slurm.watch.example.com",
      "path": "/slurm-restapi"
    }   
  },  
  {
    "name": "Seer (Hostway internet data center)",
    "api": {
      "url": "https://slurm.example.com",
      "path": "/slurm-restapi"
    }   
  }
]

Note that even thou the second one (Dev) is local to me, I didn't use http://localhost for the service URL.

Hope this helps. Good luck.

hellozzcy · 2023-05-12T01:50:29Z

I want to know where the URL and path in cluster.config.json are obtained from. I have deployed a local Slurm cluster, but I don't know what to fill in the address in cluster.config.json. Are there any default listening addresses? Please help answer this question. Thank you.

hellozzcy · 2023-05-12T06:34:36Z

Related issue #183

Have you solved this problem? I encountered the same issue where I'm not sure how to fill in the url and path in the cluster.config.json file. I couldn't find any related configuration in my Slurm cluster. Do you have any idea? Thank you.

BigDataHealthcare · 2024-01-17T19:17:20Z

Hi,

Where do i need to copy below configuration from the repository

./racks.xml
./restapi.conf

daverona · 2024-01-19T01:31:05Z

Hi,

Where do i need to copy below configuration from the repository

./racks.xml ./restapi.conf

The answer is $(pwd)/conf (i.e. conf directory under the current directory).
In my original post, there's a line: -v $(pwd)/conf:/etc/slurm-web:ro \

$(pwd)/conf directory structure is here: https://github.com/rackslab/slurm-web/tree/v2.4.0/conf
You can find where racks.xml and restapi.conf are placed.

Then$(pwd)/conf is bind-mounted to /etc/slurm-web in the container.

Hope this answers to your question.

daverona · 2024-01-19T01:58:36Z

I want to know where the URL and path in cluster.config.json are obtained from. I have deployed a local Slurm cluster, but I don't know what to fill in the address in cluster.config.json. Are there any default listening addresses? Please help answer this question. Thank you.

Maybe it wasn't clear in my original post. If slurmctld and the container run on the same host, you don't have a cluster. So the following cluster.config.json would be suffice:

[]

If your container is running on a host which is not running slurmctld, then you need to configure cluster.config.json.
To simplify explanation, assume we have following clusters:

cluster-1.example.com
  - slurmctld running
  - slurm-web container running (*)
cluster-2.example.com
  - slurmctld running
  - slurm-web container running (*)
...
observer.example.com
  - may or may not run slurmctld  
  - slurm-web container running (**)

Each server marked with (*) is not (obviously) a cluster itself. So empty array is enough for cluster.config.json. They are however need to run slurm-web container for a cluster observer (marked with (**)). cluster.config.json file in the original post is for this observer (observer.example.com in our assumption).

Now to answer to your question,

path in the file is always "/slurm-restapi"
name is not displayed so it does not matter (I use it as a comment).
url is for slurm-web container on each host (cluster-1.example.com, cluster-2.example.com, etc) reachable from observer (observer.example.com).

Here is an example. If you use https://slurm.cluster-1.example.com for cluster-1.example.com and http://slurm.cluster-2.example.com:8080 for cluster-2.example.com, cluster.config.json would be like this:

[
  {
    "name": "Cluster 1 (XXX internet data center)",
    "api": {
      "url": "https://slurm.cluster-1.example.com",
      "path": "/slurm-restapi"
    }
  },
  {
    "name": "Cluster 2 (YYY internet data center)",
    "api": {
      "url": "http://slurm.cluster-2.example.com:8080",
      "path": "/slurm-restapi"
    }
  }
]

If observer.example.com is not running slurmctld, you should omit the following lines in the original post:

  -v /etc/passwd:/etc/passwd:ro \
  -v /etc/group:/etc/group:ro \
  -v /etc/munge:/etc/munge \
  -v /etc/slurm-llnl:/etc/slurm-llnl:ro \

BigDataHealthcare · 2024-01-20T15:32:52Z

I am running the container and slurmctld on same host. The host created on virtual machine. I have updated the clusters.config.json with value []. But i am getting following error.

I found that the http://localhost:8080/slurm-restapi throwing an"Intrernal Server Error" - status : 500. I am unable to find out the root cause of issue.
Can you please share me some information that will help me to resolve issue?

daverona · 2024-01-30T00:02:57Z

I am running the container and slurmctld on same host. The host created on virtual machine. I have updated the clusters.config.json with value []. But i am getting following error.

I found that the http://localhost:8080/slurm-restapi throwing an"Intrernal Server Error" - status : 500. I am unable to find out the root cause of issue. Can you please share me some information that will help me to resolve issue?

The error is really a warning. The real problem is, your slurm-web UI part cannot reach the slurm-web REST part.

Open restapi.conf file and make sure that authorized_origins has an entry: http://localhost:8080.

rezib · 2024-05-15T14:31:50Z

Note that this issue concerns Slurm-web v2 which is not maintained anymore. The new version v3.0.0 has been released and its is much easier to install than previous versions thanks to native system packages (RPM, deb) for most popular distributions.

The quick start guide for v3.0.0 is available online: https://docs.rackslab.io/slurm-web/install/quickstart.html

If you prefer containers over traditional system packages, it is also planned to work on this in #266.

Unless you see a good reason to keep this issue open, it will be closed in a few weeks. BTW, thank you @daverona for your invaluable work on Slurm-web v2 despite its bad shape.

rezib · 2024-06-19T09:08:02Z

For the reasons explained in the previous comment, I finally close this issue.

This was referenced Sep 28, 2022

Modal CSS not working? #227

Closed

Supported versions of Debian, Ubuntu, etc. for slurm-web 2.4.0? #229

Closed

Caian mentioned this issue Jan 11, 2023

Working container for slurm 22.5 on Ubuntu 22.04 #233

Closed

rezib added the deprecated version The issue concerns a deprecated version of the software. label May 13, 2024

rezib added the pending closure Unless justified reason is provided, it will be closed soon without solution. label May 15, 2024

rezib closed this as completed Jun 19, 2024

rezib removed the pending closure Unless justified reason is provided, it will be closed soon without solution. label Jun 19, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

A working slurm-web v2.4.0 on Ubuntu 20.04 announcement #222

A working slurm-web v2.4.0 on Ubuntu 20.04 announcement #222

daverona commented Mar 28, 2022 •

edited

Loading

Zorlin commented Mar 29, 2022

rezib commented Mar 31, 2022

daverona commented Apr 2, 2022

liu-shaobo commented May 25, 2022

daverona commented May 30, 2022 •

edited

Loading

marks221b commented Jun 9, 2022

daverona commented Jun 13, 2022

andrewssobral commented Aug 19, 2022 •

edited

Loading

andrewssobral commented Aug 19, 2022

daverona commented Aug 20, 2022 •

edited

Loading

hellozzcy commented May 12, 2023

hellozzcy commented May 12, 2023

BigDataHealthcare commented Jan 17, 2024

daverona commented Jan 19, 2024

daverona commented Jan 19, 2024

BigDataHealthcare commented Jan 20, 2024 •

edited

Loading

daverona commented Jan 30, 2024

rezib commented May 15, 2024

rezib commented Jun 19, 2024

A working slurm-web v2.4.0 on Ubuntu 20.04 announcement #222

A working slurm-web v2.4.0 on Ubuntu 20.04 announcement #222

Comments

daverona commented Mar 28, 2022 • edited Loading

Zorlin commented Mar 29, 2022

rezib commented Mar 31, 2022

daverona commented Apr 2, 2022

liu-shaobo commented May 25, 2022

daverona commented May 30, 2022 • edited Loading

marks221b commented Jun 9, 2022

daverona commented Jun 13, 2022

andrewssobral commented Aug 19, 2022 • edited Loading

andrewssobral commented Aug 19, 2022

daverona commented Aug 20, 2022 • edited Loading

hellozzcy commented May 12, 2023

hellozzcy commented May 12, 2023

BigDataHealthcare commented Jan 17, 2024

daverona commented Jan 19, 2024

daverona commented Jan 19, 2024

BigDataHealthcare commented Jan 20, 2024 • edited Loading

daverona commented Jan 30, 2024

rezib commented May 15, 2024

rezib commented Jun 19, 2024

daverona commented Mar 28, 2022 •

edited

Loading

daverona commented May 30, 2022 •

edited

Loading

andrewssobral commented Aug 19, 2022 •

edited

Loading

daverona commented Aug 20, 2022 •

edited

Loading

BigDataHealthcare commented Jan 20, 2024 •

edited

Loading