public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com, Henning Schild <henning.schild@siemens.com>
Subject: Re: [PATCH v4 0/5] expand-on-first-boot btrfs and CI testing
Date: Tue, 20 Dec 2022 12:37:24 +0300	[thread overview]
Message-ID: <2618987.lGaqSPkdTl@home> (raw)
In-Reply-To: <20221213112526.3e2bcae8@md1za8fc.ad001.siemens.net>

In the email from Tuesday, 13 December 2022 13:25:26 +03 user Henning Schild 
wrote:
> Hi all,
> 
> i decided to merge the re-introduction of btrfs with the CI series i
> had going on. Because that is all so important yet seemingly fragile
> that we really do not want any big change without CI.
> 
> this is based on
> "expand-on-first-boot: switch back away from systemd-growfs"
> which should be merged because it breaks several machines like rpis,
> with the udev race we found lately
> 
> It is tested manually in qemu, especially debian-bullseye (btrfs
> candidate) and on that formerly affected rpi.
> In addition i pushed it here to trigger CI runs at ilbers already:
> https://github.com/henning-schild-work/isar/tree/henning/ilbers-ci
> 
> I get the feeling we really need a way to log in to the images running
> in CI and run test code there. Only waiting for the login prompt and
> hoping for bits in the kernel log is not powerful enough do perform
> real tests. That is something to improve at some point.
> 

Hello Henning.

We are currently working on the downstream that requires such kind of access 
to the machine running under qemu. We want to implement the essential parts of 
functionality in Isar in the nearest future:
- remove scripts/start_vm in favor of testsuite/start_vm.py (or, at least, 
scripts/start_vm will be just a wrapper)
- allow custom image names (not only hardcoded 'isar-image-base') to be tested
- support checking the image for service status (at least)
- support any custom commands execution (at most)

Actually, the latest thing should also cover previous "service status 
checking". Also, when implemented, we will be able to completely remove boot 
log parsing that is used currently.

The main idea of the upcoming implementation is executing custom commands over 
SSH in "test" thread while the machine is kept running in "main" thread.

> regards,
> Henning
> 
> Am Tue, 13 Dec 2022 11:15:04 +0100
> 
> schrieb henning.schild@siemens.com:
> > From: Henning Schild <henning.schild@siemens.com>
> > 
> > changes since v3:
> >  - rebased on "expand-on-first-boot: switch back away from
> > 
> > systemd-growfs"
> > 
> >  - implement btrfs resizing and CI testing it
> >  - put the padding wks entry into an include
> > 
> > changes since v2:
> >  - add python namespace prefix for the bitbake get functions
> >  - install only in images that use WKS_FILEs that have the "gap"
> > 
> > changes since v1:
> >  - complete rewrite to not focus only on the tests but rather the
> >  
> >    feature for all examples
> > 
> > This first was only about testing but meanwhile has a focus on
> > enabling the expand feature in all example images anyhow, and later
> > look for traces of that happening in CI test where we can.
> > We install the application in any image and in the wic images add some
> > scratch space at the end. That will enable improved interactive use of
> > all those wic images, so makes sense apart from any testing.
> > Later use the log reading feature of the qemu tests to look for traces
> > of successful resizing for non ubuntu images. In ubuntu the
> > console_loglevel is not verbose enough to find traces.
> > 
> > Henning Schild (5):
> >   expand-on-first-boot: support resizing a btrfs
> >   meta-isar: introduce an example to use btrfs
> >   CI: improve cibuilder readability
> >   meta-isar: install expand-on-first-boot in most images and add space
> >   CI: expect a message about filesystem resize vom expand script
> >  
> >  meta-isar/conf/machine/qemuamd64.conf         |  6 ++++
> >  meta-isar/conf/machine/virtualbox.conf        |  1 +
> >  meta-isar/conf/machine/vmware.conf            |  1 +
> >  .../conf/multiconfig/qemuarm-bookworm.conf    |  1 +
> >  .../lib/wic/canned-wks/expand-padding.wks.inc |  5 +++
> >  .../lib/wic/canned-wks/sdimage-efi-btrfs.wks  | 11 ++++++
> >  .../lib/wic/canned-wks/sdimage-efi-sd.wks     |  2 ++
> >  .../lib/wic/canned-wks/sdimage-efi.wks        |  2 ++
> >  .../files/expand-last-partition.sh            | 35
> > 
> > ++++++++++++++++--- testsuite/cibuilder.py                        |
> > 28 ++++++++++++--- 10 files changed, 83 insertions(+), 9 deletions(-)
> > 
> >  create mode 100644
> > 
> > meta-isar/scripts/lib/wic/canned-wks/expand-padding.wks.inc create
> > mode 100644 meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-btrfs.wks


-- 
Uladzimir Bely




  reply	other threads:[~2022-12-20  9:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 10:15 henning.schild
2022-12-13 10:15 ` [PATCH v4 1/5] expand-on-first-boot: support resizing a btrfs henning.schild
2022-12-13 16:45   ` Roberto A. Foglietta
2022-12-13 17:18     ` Henning Schild
2022-12-13 20:44       ` Roberto A. Foglietta
2022-12-13 21:05         ` Henning Schild
2022-12-13 21:20           ` Roberto A. Foglietta
2022-12-14  3:33             ` Moessbauer, Felix
2022-12-14  6:50               ` Roberto A. Foglietta
2022-12-14  7:10                 ` Roberto A. Foglietta
2022-12-13 17:01   ` Roberto A. Foglietta
2022-12-13 21:22     ` Henning Schild
2022-12-13 22:15       ` Roberto A. Foglietta
2022-12-13 10:15 ` [PATCH v4 2/5] meta-isar: introduce an example to use btrfs henning.schild
2022-12-13 10:15 ` [PATCH v4 3/5] CI: improve cibuilder readability henning.schild
2022-12-13 10:15 ` [PATCH v4 4/5] meta-isar: install expand-on-first-boot in most images and add space henning.schild
2022-12-13 10:15 ` [PATCH v4 5/5] CI: expect a message about filesystem resize vom expand script henning.schild
2022-12-13 10:25 ` [PATCH v4 0/5] expand-on-first-boot btrfs and CI testing Henning Schild
2022-12-20  9:37   ` Uladzimir Bely [this message]
2022-12-20 15:08     ` Henning Schild
2022-12-21 10:25       ` Uladzimir Bely
2022-12-21 12:13         ` Henning Schild

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=2618987.lGaqSPkdTl@home \
    --to=ubely@ilbers.de \
    --cc=henning.schild@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