[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#53486] [PATCH] deploy: Add '--execute'.
From: |
Ricardo Wurmus |
Subject: |
[bug#53486] [PATCH] deploy: Add '--execute'. |
Date: |
Tue, 01 Feb 2022 21:08:41 +0100 |
User-agent: |
mu4e 1.6.10; emacs 27.2 |
Ludovic Courtès <ludo@gnu.org> writes:
> 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.
That’s a good point.
>> 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.
As a stepping stone towards something more … “ordered” I guess my
objections to the feature melt away :) Don’t let me be in the way!
--
Ricardo