From: Anton Mikanovich <amikan@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>,
isar-users <isar-users@googlegroups.com>
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: Re: [PATCH v6 0/7] vm-img improvements and fixes
Date: Mon, 27 Dec 2021 16:00:31 +0300 [thread overview]
Message-ID: <89135a73-1f01-0508-86ec-5982b58cd392@ilbers.de> (raw)
In-Reply-To: <20211217144835.14878-1-amikan@ilbers.de>
17.12.2021 17:48, Anton Mikanovich wrote:
> changes since v5:
> - base on v4, not v3 as previous version
>
> changes since v4:
> - format commit messages
>
> changes since v3:
> - change the way we play with the SRC_URI path in p1
> - adding cover letter again
>
> changes since v2:
> - change avocado code and move renamed bullseye test into another test
>
> changes since v1:
> - rebase on next/avocado
>
>
> The vm-img support we currently have is a bit broken in various aspects.
> Most prominently the resulting ova files are accepted by vmware only
> with warnings. And UEFI booting did not really work in virtualbox or
> vmware.
>
> This series makes the template for the appliance a file one can override
> with a custom template. Which should allow close to any special
> configuration that the VMMs can express in their respective ovf
> dialects. It further makes changes to the templates we ship with isar to
> hopefully give people a decent baseline so they will not even need
> custom templates. And there is some code cleanup to the vm-img class.
>
> Henning Schild (7):
> vm-img: move template out of package into SRC_URI file
> vm-img: use two different ovf templates for vmware/virtualbox
> vm-img: shorten code by using variables we have
> vm-img: drop not used variables
> vm-img: set vmware machine type to 64bit in our template
> vm-img: make use of isars template class for most of the tmpl
> variables
> meta-isar: switch virtualbox test from buster to bullseye
>
> meta-isar/conf/local.conf.sample | 2 +-
> meta-isar/conf/machine/vmware.conf | 2 +
> ...a-buster.conf => virtualbox-bullseye.conf} | 2 +-
> meta/classes/vm-img.bbclass | 35 ++---
> .../vm-img/vm-img-virtualbox.ovf.tmpl} | 132 +++++++-----------
> meta/classes/vm-img/vm-img-vmware.ovf.tmpl | 127 +++++++++++++++++
> .../vm-template/vm-template_0.1.bb | 16 ---
> testsuite/build_test/build_test.py | 6 +-
> 8 files changed, 199 insertions(+), 123 deletions(-)
> rename meta-isar/conf/multiconfig/{virtualbox-ova-buster.conf => virtualbox-bullseye.conf} (77%)
> rename meta/{recipes-devtools/vm-template/files/vm-template.ovf.tmpl => classes/vm-img/vm-img-virtualbox.ovf.tmpl} (54%)
> create mode 100644 meta/classes/vm-img/vm-img-vmware.ovf.tmpl
> delete mode 100644 meta/recipes-devtools/vm-template/vm-template_0.1.bb
>
Applied to next, thanks.
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2021-12-27 13:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 14:48 Anton Mikanovich
2021-12-17 14:48 ` [PATCH v6 1/7] vm-img: move template out of package into SRC_URI file Anton Mikanovich
2021-12-17 16:35 ` Henning Schild
2021-12-28 6:37 ` Anton Mikanovich
2021-12-17 14:48 ` [PATCH v6 2/7] vm-img: use two different ovf templates for vmware/virtualbox Anton Mikanovich
2021-12-17 14:48 ` [PATCH v6 3/7] vm-img: shorten code by using variables we have Anton Mikanovich
2021-12-17 14:48 ` [PATCH v6 4/7] vm-img: drop not used variables Anton Mikanovich
2021-12-17 14:48 ` [PATCH v6 5/7] vm-img: set vmware machine type to 64bit in our template Anton Mikanovich
2022-05-19 21:20 ` Henning Schild
2022-05-24 19:05 ` Jan Kiszka
2022-05-24 22:28 ` Henning Schild
2021-12-17 14:48 ` [PATCH v6 6/7] vm-img: make use of isars template class for most of the tmpl variables Anton Mikanovich
2021-12-17 14:48 ` [PATCH v6 7/7] meta-isar: switch virtualbox test from buster to bullseye Anton Mikanovich
2021-12-27 13:00 ` Anton Mikanovich [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=89135a73-1f01-0508-86ec-5982b58cd392@ilbers.de \
--to=amikan@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