install wip3 on RL9

[wixaw]

Hello,
I want try slurm-web on RockyLinux 9 but i have this error

13:18:50 root@xxx:compose# dnf install openldap-devel libgsasl-devel
13:09:21 root@xxx:slurm-web# git clone -b wip3 https://github.com/rackslab/slurm-web.git compose
13:09:39 root@xxx:compose# pip install -e .
ERROR: File "setup.py" or "setup.cfg" not found. Directory cannot be installed in editable mode: /local/slurm-web/compose
(A "pyproject.toml" file was found, but editable mode currently requires a setuptools-based build.)
13:10:23 root@xxxx:compose# python3 -m pip install --upgrade pip
Requirement already satisfied: pip in /usr/lib/python3.9/site-packages (21.2.3)
Collecting pip
  Downloading pip-23.3.2-py3-none-any.whl (2.1 MB)
     |████████████████████████████████| 2.1 MB 2.4 MB/s
Installing collected packages: pip
Successfully installed pip-23.3.2
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

13:10:28 root@xxx:compose# pip install -e .
Obtaining file:///local/slurm-web/compose
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build editable ... done
  Installing backend dependencies ... done
  Preparing editable metadata (pyproject.toml) ... done
Collecting Flask (from Slurm-web==3.0.0a1)
  Downloading flask-3.0.1-py3-none-any.whl.metadata (3.6 kB)
Collecting Flask-Cors (from Slurm-web==3.0.0a1)
  Downloading Flask_Cors-4.0.0-py2.py3-none-any.whl.metadata (5.4 kB)
Collecting RacksDB (from Slurm-web==3.0.0a1)
  Downloading RacksDB-0.3.0-py3-none-any.whl.metadata (5.4 kB)
Collecting redis (from Slurm-web==3.0.0a1)
  Downloading redis-5.0.1-py3-none-any.whl.metadata (8.9 kB)
Collecting requests (from Slurm-web==3.0.0a1)
  Downloading requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)
INFO: pip is looking at multiple versions of slurm-web to determine which version is compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement RFL.authentication (from slurm-web) (from versions: none)
ERROR: No matching distribution found for RFL.authentication



python -V
Python 3.9.18

Thanks

[rezib]

Hello @wixaw,

RFL is a library developed by Rackslab, it is available in this repository. We haven't released any version of this library yet, so it is not yet published on PyPI. You can install it by cloning the Git repository and run ./install.sh to install all its packages.

[wixaw]

Thanks you so much !

[wixaw]

I successfully installed RFL, but I also needed to run 'dnf install cairo cairo-devel' before executing 'pip install -e .' to avoid dependency errors. However, I'm now having trouble understanding how to start the slurm-web service/server. Do I need an Apache proxypass with a specific Python module?

[rezib]

Hello @wixaw,

Yes, cairo-devel is a build dependency of RacksDB, one of Slurm-web external dependency. We provide prebuilt RPM and deb packages for RacksDB but not yet for Slurm-web unfortunately.

There are 2 backend services to launch in Slurm-web:

• An agent which connects to Slurm slurmrestd daemon,
• The gateway which performs authentication and route requests to the agents.

To launch an agent from a source installation, you can run the following command:

$ slurm-web-agent --conf-defs conf/vendor/agent.yml --conf your/agent.ini

To launch a gateway, launch this command:

$ slurm-web-gateway --conf-defs conf/vendor/gateway.yml --conf your/gateway.ini

You can look at files in dev/conf/ folder as a source of inspiration for your INI files.

To launch the frontend component, run this command:

$ cd frontend && npm run dev

Unfortunately, we don't provide WSGI scripts to launch the backend components with other « production-ready » HTTP servers yet. It is planned for the following months with release 3.0.0.

[rezib]

There are now RPM packages to install latest v3.0.0 release: https://docs.rackslab.io/slurm-web/install/install/distribs/rhel.html

Please tell me if they work for you!

[wixaw]

