public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/9] Support running custom commands in VM
Date: Tue, 21 Feb 2023 13:56:00 +0300	[thread overview]
Message-ID: <4601653.vXUDI8C0e8@home> (raw)
In-Reply-To: <20230208154511.1884-1-ubely@ilbers.de>

In the email from Wednesday, 8 February 2023 18:45:02 +03 user Uladzimir Bely 
wrote:
> VM run tests implementation in Isar testsuite allows only parsing
> virtual machine boot logs, so the functionality is limited.
> 
> This patchset additionally allows to run custom commands on VM
> that runs in qemu that allows to implement any custom tests.
> 
> The concept is the following.
> 
> For running custom tests SSH is used. So:
> 
>  - SSH server on machine should be configured, so `sshd-regen-keys`
> package needs to be installed in the image.
> 
>  - Ethernet interface on machine should be automatically brought up
> to make host-to-vm port forwarding working.
> 
>  - User in VM we use to connect via SSH should have public SSH key
> in their `~/.ssh/` directory preinstalled.
> 
>  - Since base isar image don't have this included, custom image name
> for vm run tests should be supported. This also allows to make reusing
> Isar testsuite in downstream simpler.
> 
> Changes since v1:
>  - Patches "meta-isar: Fix PCI bus initialization in qemuarm machine"
> and "testsuite: Use random free port for qemu SSH forwarding" are
> excluded from patchset since they are already merged.
>  - User `ci` creation/configuration is moved to a separate package so
> now it can be simply removed from target using apt. No new user flags
> are required anymore.
>  - In addition to simple commands (cmd="<command>"), running custom
> local scripts (script="<script>.sh") on remote machine is implemented.
>  - Appropriate documentation was added.
>  - patchset rebased on top of "Add developers test" patchset which
> is supposed to be merged earlier.
> 
> Notes:
>  - Mixing positional and named arguments, e.g.
> 
> |    self.vm_start('arm','bookworm',
> |    
> |        image='isar-image-ci', script='test_getty_target.sh')
> 
> is still here, since it's easy to read.
> 
> Uladzimir Bely (9):
>   testsuite: Fix failing hostname service in qemu guest
>   testsuite: Add SSH key pair for using in CI
>   meta-isar: Add a recipe that configures ci user
>   meta-isar: Use a separate image recipe in CI
>   testsuite: Allow custom image names in start_vm.py
>   testsuite: Support running custom commands in VM
>   testsuite: Support running custom scripts in VM
>   testsuite: Run custom commands and scripts on some qemu targets
>   testsuite: Update testsuite qemu-related documentation
> 
>  meta-isar/recipes-ci/images/isar-image-ci.bb  |   9 ++
>  .../isar-ci-ssh-setup/files/postinst          |  18 +++
>  .../isar-ci-ssh-setup_0.1.bb                  |  22 ++++
>  testsuite/README.md                           |  41 ++++++-
>  testsuite/cibuilder.py                        | 105 +++++++++++++++++-
>  testsuite/citest.py                           | 105 +++++++++++++++---
>  testsuite/keys/ssh/id_rsa                     |  38 +++++++
>  testsuite/keys/ssh/id_rsa.pub                 |   1 +
>  testsuite/start_vm.py                         |  23 ++--
>  testsuite/test_example_module.sh              |   5 +
>  testsuite/test_getty_target.sh                |   7 ++
>  11 files changed, 341 insertions(+), 33 deletions(-)
>  create mode 100644 meta-isar/recipes-ci/images/isar-image-ci.bb
>  create mode 100644 meta-isar/recipes-ci/isar-ci-ssh-setup/files/postinst
>  create mode 100644
> meta-isar/recipes-ci/isar-ci-ssh-setup/isar-ci-ssh-setup_0.1.bb create mode
> 100644 testsuite/keys/ssh/id_rsa
>  create mode 100644 testsuite/keys/ssh/id_rsa.pub
>  create mode 100644 testsuite/test_example_module.sh
>  create mode 100644 testsuite/test_getty_target.sh


Applied to next.



      parent reply	other threads:[~2023-02-21 10:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 15:45 Uladzimir Bely
2023-02-08 15:45 ` [PATCH v2 1/9] testsuite: Fix failing hostname service in qemu guest Uladzimir Bely
2023-02-08 15:45 ` [PATCH v2 2/9] testsuite: Add SSH key pair for using in CI Uladzimir Bely
2023-02-08 15:45 ` [PATCH v2 3/9] meta-isar: Add a recipe that configures ci user Uladzimir Bely
2023-02-08 15:45 ` [PATCH v2 4/9] meta-isar: Use a separate image recipe in CI Uladzimir Bely
2023-02-08 15:45 ` [PATCH v2 5/9] testsuite: Allow custom image names in start_vm.py Uladzimir Bely
2023-02-08 15:45 ` [PATCH v2 6/9] testsuite: Support running custom commands in VM Uladzimir Bely
2023-02-08 15:45 ` [PATCH v2 7/9] testsuite: Support running custom scripts " Uladzimir Bely
2023-02-08 15:45 ` [PATCH v2 8/9] testsuite: Run custom commands and scripts on some qemu targets Uladzimir Bely
2023-02-08 15:45 ` [PATCH v2 9/9] testsuite: Update testsuite qemu-related documentation Uladzimir Bely
2023-02-21 10:56 ` Uladzimir Bely [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=4601653.vXUDI8C0e8@home \
    --to=ubely@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