public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: alexander.heinisch@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH 0/1] meta-isar: Split deploy image script and deploy image in preparation for a target-bootstrapper
Date: Mon, 14 Oct 2024 20:28:24 +0300	[thread overview]
Message-ID: <9a76939b11c17cff0c75ffed15ec5c5965dbb4a8.camel@ilbers.de> (raw)
In-Reply-To: <20241008094902.24179-1-alexander.heinisch@siemens.com>

On Tue, 2024-10-08 at 11:49 +0200, alexander.heinisch via isar-users
wrote:
> 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
> 

Applied to next, thanks.

-- 
Best regards,
Uladzimir.



-- 
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/9a76939b11c17cff0c75ffed15ec5c5965dbb4a8.camel%40ilbers.de.

      parent reply	other threads:[~2024-10-14 17:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  9:49 alexander.heinisch via isar-users
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 ` Uladzimir Bely [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=9a76939b11c17cff0c75ffed15ec5c5965dbb4a8.camel@ilbers.de \
    --to=ubely@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