| Message ID | 20241008094902.24179-1-alexander.heinisch@siemens.com |
|---|---|
| Headers | show |
| Series | meta-isar: Split deploy image script and deploy image in preparation for a target-bootstrapper | expand |
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.
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%)