From: "Ludovic Courtès" <ludo@gnu.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [GSOC 2020] Guix Deploy, round 2!
Date: Mon, 09 Mar 2020 17:49:55 +0100 [thread overview]
Message-ID: <87d09l1nik.fsf@gnu.org> (raw)
In-Reply-To: <CAE4v=phy16AJWxxsZg9wr2tdqY1c2RBhnvuj7OX=Q7eHKECrDQ@mail.gmail.com> ("Gábor Boskovits"'s message of "Mon, 9 Mar 2020 06:58:58 +0100")
Hi!
Gábor Boskovits <boskovits@gmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> ezt írta (időpont: 2020. márc. 8., Vas
> 23:10):
[...]
>> What I miss the most, especially on the build farm, is the ability to
>> tell ‘guix deploy’ which services to restart upon completion.
>> Currently, like ‘guix system reconfigure’, it conservatively doesn’t
>> restart any running services. However, often, you’d like it to run
>> “herd restart X” upon completion.
>>
>> Another thing discussed at the Guix Days, but more relevant to more
>> advanced use cases, is the ability to define “roles”: often you’d rather
>> want to think in terms of the services machines offer and abstract over
>> the actual machines.
>>
>
> These are both great ideas. It would be also nice to access these in a
> single machine setup. I don't know where to implement this, it might make
> sense to add these to the common part of deploy and reconfigure. IIRC we
> also discussed the idea of a local deployer to be able handle the deploy
> node the same way as the rest.
If you talking about the first point above, I think it’s not that
difficult. As I see it, we could provide a command-line option and/or a
<machine> option (?) specifying which services should be restarted right
away. Restarting can be implemented as in (guix scripts system
reconfigure).
> Regarding the roles thing it would be nice to get a discussion going
> regarding the interface, so that we have an idea how it should look
> like. Wdyt?
Yes, that would be nice! There were good ideas discussed at the Guix
Days and knowledgeable people, but I can’t see the notes at
<https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/guix-days-2020>
and I’m not sure who was involved. There was probably Chris Marusich,
who else? People, please step up! :-)
Ludo’.
next prev parent reply other threads:[~2020-03-09 16:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAn03x7H2ZUg7i=6U_fcd37_KtZ5J59XTwE=sEkLmHm5h8EECQ@mail.gmail.com>
2020-02-26 22:07 ` [GSOC 2020] Discussing GNU Guix project ideas? Leandro Doctors
2020-02-27 8:16 ` Ricardo Wurmus
2020-02-27 11:52 ` Leandro Doctors
2020-02-27 14:28 ` Leandro Doctors
2020-02-27 14:44 ` zimoun
2020-02-28 0:22 ` [GSOC 2020] Improving the manual? Leandro Doctors
2020-02-28 0:37 ` zimoun
2020-02-28 0:46 ` Leandro Doctors
2020-02-28 0:39 ` sirgazil
2020-02-28 0:37 ` [GSOC 2020] Idea: Guile based build-tool Leandro Doctors
2020-02-29 13:56 ` Christopher Lemmer Webber
2020-03-02 10:02 ` zimoun
2020-03-03 11:24 ` Leandro Doctors
2020-02-29 16:54 ` [GSOC 2020] Guix Deploy, round 2! Christopher Lemmer Webber
2020-02-29 17:55 ` Gábor Boskovits
2020-03-08 22:10 ` Ludovic Courtès
2020-03-09 5:58 ` Gábor Boskovits
2020-03-09 16:49 ` Ludovic Courtès [this message]
2020-03-03 22:32 ` [GSOC 2020] Discussing GNU Guix project ideas? zimoun
2020-03-03 22:44 ` Leandro Doctors
2020-03-04 9:58 ` Gábor Boskovits
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=87d09l1nik.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
/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).