From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 53486@debbugs.gnu.org
Subject: [bug#53486] [PATCH] deploy: Add '--execute'.
Date: Tue, 01 Feb 2022 20:32:12 +0100 [thread overview]
Message-ID: <87mtjatmbn.fsf_-_@gnu.org> (raw)
In-Reply-To: <87tudj8qi3.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 31 Jan 2022 23:48:53 +0100")
Hi,
Ricardo Wurmus <rekado@elephly.net> skribis:
> This sure is useful, but for the very first time I feel that this
> doesn’t quite belong. There are a bunch of tools out there that focus
> exclusively on remote execution on several machines at once.
>
> One of them is pdsh, which lets you also define groups of machines by
> type and submit to a selected subset. It also displays remote output
> locally, and it sends local input to the remote as well.
>
> It’s tempting to add this to “guix deploy” because it likely that
> parallel remote execution is desired when “guix deploy” is used, but it
> also feels … kinda wrong.
True, but here that allows you to talk to the machines actually listed
in ‘deploy.scm’. Were you to use an external tool, you’d have to
somehow grep/sed the thing to get a list of host names.
> I wonder if there’s a Guixy spin on remote execution — the
> aforementioned “deploy-hook” feels more at home here, in my opinion.
Yes, and it would use the same mechanism. It would also more pleasant
for things you want to routinely do after a deployment.
Still, sometimes you just want to run “uname -a” or something to see if
you rebooted the machines, and a deploy hook won’t help with it.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-02-01 22:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 21:21 [bug#53486] [PATCH] deploy: Add '--execute' Ludovic Courtès
2022-01-29 13:16 ` Oleg Pykhalov
2022-01-31 22:44 ` Ludovic Courtès
2022-01-31 22:48 ` Ricardo Wurmus
2022-02-01 19:32 ` Ludovic Courtès [this message]
2022-02-01 20:08 ` Ricardo Wurmus
2022-02-02 17:44 ` bug#53486: " 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=87mtjatmbn.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=53486@debbugs.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 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.