GNU bug report logs -
#20381
Document how to interact with a remote daemon
Previous Next
Reported by: ludo <at> gnu.org (Ludovic Courtès)
Date: Mon, 20 Apr 2015 12:48:01 UTC
Severity: wishlist
Done: ludo <at> gnu.org (Ludovic Courtès)
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Tue, 25 Apr 2017 12:24:54 +0200
with message-id <8737cwdbt5.fsf <at> gnu.org>
and subject line Re: bug#20381: Interacting with a remote daemon
has caused the debbugs.gnu.org bug report #20381,
regarding Document how to interact with a remote daemon
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
20381: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20381
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
In <http://elephly.net/posts/2015-04-17-gnu-guix.html>, Ricardo notes:
At some point I think it would make sense to enhance Guix such that
RPCs can be made over SSH, so that explicit logging on to a management
machine is no longer necessary.
We should see exactly how much support is needed.
Is ‘socat’ enough, as suggested in
<https://lists.gnu.org/archive/html/guix-devel/2015-02/msg00680.html>?
That means there would be no authentication, but maybe that’s acceptable
in a cluster that is isolated on its own LAN anyway.
Option #2 would be to augment (guix store) and guix-daemon so that there
is built-in support for TCP sockets, which would be slightly more
convenient.
Option #3 would be to make (guix store) SSH-capable, with Guile-SSH.
But it sounds like SSH would incur relatively high latency when
connecting to the daemon.
There remains the problem that /var/guix/profiles/per-user/$USER would
have to be writable to this to be useful.
Thoughts?
Ludo’.
[Message part 3 (message/rfc822, inline)]
Hello!
ludo <at> gnu.org (Ludovic Courtès) skribis:
> In <http://elephly.net/posts/2015-04-17-gnu-guix.html>, Ricardo notes:
>
> At some point I think it would make sense to enhance Guix such that
> RPCs can be made over SSH, so that explicit logging on to a management
> machine is no longer necessary.
>
> We should see exactly how much support is needed.
>
> Is ‘socat’ enough, as suggested in
> <https://lists.gnu.org/archive/html/guix-devel/2015-02/msg00680.html>?
> That means there would be no authentication, but maybe that’s acceptable
> in a cluster that is isolated on its own LAN anyway.
>
> Option #2 would be to augment (guix store) and guix-daemon so that there
> is built-in support for TCP sockets, which would be slightly more
> convenient.
>
> Option #3 would be to make (guix store) SSH-capable, with Guile-SSH.
> But it sounds like SSH would incur relatively high latency when
> connecting to the daemon.
I think this is fixed by this series of commits:
285f63e80 * store: Support 'ssh://' URIs in 'GUIX_DAEMON_SOCKET'.
e53783372 * ssh: Decompose 'connect-to-remote-daemon'.
615c5298f * ssh: Move 'open-ssh-session' to (guix ssh).
ba97e454b * offload: Avoid using '_' as a 'match' pattern.
3dff90ce3 * store: Add support for remote connections via 'guix://' URIs.
3b5cd17a9 * store: Add 'system-error-to-connection-error' macro.
1397b422e * store: 'GUIX_DAEMON_SOCKET' can now be a URI.
with the caveats given here:
https://lists.gnu.org/archive/html/guix-devel/2017-04/msg00487.html
Closing!
Ludo’.
This bug report was last modified 8 years and 33 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.