From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 72766@debbugs.gnu.org
Subject: [bug#72766] [PATCH v2 2/2] gnu: slurm: Enable REST API.
Date: Thu, 12 Sep 2024 17:31:50 +0200 [thread overview]
Message-ID: <87bk0skhw9.fsf@inria.fr> (raw)
In-Reply-To: <87ttelnl8w.fsf@systemreboot.net> (Arun Isaac's message of "Thu, 12 Sep 2024 12:51:11 +0100")
Hi,
Arun Isaac <arunisaac@systemreboot.net> skribis:
>> Another possibility would be to do the opposite: keep ‘slurm’ without
>> MariaDB & co., and have a ‘slurm-rest’ (?) variant with all the bells
>> and whistles?
>
> The problem with that approach is that I'm sure there will be more
> optional features to add to slurm. Then, we would have a combinatorial
> explosion of packages---slurm-rest, slurm-rest+feature1,
> slurm-rest+feature2, slurm-feature1+feature2, etc.
Not necessarily: that second variant could be maximal, where additional
features would be added.
> I am ok with having a slurm-minimal for all versions. That's the
> lesser evil.
OK.
There might be a third option: moving server-side code to a separate
output. That way, perhaps client-side code (things like ‘openmpi’)
would not have MariaDB & co. in their closure?
Ludo’.
next prev parent reply other threads:[~2024-09-12 15:33 UTC|newest]
Thread overview: 27+ 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 [this message]
2024-09-16 21:55 ` Arun Isaac
2024-09-17 6:37 ` Ludovic Courtès
2024-09-17 14:54 ` Arun Isaac
2024-10-18 14:58 ` [bug#72766] [PATCH v3 0/2] " Arun Isaac
2024-10-18 14:58 ` [bug#72766] [PATCH v3 1/2] gnu: " Arun Isaac
2024-10-18 14:58 ` [bug#72766] [PATCH v3 2/2] gnu: slurm: Move client executables into separate output Arun Isaac
2024-10-24 10:01 ` Ludovic Courtès
2024-10-24 14:50 ` Arun Isaac
2024-10-25 9:32 ` Ludovic Courtès
2024-10-25 15:23 ` Arun Isaac
2024-10-25 15:24 ` [bug#72766] [PATCH v4] gnu: slurm: Enable REST API Arun Isaac
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=87bk0skhw9.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=72766@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/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).