From: "Etienne B. Roesch" <etienne.roesch@gmail.com>
To: help-guix@gnu.org
Subject: guix on nfs based systems
Date: Wed, 22 Nov 2023 17:32:07 +0000 [thread overview]
Message-ID: <CAPX-MzA5P1A8u8QbR-g-Lx4gONQ+o7mO1TZzhZ3UHh=KdUxhvw@mail.gmail.com> (raw)
Hi,
I have been successful in convincing our IT dept to provide guix as
standard on our vms and research clusters. We use this sophisticated
platform that allows users to spawn a vm at will, and also use this shared
ldap user database to allow for people to log on from computers/terminals
spread on campus. Home directories are basically pulled from the OS (mostly
ubuntu and centos) as a shared file system on the network, which then
synchronises changes live. Practically, that means a user will find its
desktop, preferences and files as they move to different computers.
Theoretically, a user can connect to several computers at the same time,
which can lead to conflict issues at times, e.g. firefox doesn't like
parallel access to its preferences. I haven't fully tested it, but we think
that a guix profile is specific to a given computer, because of the way it
links to the store, which is (currently) local to the vm, which isn't
ideal: the whole point of using vms is for users to kill them when they
don't need them.
What would be the recommended way of solving this? Has anybody had a
similar situation?
I am thinking we could either:
- leave it as is, and train users to recreate their profiles whenever they
use a new vm/computer (after all, that's what guix is for) but it could
take some time to recompile if binaries aren't available
- maybe turn /gnu/store as a shared nfs folder
Have an awesome week!
Etienne
next reply other threads:[~2023-11-22 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 17:32 Etienne B. Roesch [this message]
2023-11-23 6:32 ` guix on nfs based systems Efraim Flashner
2023-11-23 9:41 ` Etienne B. Roesch
2023-11-26 7:33 ` Efraim Flashner
2023-12-14 14:41 ` Ricardo Wurmus
2023-11-23 13:03 ` Felix Lechner via
2023-11-23 13:03 ` Felix Lechner via Guix-Science
2023-11-24 18:08 ` Etienne B. Roesch
2023-11-26 7:36 ` Efraim Flashner
2023-12-13 10:17 ` Etienne B. Roesch
2023-12-14 14:46 ` Ricardo Wurmus
2023-12-14 15:28 ` Etienne B. Roesch
2023-12-14 15:33 ` Pierre-Antoine Bouttier
2023-12-14 15:33 ` Pierre-Antoine Bouttier
2023-12-14 15:57 ` Etienne B. Roesch
2023-12-14 19:35 ` [ext] " Ricardo Wurmus
2024-02-15 16:14 ` Simon Tournier
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='CAPX-MzA5P1A8u8QbR-g-Lx4gONQ+o7mO1TZzhZ3UHh=KdUxhvw@mail.gmail.com' \
--to=etienne.roesch@gmail.com \
--cc=help-guix@gnu.org \
/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).