Skip to content

[CLUST-361] configure slurmrestd so the backend can reach the Slurm REST API - #188

Open
joegoooo wants to merge 1 commit into
mainfrom
feat/CLUST-361-setup-ansible-slurmrestd
Open

[CLUST-361] configure slurmrestd so the backend can reach the Slurm REST API#188
joegoooo wants to merge 1 commit into
mainfrom
feat/CLUST-361-setup-ansible-slurmrestd

Conversation

@joegoooo

Copy link
Copy Markdown
Contributor

Type of changes

  • Feature

Purpose

  • Run Slurmrestd on target nodes

Additional Information

The slurm_controller role installed slurm-smd-slurmrestd but never
configured or started it, so slurmrestd was not listening on TCP and
the backend's slurm_restful_base_url had nothing to connect to.

Add a systemd drop-in that clears the packaged ExecStart and rebinds
slurmrestd to a TCP address with JWT auth, then enable and start the
service. JWT was already wired up on the cluster side: slurm.conf
carries AuthAltTypes=auth/jwt and the role generates /etc/slurm/jwt.key.

The listen host and port are exposed as role defaults
(slurmrestd_listen_host, slurmrestd_port) so they can be overridden
from the inventory.

The tasks live in their own tasks/slurmrestd.yaml, imported from
main.yaml, so they can be exercised in isolation via tasks_from.

Claude-Session: https://claude.ai/code/session_01AToP9zWdizh6dQZ9Q6H85n
@joegoooo joegoooo self-assigned this Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant