Hi all,

I realize this is missing some context.

There already exists a solution here https://docs.galaxyproject.org/en/master/admin/cluster.html#submitting-jobs-as-the-real-user
But, to my understanding, it assumes:
- galaxy running on head node
- "galaxy" user exists on head node
- "galaxy" user is a sudoer
For our install, none of these hypotheses are valid, hence adding real-user capability to the ssh Slurm runner.

Regards,

Vlad

De: "VLAD VISAN" <vlad.visan@univ-grenoble-alpes.fr>
À: "small-scale-admins" <small-scale-admins@lists.galaxyproject.org>
Envoyé: Jeudi 23 Janvier 2025 16:25:26
Objet: Dynamic user ssh job submission

Hi all,

Giuseppe, Lucille & Matthias were talking about submitting jobs to a cluster as the user launching the workflow, over ssh.

Here is the summary of how we did it, by adding a "dynamic user" option to the existing cli.py runner (that can work over ssh)

Code modification: https://github.com/vladvisan/galaxy/commit/6276fd58d27d5b02035be0e16ae8641de880a9a1
- If you have any comments, I'm thinking of improving it and then submitting a PR ?
Our related related config:
- use TPV
- in tpv_rules_local.yml:
  - destinations:
    ssh_ord_mini:
    runner: cli
    params:
    shell_plugin: SecureShell
    shell_username: user-a#arbitrary, not actually used in dynamic mode
    job_partition: main
  - (comment which has no impact on the dynamic user aspect: we have no job_plugin k/v in "destinations" because we get let the user choose it step by step, using TPV)

Hope it helps & appreciate any feedback as well,

Regards,

Vlad