From: <Adithya.Balakumar@toshiba-tsip.com>
To: <cip-dev@lists.cip-project.org>, <jan.kiszka@siemens.com>,
<quirin.gylstorff@siemens.com>
Cc: <felix.moessbauer@siemens.com>,
<Shivanand.Kunijadar@toshiba-tsip.com>,
<Sai.Sathujoda@toshiba-tsip.com>, <dinesh.kumar@toshiba-tsip.com>,
<kazuhiro3.hayashi@toshiba.co.jp>
Subject: RE: [cip-dev] [isar-cip-core][PATCH v4 0/3] Integrate Delta Update with rdiff_image and delta handler
Date: Mon, 6 May 2024 08:47:05 +0000 [thread overview]
Message-ID: <TYCPR01MB9669132581B052EDE6105F7DC41C2@TYCPR01MB9669.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <e197cfad-fad4-4309-9132-f443ff0c0987@siemens.com>
Hi Quirin,
Yes, will send out v5 today. Apologies for the delay.
Regards,
Adithya Balakumar
-----Original Message-----
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Quirin Gylstorff via lists.cip-project.org
Sent: Monday, May 6, 2024 1:55 PM
To: cip-dev@lists.cip-project.org; jan.kiszka@siemens.com
Cc: felix.moessbauer@siemens.com; kunijadar shivanand(ＴＳＩＰ TMIEC ODG Porting) <Shivanand.Kunijadar@toshiba-tsip.com>; ashrith sai(ＴＳＩＰ) <Sai.Sathujoda@toshiba-tsip.com>; dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４) <kazuhiro3.hayashi@toshiba.co.jp>
Subject: Re: [cip-dev] [isar-cip-core][PATCH v4 0/3] Integrate Delta Update with rdiff_image and delta handler
Hi,
is the patch v5 in work?
Quirin
On 4/25/24 11:44 AM, Adithya Balakumar via lists.cip-project.org wrote:
> These series of patches enable the support for delta update for the
> root file system with swupdate's rdiff_image and delta handler(zchunk).
>
> A couple notes about the implementation:
> - In this patchset, Delta update is only supported for the root file system.
> - The newly added delta-update.bbclass handles the creation of the delta update artifacts.
> - The update handler type i.e rdiff_image or delta handler is set in the variable "DELTA_UPDATE_TYPE"
> in the swupdate.yml file along with some variables required for each handler.
> - The creation of delta artifact for the rdiff_image handler requires
> a reference image (against which the delta is computed). Currently the
> reference artifact file (.squashfs/.verity) is passed to the build
> system by placing the artifact in the path "${TOPDIR}/previous-image" and setting the name of the artifact in the variable DELTA_RDIFF_REF_IMAGE in the swupdate.yml file.
> - zchunk based delta update is only supported for sid onwards.
>
> Changes in v4:
> - Create only 1 .swu file, either delta or complete swu.
> - By default complete update swu is created.
>
> Changes in v3:
> - Rebase to current next branch
> (61e998e1e0541e2713c05fcbf21df39fbc882a0a)
> - Set "${TOPDIR}/previous-image" as the path for the previous image artifact for rdiff update.
> - README updates to verify delta update.
>
> Changes in v2:
> - Removed zchunk support for bookworm (due to use of backports). Currently zchunk based update only supported in Sid.
> - Removed delta-update.yml file. Related variables have default values and can be set in manually swupdate.yml file.
> - Using .squashfs file (.verity file in the case of Secure boot) for rdiff delta creation instead of .wic file.
> - rdiff is set as default for delta update type, the build system looks for the v1 artifact in a default path (image-v1/<artifact_name>).
> - Created a separate template file for sw-description of delta update.
> - Renamed delta_update.bbclass to delta-update.bbclass.
>
> Adithya Balakumar (3):
> Add Delta update support with rdiff_image and delta handler
> swupdate.bbclass: Generate swu for delta updates
> doc/README.swupdate.md: Update steps to test Delta software Update
>
> classes/delta-update.bbclass | 97 +++++++++++++++++++++
> classes/swupdate.bbclass | 27 +++++-
> conf/layer.conf | 2 +-
> doc/README.swupdate.md | 59 +++++++++++++
> kas/opt/swupdate.yml | 5 ++
> recipes-core/images/swu/sw-description.tmpl | 5 +-
> 6 files changed, 189 insertions(+), 6 deletions(-)
> create mode 100644 classes/delta-update.bbclass
>
>
>
>
>
prev parent reply other threads:[~2024-05-06 8:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 9:44 [isar-cip-core][PATCH v4 0/3] Integrate Delta Update with rdiff_image and delta handler Adithya Balakumar
2024-04-25 9:44 ` [isar-cip-core][PATCH v4 1/3] Add Delta update support " Adithya Balakumar
2024-04-29 12:15 ` Jan Kiszka
2024-04-25 9:44 ` [isar-cip-core][PATCH v4 2/3] swupdate.bbclass: Generate swu for delta updates Adithya Balakumar
2024-04-29 12:21 ` Jan Kiszka
2024-04-25 9:44 ` [isar-cip-core][PATCH v4 3/3] doc/README.swupdate.md: Update steps to test Delta software Update Adithya Balakumar
2024-04-29 12:45 ` Jan Kiszka
2024-04-29 13:05 ` Adithya.Balakumar
2024-04-29 14:18 ` Jan Kiszka
2024-04-29 14:59 ` [cip-dev] " Adithya.Balakumar
2024-05-01 7:39 ` Jan Kiszka
2024-04-25 12:01 ` [isar-cip-core][PATCH v4 0/3] Integrate Delta Update with rdiff_image and delta handler MOESSBAUER, Felix
2024-05-06 8:25 ` [cip-dev] " Gylstorff Quirin
2024-05-06 8:47 ` Adithya.Balakumar [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=TYCPR01MB9669132581B052EDE6105F7DC41C2@TYCPR01MB9669.jpnprd01.prod.outlook.com \
--to=adithya.balakumar@toshiba-tsip.com \
--cc=Sai.Sathujoda@toshiba-tsip.com \
--cc=Shivanand.Kunijadar@toshiba-tsip.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).