From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>, guix-devel@gnu.org
Cc: guix-sysadmin <guix-sysadmin@gnu.org>
Subject: Re: Sustainable funding and maintenance for our infrastructure
Date: Mon, 08 Jul 2024 08:46:47 -0700 [thread overview]
Message-ID: <87r0c3dgyg.fsf@wireframe> (raw)
In-Reply-To: <87sewr98jd.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]
On 2024-07-02, Ludovic Courtès wrote:
> We (Andreas, Chris, Ricardo, Romain, and myself) were having a
> discussion about what it would take to set up a build farm similar to
> what’s behind ci.guix: roughly 30 x86_64 servers, with 32-core/64-thread
> CPUs and 128 GiB of RAM. The reason for this discussion is that we were
> thinking that we should not take our existing build farms for granted
> and be prepared for the future.
>
> The various options and back-of-the-envelope estimates we came up with
> are as follows:
>
> 1. Buying and hosting hardware:
> 250k€ for hardware
> 3k€/month (36k€/year)
>
> 2. Renting machines (e.g., on Hetzner):
> 6k€/month (72k€/year)
>
> 3. Sponsored:
> get hardware and/or hosting sponsored (by academic institutions or
> companies).
This may be a little wild, but what are the downsides to doing some
combination of all of the above? Maybe higher bandwidth requirements
between the various pieces of infrastructure presumably being hosted in
different locations? Maybe also a little more complexity in the overall
setup?
A mixed strategy could reduce ... the upfront cost of buying and hosting
hardware (#1), the ongoing costs of renting (#2), and dependence on the
generosity of a third party for sponsored hardware & hosting (#3).
It seems like any strategy should have some redundancy (e.g. multiple
independent build farms) so that a failure in one datacenter does not
effectively take down the whole network...
In a sense, we already have some of that, with ci.guix.gnu.org and
bordeaux.guix.gnu.org, and also the new North American build farm
... though they are not full replacements for each other.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2024-07-08 15:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 14:24 Sustainable funding and maintenance for our infrastructure Ludovic Courtès
2024-07-03 1:13 ` indieterminacy
2024-07-04 16:37 ` Simon Tournier
2024-07-08 12:02 ` Ricardo Wurmus
2024-07-09 14:49 ` Simon Tournier
2024-07-11 9:23 ` Ludovic Courtès
2024-07-08 15:46 ` Vagrant Cascadian [this message]
2024-07-08 18:28 ` Vincent Legoll
2024-07-09 9:47 ` Tomas Volf
2024-07-11 10:33 ` Andreas Enge
2024-07-11 20:44 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-07-11 9:38 ` Ludovic Courtès
2024-07-12 10:44 ` Simon Tournier
2024-07-21 12:52 ` Ludovic Courtès
2024-07-08 16:27 ` Efraim Flashner
2024-07-08 17:21 ` Enrico Schwass
2024-07-11 10:48 ` Andreas Enge
2024-07-11 9:28 ` Ludovic Courtès
2024-08-01 22:11 ` Marek Paśnikowski
2024-08-13 2:53 ` Jonathan Frederickson
2024-08-13 16:23 ` Sergio Pastor Pérez
2024-08-13 23:38 ` Jonathan Frederickson
2024-08-14 13:21 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-08-24 23:15 ` Jonathan Frederickson
2024-08-21 22:07 ` P2P Guix package building and distribution Christine Lemmer-Webber
2024-08-22 9:05 ` Andreas Enge
2024-08-22 21:57 ` Samuel Christie via Development of GNU Guix and the GNU System distribution.
-- strict thread matches above, loose matches on Subject: below --
2024-07-02 14:26 Sustainable funding and maintenance for our infrastructure 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=87r0c3dgyg.fsf@wireframe \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=ludo@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.
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).