public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2 0/4] Imager schroot migration
Date: Fri, 30 Dec 2022 22:08:20 +0300	[thread overview]
Message-ID: <20221230190824.12256-1-amikan@ilbers.de> (raw)

This patchset moves Isar imager from buildchroot to schroot usage as the next
step after moving to sbuild.

Imagers of every target are now running in separate schroot sessions with
independent overlays on top of basic unchanged schroot. It means we need to
open schroot session before any imager task execution and close this session
after the usage. Any changes made inside overlay will be dropped after the
usage to keep basic schroot clean.

We also need to introduce additional cleanup inside isar-events finish handler
to prevent leaving sessions in case we execute only session start task.

There are still couple of issues need to be solved before the usage:
- there are no documentaion updates
- only basic build scenarios works, CI still fails

Changes since v1:

- Rebased on next and bitbake update
- Fix some build cases

Anton Mikanovich (4):
  sbuild: Allow setting custom config paths
  imager: Migrate from buildchroot to schroot
  imager: Move image types to schroot
  events: Cleanup lost schroot sessions if any

 meta/classes/image-tools-extension.bbclass | 80 ++++++++++++++++---
 meta/classes/image.bbclass                 |  4 +-
 meta/classes/imagetypes_vm.bbclass         |  7 +-
 meta/classes/imagetypes_wic.bbclass        | 89 ++++++++--------------
 meta/classes/isar-events.bbclass           | 16 ++++
 meta/classes/sbuild.bbclass                | 51 +++++++++----
 6 files changed, 159 insertions(+), 88 deletions(-)

-- 
2.17.1


             reply	other threads:[~2022-12-30 19:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 19:08 Anton Mikanovich [this message]
2022-12-30 19:08 ` [PATCH v2 1/4] sbuild: Allow setting custom config paths Anton Mikanovich
2022-12-30 19:08 ` [PATCH v2 2/4] imager: Migrate from buildchroot to schroot Anton Mikanovich
2022-12-30 19:08 ` [PATCH v2 3/4] imager: Move image types " Anton Mikanovich
2022-12-30 19:08 ` [PATCH v2 4/4] events: Cleanup lost schroot sessions if any Anton Mikanovich
2023-01-03  9:55   ` Roberto A. Foglietta
2023-01-04 11:19     ` Roberto A. Foglietta
2022-12-30 19:13 ` [PATCH v2 0/4] Imager schroot migration Anton Mikanovich

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=20221230190824.12256-1-amikan@ilbers.de \
    --to=amikan@ilbers.de \
    --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