From: "Sébastien Lerique" <sl@eauchat.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-science@gnu.org
Subject: Re: Introducing Guix to HPC at my institution
Date: Tue, 16 Mar 2021 10:54:35 +0900 [thread overview]
Message-ID: <87zgz3c17o.fsf@eauchat.org> (raw)
In-Reply-To: <CAJ3okZ3DLHMr4h8Ug73oS_dS452AAu6UaBwkJaAnCJPzf0-+cg@mail.gmail.com>
Hi Simon,
Thanks for your answer!
On 15 Mar 2021 at 22:47, zimoun <zimon.toutoune@gmail.com> wrote:
> Well, if you are French speaker, a two mornings* workshop is in
> the
> pipe. The announce should come really soon. The idea is
> sharing
> feedback with other users from sysadmin to researcher.
>
> *morning in metropolitan France meaning. :-)
I am French, I'll be very happy to attend if I can! I live in
Japan now though, so I guess I'll miss parts. Are you planning to
record the workshop?
Another thought: given Ludo's position, I am imagining that Inria
Bordeaux runs Guix on some of their infrastructure, is that the
case? If so, can you share any details about how that came to
happen?
>> As a first step I would like to discuss with the sysadmins if
>> they
>> would consider activating user namespaces so users can play
>> around. Aside from [1] and [2], are there any updated
>> discussions
>> about this topic, e.g. why to do it or why not?
>
> You mean to run "bundles" on computers that do not have Guix
> installed, right?
> Well, the answer "qui peut le plus peut le moins" is maybe not
> satisfactoring... if you have the choice to do it, you should.
> Even,
> if you have the choice to install Guix (the package manager),
> you also
> should.
Yes I meant that. They run CentOS 8, so convincing them to run a
build daemon will not be as simple as `apt install guix`, but
we'll see how the conversation goes :)
I'll write back here in a few days once I've thought about how to
present things to the sysadmins. In the meantime, any feedback on
past experience is very welcome!
Sébastien
next prev parent reply other threads:[~2021-03-16 1:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 3:12 Introducing Guix to HPC at my institution Sébastien Lerique
2021-03-15 13:47 ` zimoun
2021-03-16 1:54 ` Sébastien Lerique [this message]
2021-03-16 8:06 ` zimoun
2021-03-16 9:05 ` Ludovic Courtès
2021-03-18 2:26 ` Sébastien Lerique
2021-03-26 8:22 ` Sébastien Lerique
2021-03-29 12:03 ` Ludovic Courtès
2021-03-30 1:54 ` Sébastien Lerique
2021-03-30 7:21 ` Ludovic Courtès
2021-03-31 5:23 ` Sébastien Lerique
2021-04-01 8:35 ` Ludovic Courtès
2021-04-01 14:34 ` Sébastien Lerique
2021-04-10 20:43 ` Ludovic Courtès
2021-04-12 1:21 ` Sébastien Lerique
2021-04-12 12:43 ` Ludovic Courtès
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=87zgz3c17o.fsf@eauchat.org \
--to=sl@eauchat.org \
--cc=guix-science@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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.
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).