public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "alexander.heinisch via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: quirin.gylstorff@siemens.com,
	Alexander Heinisch <alexander.heinisch@siemens.com>
Subject: [PATCH 0/1] meta-isar: Split deploy image script and deploy image in preparation for a target-bootstrapper
Date: Tue,  8 Oct 2024 11:49:01 +0200	[thread overview]
Message-ID: <20241008094902.24179-1-alexander.heinisch@siemens.com> (raw)

From: Alexander Heinisch <alexander.heinisch@siemens.com>

We are working on a target-bootstrapper to solve some of the issues stated here: https://groups.google.com/g/isar-users/c/ta0G_KGS_yU
For downstream projects, this enables to not only copy the image to the target, but
increases flexibility to certain comissioning tasks like:
- Downloading images from a server/S3/...
- Encryption of devices after image deployment
- Enrollment of secure boot keys
- Generating and uploading commissioning reports.
- "offline" device onboarding

The target-bootstrapper itself is not included here, and will be submitted separately, once matured enough!

Still to bring more flexibility to downstream projects it is valuable to separate the
actual deploy image logic from the service itself.


Alexander Heinisch (1):
  meta-isar: Split deploy image script and deploy image service.

 .../images/isar-image-installer.bb            |  2 +-
 .../deploy-image-service.bb                   | 21 +++++++++++++++++++
 .../files/install.override.conf               |  0
 .../deploy-image/deploy-image_0.1.bb          |  8 ++-----
 4 files changed, 24 insertions(+), 7 deletions(-)
 create mode 100644 meta-isar/recipes-installer/deploy-image-service/deploy-image-service.bb
 rename meta-isar/recipes-installer/{deploy-image => deploy-image-service}/files/install.override.conf (100%)

-- 
2.43.0

-- 
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 on the web visit https://groups.google.com/d/msgid/isar-users/20241008094902.24179-1-alexander.heinisch%40siemens.com.

             reply	other threads:[~2024-10-08  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  9:49 alexander.heinisch via isar-users [this message]
2024-10-08  9:49 ` [PATCH 1/1] meta-isar: Split deploy image script and deploy image service alexander.heinisch via isar-users
2024-10-14 17:28 ` [PATCH 0/1] meta-isar: Split deploy image script and deploy image in preparation for a target-bootstrapper Uladzimir Bely

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=20241008094902.24179-1-alexander.heinisch@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=alexander.heinisch@siemens.com \
    --cc=quirin.gylstorff@siemens.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