From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: Public guix offload server
Date: Fri, 29 Oct 2021 14:01:17 +0200 [thread overview]
Message-ID: <87o8782g6q.fsf@gnu.org> (raw)
In-Reply-To: <87cznz74l5.fsf@nckx> (Tobias Geerinckx-Rice's message of "Wed, 20 Oct 2021 23:06:05 +0200")
Hi,
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> Arun Isaac 写道：
[...]
>> Currently, guix offload requires mutual trust between the master
>> and the build machines. If we could make the trust only one-way,
>> security might be less of an issue.
>
> It might! It's easy to imagine a second, less powerful offload
> protocol where clients can submit only derivations to be built by
> the remote daemon, plus fixed-output derivations.
One thing that does not require mutual trust, roughly like you describe
is:
GUIX_DAEMON_SOCKET=ssh://guix.example.org guix build …
We could have an HTTP bridge and that’d be workable. It could be just
streaming the daemon RPCs as-is on websockets, or defining an HTTP API
for each useful RPC.
Perhaps some of this can be also addressed with the Guix Build
Coordinator, which already provides an HTTP API, although a higher-level
one. Chris?
>> WDYT? How does everyone else handle big builds? Do you have access
>> to
>> powerful workstations?
I have a 4-core Intel i7 laptop, which is okay for many things, and I
also have access to a couple of 32-core machines when I need to test
bigger builds like GCC. And then there’s waiting for ci.guix feedback.
Ludo’.
next prev parent reply other threads:[~2021-10-29 12:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 20:53 Public guix offload server Arun Isaac
2021-10-20 21:06 ` Tobias Geerinckx-Rice
2021-10-20 22:54 ` Leo Famulari
2021-10-21 16:46 ` Tobias Geerinckx-Rice
2021-10-21 8:12 ` zimoun
2021-10-21 16:31 ` Tobias Geerinckx-Rice
2021-10-21 18:04 ` zimoun
2021-10-21 21:15 ` Jonathan McHugh
2021-10-21 21:51 ` zimoun
2021-10-21 22:16 ` Tobias Geerinckx-Rice
2021-10-22 7:33 ` zimoun
2021-10-23 5:49 ` Arun Isaac
2021-10-23 7:23 ` zimoun
2021-10-24 6:43 ` Arun Isaac
2021-10-25 9:27 ` indieterminacy
2021-10-22 7:23 ` Jonathan McHugh
2021-10-21 20:23 ` Arun Isaac
2021-10-29 12:04 ` Ludovic Courtès
2021-10-29 12:01 ` Ludovic Courtès [this message]
2021-10-20 22:56 ` Leo Famulari
2021-10-21 15:49 ` Joshua Branson
2021-10-21 16:41 ` Tobias Geerinckx-Rice
2021-10-21 17:22 ` Vagrant Cascadian
2021-10-29 12:06 ` Ludovic Courtès
2021-10-29 12:44 ` Tobias Geerinckx-Rice
2021-10-21 23:40 ` jbranso
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=87o8782g6q.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).