public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: alexander.heinisch@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH 0/6] Add target bootstrapper framework
Date: Tue, 14 Oct 2025 16:59:49 +0200	[thread overview]
Message-ID: <03775d5b-497a-4935-91ca-ac4b81086e9b@ilbers.de> (raw)
In-Reply-To: <20250922170445.1393839-1-alexander.heinisch@siemens.com>

Applied to next, thanks.

On 9/22/25 19:04, alexander.heinisch via isar-users wrote:
> From: Alexander Heinisch<alexander.heinisch@siemens.com>
>
> Currently the installer deploys images embedded to itself.
>
> In many situations this is fine, but for some more demanding requirements
> are in place. e.g.:
> - enrollment of keys (e.g. Secure Boot),
> - setup for disk encryption,
> - collection and reporting of device information (serial number, mac addresses, ...)
> - resize / repartition of disk during comissioning
> - generation of a commissioning report
>
> While many of these tasks can be done on first-boot doing so during
> device setup can be beneficial in many cases.
> e.g.
> - additional time required for "first-boot" when performing tasks
> with high effort on site may not be desired
> - the comissioning environment oftentimes allows for failures during
> that phase - worst case the device is put aside. On site failures during
> the wrong bootstrapping phases (secure boot setup, disk encryption)
> can be severe.
>
> This patch extends current installer behaviour to support a flexible
> framework to define multiple tasks to be executed in sequence during
> the "target (device) bootstrapping" phase.
>
> Note: Current patchset uses installer and target-bootstrapper interchangeably.
> Imo the name target-bootstrapper fits better to the actual purpose,
> while installer is already established for some time in isar and changing
> the naming would probably break some downstream. Although, that could be
> fixed in a backwards compatible way, I left this exercise open upon agreement.
>
> Alexander Heinisch (6):
>    isar-installer: Moved installer related Kconfig to separate file.
>    isar-installer: Added target bootstrapper framework
>    isar-installer: Use target-bootstrapper-service in favour of
>      deploy-image-service
>    isar-installer: Removed deploy-image-service
>    isar-installer: Fixing race between ttys in unattended mode.
>    isar-installer: Added example target bootstrapper task to collect
>      device information.
>
>   kas/image/Kconfig                             |  83 ++------------
>   kas/image/isar-image-installer.yaml           |   6 +
>   kas/installer/Kconfig                         | 104 ++++++++++++++++++
>   kas/installer/add-device-info-collector.yaml  |  14 +++
>   kas/installer/unattended.yaml                 |  18 +++
>   meta-isar/classes/target-bootstrapper.bbclass |  37 +++++++
>   .../images/isar-image-installer.bb            |   2 +-
>   .../deploy-image-service.bb                   |  21 ----
>   .../files/install.override.conf               |   5 -
>   .../device-info-collector.bb                  |  27 +++++
>   .../files/usr/bin/device-info-collector.sh    |  28 +++++
>   .../files/target-bootstrapper.override.conf   |   3 +
>   .../target-bootstrapper-service.bb            |  38 +++++++
>   .../files/target-bootstrapper.sh.tmpl         |  44 ++++++++
>   .../target-bootstrapper.bb                    |  41 +++++++
>   15 files changed, 369 insertions(+), 102 deletions(-)
>   create mode 100644 kas/installer/Kconfig
>   create mode 100644 kas/installer/add-device-info-collector.yaml
>   create mode 100644 kas/installer/unattended.yaml
>   create mode 100644 meta-isar/classes/target-bootstrapper.bbclass
>   delete mode 100644 meta-isar/recipes-installer/deploy-image-service/deploy-image-service.bb
>   delete mode 100644 meta-isar/recipes-installer/deploy-image-service/files/install.override.conf
>   create mode 100644 meta-isar/recipes-installer/device-info-collector/device-info-collector.bb
>   create mode 100755 meta-isar/recipes-installer/device-info-collector/files/usr/bin/device-info-collector.sh
>   create mode 100644 meta-isar/recipes-installer/target-bootstrapper-service/files/target-bootstrapper.override.conf
>   create mode 100644 meta-isar/recipes-installer/target-bootstrapper-service/target-bootstrapper-service.bb
>   create mode 100644 meta-isar/recipes-installer/target-bootstrapper/files/target-bootstrapper.sh.tmpl
>   create mode 100644 meta-isar/recipes-installer/target-bootstrapper/target-bootstrapper.bb
>
> --
> 2.39.5
>

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/03775d5b-497a-4935-91ca-ac4b81086e9b%40ilbers.de.

      parent reply	other threads:[~2025-10-14 15:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 17:04 alexander.heinisch via isar-users
2025-09-22 17:04 ` [PATCH 1/6] isar-installer: Moved installer related Kconfig to separate file alexander.heinisch via isar-users
2025-09-22 17:04 ` [PATCH 2/6] isar-installer: Added target bootstrapper framework alexander.heinisch via isar-users
2025-09-22 17:04 ` [PATCH 3/6] isar-installer: Use target-bootstrapper-service in favour of deploy-image-service alexander.heinisch via isar-users
2025-09-22 17:04 ` [PATCH 4/6] isar-installer: Removed deploy-image-service alexander.heinisch via isar-users
2025-09-22 17:04 ` [PATCH 5/6] isar-installer: Fixing race between ttys in unattended mode alexander.heinisch via isar-users
2025-09-22 17:04 ` [PATCH 6/6] isar-installer: Added example target bootstrapper task to collect device information alexander.heinisch via isar-users
2025-10-14 14:59 ` Zhihang Wei [this message]

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=03775d5b-497a-4935-91ca-ac4b81086e9b@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=alexander.heinisch@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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