From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id IJRTDAIphGZWhwAA62LTzQ:P1 (envelope-from ) for ; Tue, 02 Jul 2024 16:21:22 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id IJRTDAIphGZWhwAA62LTzQ (envelope-from ) for ; Tue, 02 Jul 2024 18:21:22 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=CXQoli5E; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gnu.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1719937282; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=ankMW7HPAtGOXIeyPma/v4mRf+KL/dOImfqYvQu/HNU=; b=C2zlMRlTJRvyHpaaP3JwUsj6jUUyWnidhy3pjwbr+fIbrPYWFXLl8j9VZtHRLE/3hlwCKS UBC3jlzXceycUV4yWFblGGqfXPql7C0KqXi+ECMIrtNxXPJylCmxwGIUjtK2S9orklhJ+d ioRrGeT9rkRpl10yJ8AqSBW+0DWikaHZNEsIsn+Ep07sFabFudbDp8eGaUBq/8gVfIIK9A cIgZamqESzmjRPIrBW7BRwA4+M6l8MGV77EVvOrQlgWFyIwVDJcOcErEl0NDf+vCenHhTT zS0x4yRWC1yoWsFeyyPbx3g/jpNLOn3V3pOLSntREVt2iD/KSD9xHKcIRonNMA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=CXQoli5E; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gnu.org ARC-Seal: i=1; s=key1; d=yhetil.org; t=1719937282; a=rsa-sha256; cv=none; b=i5ngFUvjUcY4DHOZWxZie0ViSyFxH+BG0CCyKHqOchByiQfFOZpSYlPkW0VZpFLwO+QSbF EtN+pfNEMsgIOiVAOpOJNlHmlReO7+rUgmT/RH3q/KOeMuu+7Tnve4+Oj/JIMBlDlmuvKI GfLIoFGYoRudmPtqjrmuAqwtNBOInf28Mmr5Z7YOK0LbCD/vUjqxKNuYUKhpYDArqJyUQw xudkJTCIc2xZWntgnQ4fIo/QB58/KzaLKQKwkgf+mwmEWkMRvz1/J7mSzr0tlrSOgwE9RR /E6JWN3lNNinHXVnxR/NbY4Jlt/SC3J0dDrGLAvVU+4cnGScxNZYkEG8JDswhA== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 607AF27A06 for ; Tue, 2 Jul 2024 18:21:21 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sOeQv-0006QF-CB; Tue, 02 Jul 2024 10:24:37 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sOeQu-0006Iy-03; Tue, 02 Jul 2024 10:24:36 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sOeQt-0002EM-LN; Tue, 02 Jul 2024 10:24:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:Subject:To:From:in-reply-to: references; bh=ankMW7HPAtGOXIeyPma/v4mRf+KL/dOImfqYvQu/HNU=; b=CXQoli5Eg0bOAv sxGcsRSz0zj2MntJXlZqyl6FaQV1dA5DhflNS5gXuFYTeyL7zt7oGtO2H3Fv3ZDvaCyAhr5mzFIHI 81sBRfv2HzJbpwXIeDoKp76wUOTvslU4PoVqRj98JNR64E5EcKmv1LL5NeBcJhw+HcAVA2N2Q3YsU t3FBVu38RzgVaCBM0OUQfbqtHYKzrR+Vy8c3H2fpbWSEqOAPy71qR7/RivVQXp4iDjj6hHAHmzo3t MI6kyrMTUypUOHIYjZMVJHPO8YatWM8KidnOCx2Zl975arQardAMlrVehH5SvFFZRd35LX456/GMC Mc2sSGyEpjhRketXP5tw==; From: =?utf-8?Q?Ludovic_Court=C3=A8s?= To: guix-devel@gnu.org Subject: Sustainable funding and maintenance for our infrastructure CC: guix-sysadmin X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: Quintidi 15 Messidor an 232 de la =?utf-8?Q?R=C3=A9v?= =?utf-8?Q?olution=2C?= jour du Chamois X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-pc-linux-gnu Date: Tue, 02 Jul 2024 16:24:06 +0200 Message-ID: <87sewr98jd.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Spam-Score: -3.70 X-Migadu-Queue-Id: 607AF27A06 X-Migadu-Scanner: mx10.migadu.com X-Migadu-Spam-Score: -3.70 X-TUID: u7qgzN6Hl5Y/ Hello Guix! 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=E2=80=99s behind ci.guix: roughly 30 x86_64 servers, with 32-core/64-t= hread 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=E2=82=AC for hardware 3k=E2=82=AC/month (36k=E2=82=AC/year) 2. Renting machines (e.g., on Hetzner): 6k=E2=82=AC/month (72k=E2=82=AC/year) 3. Sponsored: get hardware and/or hosting sponsored (by academic institutions or companies). Option #1 gives us =E2=80=9Cfull control=E2=80=9D, the downside being that = it=E2=80=99s a lot of work and a real burden (get crowdfunding for the initial funding, later on to sustain funding to cover hosting, ensure Guix Foundation is up to the task of managing the assets, and of course to take care of the machines for their entire lifecycle). Option #2 gives us less control (we don=E2=80=99t know exactly what hardwar= e is being used and have to trust the company hosting the machines). The upside is that it=E2=80=99s much less work over time (the company is respon= sible for upgrading hardware) and less work initially (no need to raise as much money to buy hardware). Option #3 potentially gives less control (depending on the project=E2=80=99s relation with the hosting organization) and makes the project dependent on the sponsor and/or person(s) in touch with them. On the upside, it could significantly reduce costs (potentially to 0=E2=82=AC). This is an important topic for the project, one we should plan for: socially, financially, technically. This takes time, which is why preparation is needed. What do people think? Ludo=E2=80=99 & co.