Thanks for fixes,
I have slurm 22.05.9 on RockyLinux9

I try tro use token jwt with that : curl -k -vvv -H X-SLURM-USER-TOKEN:xxxxxxxxxxxxx--unix-socket /run/slurmrestd/slurmrestd.socket 'http://localhost/slurm/v0.0.39/ping' but i obtain "Authentication failure"

here are some logs journalctl slurmrestd.service logs

May 14 08:33:13 r9dev slurmrestd[1606612]: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] accepted user >
May 14 08:33:13 r9dev slurmrestd[1606612]: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:33:13 r9dev slurmrestd[1606612]: slurmrestd: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] ac>
May 14 08:33:13 r9dev slurmrestd[1606612]: slurmrestd: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:33:02 r9dev slurmrestd[1606612]: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] accepted user >
May 14 08:33:02 r9dev slurmrestd[1606612]: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:32:51 r9dev slurmrestd[1606612]: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] accepted user >
May 14 08:32:51 r9dev slurmrestd[1606612]: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:32:51 r9dev slurmrestd[1606612]: slurmrestd: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] ac>
May 14 08:32:51 r9dev slurmrestd[1606612]: slurmrestd: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:32:40 r9dev slurmrestd[1606612]: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] accepted user >
May 14 08:32:40 r9dev slurmrestd[1606612]: slurmrestd: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] ac>
May 14 08:32:40 r9dev slurmrestd[1606612]: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:32:40 r9dev slurmrestd[1606612]: slurmrestd: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:32:29 r9dev slurmrestd[1606612]: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] accepted user >
May 14 08:32:29 r9dev slurmrestd[1606612]: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:32:18 r9dev slurmrestd[1606612]: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] accepted user >
May 14 08:32:18 r9dev slurmrestd[1606612]: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:32:18 r9dev slurmrestd[1606612]: slurmrestd: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] ac>
May 14 08:32:18 r9dev slurmrestd[1606612]: slurmrestd: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:32:07 r9dev slurmrestd[1606612]: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] accepted user >
May 14 08:32:07 r9dev slurmrestd[1606612]: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:32:07 r9dev slurmrestd[1606612]: slurmrestd: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] ac>
May 14 08:32:07 r9dev slurmrestd[1606612]: slurmrestd: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:31:56 r9dev slurmrestd[1606612]: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] accepted user >
May 14 08:31:56 r9dev slurmrestd[1606612]: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs
May 14 08:31:56 r9dev slurmrestd[1606612]: slurmrestd: rest_auth/local: _auth_socket: _auth_socket: [/run/slurmrestd/slurmrestd.socket->fd:8] ac>
May 14 08:31:56 r9dev slurmrestd[1606612]: slurmrestd: operations_router: [/run/slurmrestd/slurmrestd.socket->fd:8] GET ///slurm/v0.0.39/jobs

[rezib]

Ah unfortunately Slurm-web v3.0.0 requires Slurm >= 23.02. REST API v0.0.39 is not available in Slurm 22.05. More details are available in documentation: https://docs.rackslab.io/slurm-web/overview/architecture.html#slurm-versions

BTW, Slurm-web does not support slurmrest with JWT authentication, it only works with Munge authentication at this point.

[wixaw]

ahh ok ! sorry i dont read this requirement :/
and I'm dependent on the slurm version distributed by RHEL, our policy being not to install .rpm packages and to have security updates automatically
Unlucky

[rezib]

I guess you are talking about Slurm packages in EPEL9 as Slurm is not packaged nor distributed in RHEL/RockyLinux by itself. This is just a friendly advice but regarding security concerns, I don't recommend using these packages as they are community maintained with quite some lag. For example, they don't include fixes for high severity security holes CVE-2023-49933, CVE-2023-49936, CVE-2023-49937, CVE-2023-49938 and CVE-2023-41914. Did you check this?

[wixaw]

Thank you very much for bringing this to my attention. Indeed, I had not noticed the previous CVEs. I have asked the maintainer to update the repository...