[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] routing jobs to a remote Slurm cluster



Hi Miron,

No, I will take a look.

Thanks,

Ron

==
On 5/8/24 11:06, MIRON LIVNY via HTCondor-users wrote:
Ron,

Did you consider deploying an Annex on the SLURM cluster?

This way the user only âseesâ HTCondor.

Miron


Sent from my iPhone

On May 8, 2024, at 08:33, R Tapia <rdt12@xxxxxxx> wrote:

ïHi All,

I have an HTCondor cluser, LOCAL, and a Slurm cluster, REMOTE. I also have a user with username RUSER on REMOTE and an ssh key that allows users on LOCAL to ssh from the access point (AP) for LOCAL a submit node on REMOTE as RUSER.

What I would like is for arbitrary users on LOCAL to be able to submit
jobs that get routed to Slurm jobs on REMOTE running at RUSER without having access to the key.

Any idea how I would go about setting this up?

Thanks,

Ron

--
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

--
-----BEGIN PGP SIGNED MESSAGE-----
R3V2ZiB6cmZmbnRyIHZmYSdnIGVybnl5bCBmdnRhcnEuIFYgd2hmZyBoZnIgZ3VyIGZnZXZhdApu
b2JpciAgZ2IgbmlidnEgdW5pdmF0IHl2YXhmIHl2eHI6CgogICAgICAgIHVnZ2M6Ly9qamouc2Ji
LnBiei8KCnpuYXR5cnEgb2wgQnNzdnByIDM2NS4KCg==
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
R3V2ZiB6cmZmbnRyIHZmYSdnIGVybnl5bCBmdnRhcnEuIFYgd2hmZyBoZnIgZ3VyIGZnZXZhdApu
b2JpciAgZ2IgbmlidnEgdW5pdmF0IHl2YXhmIHl2eHI6CgogICAgICAgIHVnZ2M6Ly9qamouc2Ji
LnBiei8KCnpuYXR5cnEgb2wgQnNzdnByIDM2NS4KCg==
-----END PGP SIGNATURE-----