From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 72766@debbugs.gnu.org
Subject: [bug#72766] [PATCH v2 2/2] gnu: slurm: Enable REST API.
Date: Tue, 17 Sep 2024 15:54:41 +0100 [thread overview]
Message-ID: <87y13ql49a.fsf@systemreboot.net> (raw)
In-Reply-To: <87tteeair5.fsf@inria.fr>
>> I presume you might need to carry both the server-side and the
>> client-side code in a guix pack. So, how would this option help?
>
> No, to run code on a supercomputer, you only need MPI and things like
> ‘salloc’, ‘sbatch’, etc. There’s definitely no need for ‘slurmd’ or
> anything like that in that case because it’s already running on the
> machine.
Ah, ok, the server-side is maintained by a different admin team. I was
thinking you were maintaining the server-side as well. That makes sense,
thank you!
In that case, I'll split slurm into two outputs---a server and a
client-side. I'll send a patch in the coming days.
prev parent reply other threads:[~2024-09-17 14:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 23:30 [bug#72766] [PATCH 0/2] slurm: Enable REST API Arun Isaac
2024-08-22 23:36 ` [bug#72766] [PATCH 1/2] gnu: Add libjwt Arun Isaac
2024-08-22 23:36 ` [bug#72766] [PATCH 2/2] gnu: slurm: Enable REST API Arun Isaac
2024-09-02 7:43 ` Ludovic Courtès
2024-09-06 16:03 ` Arun Isaac
2024-09-06 16:06 ` Arun Isaac
2024-09-09 7:13 ` Ludovic Courtès
2024-09-09 14:59 ` Arun Isaac
2024-09-10 8:32 ` Ludovic Courtès
2024-09-09 15:24 ` [bug#72766] [PATCH v2 1/2] gnu: Add libjwt Arun Isaac
2024-09-09 15:24 ` [bug#72766] [PATCH v2 2/2] gnu: slurm: Enable REST API Arun Isaac
2024-09-10 6:50 ` Ludovic Courtès
2024-09-10 15:02 ` Arun Isaac
2024-09-12 8:24 ` Ludovic Courtès
2024-09-12 11:51 ` Arun Isaac
2024-09-12 15:31 ` Ludovic Courtès
2024-09-16 21:55 ` Arun Isaac
2024-09-17 6:37 ` Ludovic Courtès
2024-09-17 14:54 ` Arun Isaac [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y13ql49a.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=72766@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).