From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Etienne B. Roesch" <etienne.roesch@gmail.com>
Cc: <help-guix@gnu.org>, <guix-science@gnu.org>
Subject: Re: guix on nfs based systems
Date: Thu, 14 Dec 2023 15:41:19 +0100 [thread overview]
Message-ID: <87ttokalmx.fsf@mdc-berlin.de> (raw)
In-Reply-To: <CAPX-MzDQFpfZsu8CRsxUL4M-xSYb13sxm1O4LVVHLPdPmLk6QA@mail.gmail.com>
Hi Etienne,
FWIW at the MDC we’ve been doing the same: on all nodes mount /gnu read-only, mount
/var/guix read-write; provide a “guix” executable that sets
GUIX_DAEMON_SOCKET and disables/discourages “guix gc”.
> Thanks! That's really helpful! How robust is your system to bandwidth
> fluctuations and network hiccups?
Network reliability has never been an issue for us when it comes to
Guix. We serve /gnu redundantly with pacemaker so that we can take down
one of the two Guix servers (they are VMs) without affecting
availibility of programs and files on /gnu.
> How big is your store, /gnu, /var/guix?
We have about 2TB for /gnu. We never run “guix gc” because the Guix
servers have no access to all the users’ shares, so it would be overly
aggressive in determining garbage.
> How many users do you have?
About 200.
--
Ricardo Wurmus
System administrator
BIMSB - Scientific Bioinformatics Platform
Max Delbrueck Center for Molecular Medicine
email: ricardo.wurmus@mdc-berlin.de
tel: +49 30 9406 1796
next prev parent reply other threads:[~2023-12-14 14:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPX-MzA5P1A8u8QbR-g-Lx4gONQ+o7mO1TZzhZ3UHh=KdUxhvw@mail.gmail.com>
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 [this message]
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=87ttokalmx.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=etienne.roesch@gmail.com \
--cc=guix-science@gnu.org \
--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).