From: "'Heinisch, Alexander' via isar-users" <isar-users@googlegroups.com>
To: "quirin.gylstorff@siemens.com" <quirin.gylstorff@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: RE: [meta-isar] Proposal to improve initial device bootstrapping
Date: Thu, 18 Jul 2024 11:34:34 +0000 [thread overview]
Message-ID: <AM7PR10MB332070E1C0F1D6D7F0E4BECB86AC2@AM7PR10MB3320.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <34c4028d-2d4d-4c3c-b528-972bfaa9f74b@siemens.com>
> > 2. **Problem**: When embedding the target image into the installer rootfs a rebuild of the installer image is required everytime we change the target image.
> >
> > **Possible Solution**: Installer image could download target
> > image from http/ftp/s3 server at runtime and install it from memory.
> > (Therefore, we have to ensure enough memory is provided, or probably
> > support some kind of streaming functionality)
>
> This sounds like what SWUpdate or rauc already provide. Which could be used to describe the system and also provide a installation state.
>
> Quirin
(I will focus on SWUpdate, since we already ship it in our target images.)
That means instead of deploying a wic image like now, we could ship
e.g. SWUpdate and use an swu file to execute the tasks described?
Therefore, a reuse of partitioning and image deployment from such utility
was possible, putting the steps described for encryption,
secure-boot deployment, aso. as post scripts.
Although, I see the value when it comes to image download/streaming
and verification of such, I'm not sure if the gained value of having SWUpdate
outweights the effort of shipping SWUpdate for an installer,
compared to a relatively simple script.
bmaptool, which is used right now to deploy the image, already supports
downloads from http(s)://, ftp://, ssh:// and file:// sources, checksums
and signature verification.
+ Reuse of existing logic (SWUpdate)
- Harder (although not that hard at all) to understand compared to
(imo relatively) simple script logic
- Build and ship additional component/dependency SWUpdate
~ Build additional image for swu
(probably that's done anyways if SWUpdate is in use for OS/Firmware updates,
but downstream projects could use other stacks like rauc, mender, ... already)
+ Same workflows for encryption / sb-enrollment could also be used on upgrades
What was the reason not to use SWUpdate for the current installer?
BR Alexander
--
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/AM7PR10MB332070E1C0F1D6D7F0E4BECB86AC2%40AM7PR10MB3320.EURPRD10.PROD.OUTLOOK.COM.
next prev parent reply other threads:[~2024-07-18 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 13:30 'Heinisch, Alexander' via isar-users
2024-07-17 14:47 ` 'Gylstorff Quirin' via isar-users
2024-07-18 11:34 ` 'Heinisch, Alexander' via isar-users [this message]
2024-07-23 12:35 ` 'Gylstorff Quirin' via isar-users
2024-07-25 12:37 ` 'Niedermayr, BENEDIKT' via isar-users
2024-08-19 8:32 ` 'Heinisch, Alexander' via isar-users
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=AM7PR10MB332070E1C0F1D6D7F0E4BECB86AC2@AM7PR10MB3320.EURPRD10.PROD.OUTLOOK.COM \
--to=isar-users@googlegroups.com \
--cc=alexander.heinisch@siemens.com \
--cc=jan.kiszka@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