public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
To: isar-users@googlegroups.com
Subject: [PATCH 0/2] Add support for containerized SDKs
Date: Fri,  5 Feb 2021 10:08:25 +0100	[thread overview]
Message-ID: <20210205090827.17788-1-silvano.cirujano-cuesta@siemens.com> (raw)

This patch series extends the SDK creation task `populate_sdk` to enable
the creation of container images (different formats that can be
simultaneously generated supported) providing the SDK. Containerized
SDKs are easy to distribute and run and are therefore quickly spreading.

The SDK format available until this patch (.tar.xz of SDK rootfs that
can be chrooted to) remains available and is the default. Even for those
wanting to use the here called `tar-xz` format it's possible to use
container images as "packaging" medium (simple to get tools -script,
skopeo,...- can help on this, if needed).

More information about its usage is documented in the file
docs/user_manual.md.

A PoC/demo of this functionality has been created based on the project
https://github.com/siemens/meta-iot2050.
Jan Kiszka already tested and liked it! =>
https://github.com/siemens/meta-iot2050/issues/86#issuecomment-768907845

In order to get a feeling about its usage (you need Docker or Podman),
follow these simple copy&paste instructions:
https://github.com/Silvanoc/meta-iot2050/blob/master/kas/BUILDING-SDK-CONTAINER.md#running-the-sdk
Build instructions are available in the upper part of that document.

Two new dependencies are required to create containerized SDKs (as
specified in the documentation).

Typical container image management actions (e.g. push an image to a
container image regitry) are out of scope. Available tools (Docker,
Skopeo, Buildah, Podman,...) should be used for these actions.

This patch series addresses the comments and concerns raised in the RFC
called "support generation of sdk container images".

A patch will follow this one to get the dependencies into the container
images being provided by the project
https://github.com/siemens/kas (for `kas-container`, for example).

Silvano Cirujano Cuesta (2):
  sdk: support creation of container image
  docs: document usage of sdk container images

 doc/user_manual.md                       |  79 +++++++++++++++++
 meta/classes/image-sdk-extension.bbclass | 104 +++++++++++++++++++++--
 2 files changed, 176 insertions(+), 7 deletions(-)

-- 
2.30.0


             reply	other threads:[~2021-02-05  9:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05  9:08 Silvano Cirujano Cuesta [this message]
2021-02-05  9:08 ` [PATCH 1/2] sdk: support creation of container image Silvano Cirujano Cuesta
2021-02-05 11:07   ` Jan Kiszka
2021-02-05 11:24     ` Silvano Cirujano Cuesta
2021-02-05 11:29       ` Jan Kiszka
2021-02-05 17:52         ` Silvano Cirujano Cuesta
2021-02-05 18:20           ` Jan Kiszka
2021-02-05  9:08 ` [PATCH 2/2] docs: document usage of sdk container images Silvano Cirujano Cuesta
2021-02-05 11:07   ` Jan Kiszka
2021-02-05 14:58     ` Silvano Cirujano Cuesta
2021-02-05 18:21       ` Jan Kiszka

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=20210205090827.17788-1-silvano.cirujano-cuesta@siemens.com \
    --to=silvano.cirujano-cuesta@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