unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ryan Prior <ryanprior@hey.com>
To: "Ricardo Wurmus" <rekado@elephly.net>, "Ludovic Courtès" <ludo@gnu.org>
Cc: Development of GNU Guix and the GNU System distribution
	<guix-devel@gnu.org>
Subject: Re: guix pack file enumerator?
Date: Tue, 15 Dec 2020 02:43:12 +0000	[thread overview]
Message-ID: <34e794ff8aac520ec79fa3ae359a9ed25f769e5c@hey.com> (raw)
In-Reply-To: <87zh2gvhu5.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

On December 14, 2020, "Ludovic Courtès" <ludo@gnu.org> wrote:
> Here’s another idea: allowing ‘guix copy’ to talk to a “raw” remote
> store—i.e., just /gnu/store + /var/guix/db accessed over SSH.


> Hmm that amounts to implementing a subset of the daemon.

This reminds me of the much-loved "agentless" model of software
deployment as practiced by Ansible. [1] To provision, configure, and
deploy using Ansible all you need on the target machine is Python and
sshd. It copies its tools over, does its work, then cleans up after
itself.

If Guix could deploy to any machine with Guile + sshd that would be a
pretty compelling story. If you could also substitute perl or python or
something more ubiquitous, that would be even stronger, at the cost of
decreased code re-use. Best of all would be a mini-daemon we could
cross-compile for the target architecture, scp over as a single file,
execute there to carry out the rest of the task, then delete if no
longer needed. This approach is used to great effect by the Mgmt
automation tool [2].


[1] White paper (pdf, 5 pages)
https://www.ansible.com/hubfs/pdfs/Benefits-of-Agentless-WhitePaper.pdf
[2] https://github.com/purpleidea/mgmt/

[-- Attachment #2: Type: text/html, Size: 3593 bytes --]

  reply	other threads:[~2020-12-15  2:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06  9:53 guix pack file enumerator? Ricardo Wurmus
2020-12-06 19:33 ` Ryan Prior
2020-12-07 15:14 ` zimoun
2020-12-08 11:13 ` Ludovic Courtès
2020-12-09 11:04   ` Ricardo Wurmus
2020-12-14  9:48     ` Ludovic Courtès
2020-12-15  2:43       ` Ryan Prior [this message]
2020-12-15  9:53         ` Nicolò Balzarotti

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=34e794ff8aac520ec79fa3ae359a9ed25f769e5c@hey.com \
    --to=ryanprior@hey.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=rekado@elephly.net \
    /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).