From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: s6-rc user experience question
Date: Mon, 17 Oct 2022 13:11:46 +0000 [thread overview]
Message-ID: <em65561c96-25a9-4012-8d1b-88060c37b61d@56081f05.com> (raw)
In-Reply-To: <20221016160228.bypf5lyje6wfvbnc@localhost>
>Perhaps I can offer a few suggestions how to improve usability:
> - combine compile + svscan on empty dir + init steps into one, like
> `s6-rc init source_dir` and it does those steps under the hood.
No, because these are operations that are ideally done at different
times.
- Compilation happens "offline", before you (re)boot the machine.
- s6-svscan is run independently from s6-rc, typically very early
during the boot sequence. (Ideally it's process 1.) In any case the
preexistence of a supervision tree is assumed by s6-rc, so spawning
one as part of an s6-rc command isn't good workflow.
- Initialization happens when the service manager is ready to run,
which means when the machine is online and already has an s6-svscan
running.
Combining these operations is only useful if you're doing things in
a very convoluted, suboptimal way.
> - maybe instead of creating file based database take on sqlite as a dependency and keep compiled + live state there? sqlite is
> ubiquitous and very light weight. It can save the trouble of
> inventing our own compiled database formats and folder strucutres
The format of the compiled database is entirely orthogonal to the
usability. Adding a dependency to an external package would do exactly
nothing to improve the UX here; it would just make the code bigger,
slower, more complex, harder to maintain and less secure. And that's
without mentioning that a relational database is not at all the right
structure for the kind of data that s6-rc deals with.
Not a great trade-off, if you ask me.
However, there's a change I can make that would immediately improve
s6-rc's usability: since it's largely a perception issue, changing
the vocabulary from "s6-rc-compile" to "s6-rc-snapshot" and
"compiled database" to "opaque snapshot of the set of services" would
be a good idea. It would spook fewer people, and send fewer people
into red herring trains of thoughts. :)
>What are your plans / thoughts on s6-rc redesign?
It's ongoing. It's difficult, and I always find a myriad of things to
do to distract me from working on it, so it's going (very) slowly. But
it's always lurking in the back of my mind, and there isn't a day that
I don't wonder what I have gotten myself into.
The initial call for funds is still readable here:
https://skarnet.com/projects/service-manager.html
--
Laurent
next prev parent reply other threads:[~2022-10-17 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 6:28 Ihor Antonov
2022-10-16 10:39 ` Laurent Bercot
2022-10-16 16:02 ` Ihor Antonov
2022-10-17 13:11 ` Laurent Bercot [this message]
2022-10-17 15:43 ` Ihor Antonov
2022-10-17 21:32 ` Laurent Bercot
2022-10-18 1:13 ` Alexis
2022-10-18 3:14 ` Ihor Antonov
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=em65561c96-25a9-4012-8d1b-88060c37b61d@56081f05.com \
--to=ska-supervision@skarnet.org \
--cc=supervision@list.skarnet.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.
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 NNTP newsgroup(s).