From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: GSoC project ideas
Date: Wed, 25 Feb 2015 00:25:38 +0100 [thread overview]
Message-ID: <87a9027uz1.fsf@gnu.org> (raw)
In-Reply-To: <idjr3tfgv8t.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Tue, 24 Feb 2015 16:54:58 +0100")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> Could using Guile SSH for build offloading be made a project or is this
> the scope not big enough?
Not big enough I guess (and it’s partly done in wip-guile-ssh, the
missing bits being mostly in Guile-SSH itself.)
> This might also be extended to allow Guix clients to communicate with a
> remote Guix daemon, all operating on a shared store. This would be a
> special case of offloading where the remote build machine is always used
> and no local Guix daemon needs to run at all.
Too small, I think.
It just occurred to me that this may be possible to solve it simply with
‘socat’.
On the machine that runs guix-daemon, run:
socat TCP4-LISTEN:9999 UNIX:/var/guix/daemon-socket/socket
On the other one, run:
socat UNIX-LISTEN:$PWD/foo TCP4:the-other-machine:9999 &
export GUIX_DAEMON_SOCKET=$PWD/foo
Does it work for you?
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-02-24 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 15:45 GSoC project ideas Ludovic Courtès
2015-02-24 15:54 ` Ricardo Wurmus
2015-02-24 23:25 ` Ludovic Courtès [this message]
2015-02-25 6:45 ` Manolis Ragkousis
2015-02-25 15:34 ` Ludovic Courtès
2015-02-25 15:33 ` Ludovic Courtès
2015-02-26 15:50 ` Thompson, David
2015-02-26 16:47 ` Ludovic Courtès
2015-02-27 13:01 ` David Thompson
2015-02-27 17:13 ` Ludovic Courtès
2015-03-04 23:04 ` David Thompson
2015-03-06 12:36 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9027uz1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.