From: richard.purdie@linuxfoundation.org
To: Alex Kiernan <alex.kiernan@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v5 0/6] Fix systemd service enables/move towards "stateless" configuration
Date: Tue, 30 Apr 2019 11:59:51 +0100 [thread overview]
Message-ID: <546ea9e32e2fb9ffa97aae5fbd328f653a1949b5.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190429144325.63744-1-alex.kiernan@gmail.com>
On Mon, 2019-04-29 at 15:43 +0100, Alex Kiernan wrote:
> This is largely Jonas Bonn <jonas@norrbonn.se> patchset to move
> towards a
> "stateless" configuration:
>
> These patches make some modifications to systemd with the long-term
> goal
> of being able to run OE in systemd's "stateless" configuration.
> "Stateless" boils down to building an image with empty /etc and
> /var
> directories so that volatile (tmpfs) filesystems can be mounted
> there;
> this requires that the system subsequently be able to populate
> these
> directories dynamically, which systemd mostly takes care of if
> things are
> done right.
>
> In these patches:
> i) Don't include machine-id in writable images so that systemd
> can run
> its first-boot machinery
> ii) Move systemd configuration files out of /etc
> iii) Allow systemd to dynamically enable services and populate
> /etc/systemd/system via the presets mechanism
>
> There's a long way to go to get to a working "stateless"
> configuration.
> Getting to a "volatile" system (just empty /var) should be easier
> and I'll
> post patches moving things in that direction shortly.
>
> As a result of the systemd 242 upgrade, which includes 01d2041e41f4
> ("meson: stop creating enablement symlinks in /etc during
> installation"), services such as systemd-networkd are no longer
> enabled
> in images.
>
> This patch set fixes this problem in addition to satisfying the goal
> of
> moving towards "stateless" configurations.
>
> The issue with respect to image testing during CI was caused by
> systemd-time-wait-sync.service being enabled due to the lack of a
> default preset policy:
>
> https://www.freedesktop.org/wiki/Software/systemd/Preset/#howto
>
> We include a default policy of "enable nothing" which matches that
> used
> by (at least) Arch and Fedora.
>
> Changes in v5:
> - rebased for systemd 242
> - install default preset distribution policy of "enable nothing"
>
> Changes in v4:
> - add patch to make systemd-firstboot a non-default option to systemd
> to
> prevent unexpected prompts at runtime
>
> Changes in v3:
> - parameterize preset-file installation location (as suggested in
> patch
> review)
>
> Changes in v2:
> - address patchtest warnings:
> - include sign-offs on patches
> - include License-Update tag on patch that makes licensing change
> - dropped patch implementing brute-force removal of unit files
> installed
> by systemd into /etc
> - reworked the systemd-conf patch to restore the installation of the
> base systemd configuration files
>
> Jonas Bonn (6):
> systemd: don't build firstboot by default
> systemd: do not create machine-id
> systemd-conf: simplify creation of machine-specific configuration
> systemd: create preset files instead of installing in image
> systemd-systemctl-native: simplify and support preset-all
> rootfs-postcommands: call preset-all for read-only-rootfs
I think this is close but in one of our test configurations it appears
the ssh server isn't starting:
https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/548
(the stdio log shows the configuration its building for step 6 and
step6c shows it failing to ssh into the image)
I reran it and the same error happened twice so it is consistent.
Cheers,
Richard
next prev parent reply other threads:[~2019-04-30 10:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 14:43 [PATCH v5 0/6] Fix systemd service enables/move towards "stateless" configuration Alex Kiernan
2019-04-29 14:43 ` [PATCH v5 1/6] systemd: don't build firstboot by default Alex Kiernan
2019-04-29 14:43 ` [PATCH v5 2/6] systemd: do not create machine-id Alex Kiernan
2019-04-29 14:43 ` [PATCH v5 3/6] systemd-conf: simplify creation of machine-specific configuration Alex Kiernan
2019-04-29 14:43 ` [PATCH v5 4/6] systemd: create preset files instead of installing in image Alex Kiernan
2019-04-29 14:43 ` [PATCH v5 5/6] systemd-systemctl-native: simplify and support preset-all Alex Kiernan
2019-04-30 10:31 ` Alex Kiernan
2019-04-29 14:43 ` [PATCH v5 6/6] rootfs-postcommands: call preset-all for read-only-rootfs Alex Kiernan
2019-04-30 10:59 ` richard.purdie [this message]
2019-04-30 11:45 ` [PATCH v5 0/6] Fix systemd service enables/move towards "stateless" configuration Alex Kiernan
2019-04-30 11:52 ` Alex Kiernan
2019-04-30 12:02 ` Paul Barker
2019-04-30 12:13 ` Alex Kiernan
2019-04-30 12:24 ` Paul Barker
2019-04-30 12:33 ` Alex Kiernan
2019-04-30 12:37 ` Paul Barker
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=546ea9e32e2fb9ffa97aae5fbd328f653a1949b5.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kiernan@gmail.com \
--cc=openembedded-core@lists.openembedded.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