From: "Cook, Malcolm" <MEC@stowers.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Ricardo Wurmus" <ricardo.wurmus@mdc-berlin.de>
Cc: Guix-devel <guix-devel@gnu.org>,
'Pjotr Prins' <pjotr.public66@thebird.nl>,
"'bio-packaging@mailman.open-bio.org'"
<bio-packaging@mailman.open-bio.org>
Subject: RE: Using a shared Guix store (was RE: [Bio-packaging] testing out guix)
Date: Wed, 8 Jul 2015 19:20:09 +0000 [thread overview]
Message-ID: <1436383208498.32759@stowers.org> (raw)
In-Reply-To: <87616k0vvo.fsf@gnu.org>
Hi Ludovic and Ricardo,
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>
> > Even then, /gnu would be mounted read-only on all but the management
> > host, because there would still only be one daemon writing to the
> > store and the localstatedir – even if it would take requests from
> > multiple remote guix clients.
>
> I think $localstatedir (/var/guix by default), or a subset thereof (namely
> /var/guix/profiles/per-user) should be shared read-write over NFS to allow
> users to create the profiles/per-user/$USER symlinks from other machines.
Loduvic, I'm not sure I understand well enough to agree....
Ricardo, I appreciate your fixing my reasoning below....
Certainly per-user profiles must be network readable , since they wind up on PATH. Perhaps within /gnu/guix/profiles/per-user?
However, if `guix` command is enabled (using ssh/pipe/??) to run in networked environment with build and other work continuing to be coordinated by guix-daemon, then updates to per-user profiles similarly would need to be coordinated. For example, if a user wants to `guix package --install somePkg-someVersion` then that package must be protected against any "simultaneous" garbage collection. Running the --install through the network daemon is the guix way of protecting against such a race condition.
On this topic, examining the documentation a bit further makes me wonder whether support for `guix build --root MYROOT` will be impossible when (a) MYROOT is not accessible to the host running guix-daemon. Will this be an issue?
Cheers,
Malcolm
next prev parent reply other threads:[~2015-07-08 19:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 20:22 Using a shared Guix store (was RE: [Bio-packaging] testing out guix) Cook, Malcolm
2015-06-19 8:06 ` Ricardo Wurmus
2015-06-19 11:34 ` Ludovic Courtès
2015-06-25 6:40 ` Ricardo Wurmus
2015-06-19 11:40 ` Ludovic Courtès
2015-07-08 19:20 ` Cook, Malcolm [this message]
2015-07-08 19:43 ` Ricardo Wurmus
2015-06-19 17:48 ` Cook, Malcolm
2015-06-24 19:57 ` Ludovic Courtès
2015-07-08 18:03 ` Cook, Malcolm
2015-07-08 19:53 ` Ricardo Wurmus
2015-07-10 8:39 ` Ludovic Courtès
2015-07-11 0:48 ` Cook, Malcolm
2015-07-13 16:45 ` Test suite failures Ludovic Courtès
2015-07-18 3:04 ` Cook, Malcolm
2015-07-18 15:02 ` Ludovic Courtès
2015-07-11 0:54 ` Using a shared Guix store (was RE: [Bio-packaging] testing out guix) Cook, Malcolm
2015-07-15 15:45 ` Ricardo Wurmus
2015-07-15 19:49 ` Cook, Malcolm
2015-07-15 20:28 ` Pjotr Prins
2015-07-18 9:26 ` Cook, Malcolm
2015-07-18 15:13 ` Ludovic Courtès
2015-07-19 9:18 ` Claes Wallin (韋嘉誠)
2015-07-19 9:33 ` Andreas Enge
2015-07-20 22:37 ` Cook, Malcolm
2015-07-21 20:23 ` Cook, Malcolm
2015-07-21 20:29 ` Ricardo Wurmus
2015-07-23 22:52 ` 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=1436383208498.32759@stowers.org \
--to=mec@stowers.org \
--cc=bio-packaging@mailman.open-bio.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=pjotr.public66@thebird.nl \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).