From: Ali Alnubani <alialnu@nvidia.com>
To: "ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>,
"ci@dpdk.org" <ci@dpdk.org>
Cc: "aconole@redhat.com" <aconole@redhat.com>
Subject: RE: [PATCH v2 0/6] Community Lab Container Definitions
Date: Thu, 20 Oct 2022 08:25:06 +0000 [thread overview]
Message-ID: <DM4PR12MB5167FAF8DF0AECC195C23FAEDA2A9@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221019125307.258582-1-ohilyard@iol.unh.edu>
> -----Original Message-----
> From: ohilyard@iol.unh.edu <ohilyard@iol.unh.edu>
> Sent: Wednesday, October 19, 2022 3:53 PM
> To: ci@dpdk.org
> Cc: aconole@redhat.com; Ali Alnubani <alialnu@nvidia.com>; Owen Hilyard
> <ohilyard@iol.unh.edu>
> Subject: [PATCH v2 0/6] Community Lab Container Definitions
>
> From: Owen Hilyard <ohilyard@iol.unh.edu>
>
> This patch series contains a new version of the DPDK CI containers. The old
> version was tied very tightly to the Community Lab Infrastructure, so it was
> not suitable for general use. This version is designed to make adding new
> OSes or OS versions as easy as possible. The minimum functionality can easily
> be built on any system that can compile DPDK. It includes support for
> building containers for other non-native architectures (ex: arm containers
> on x86) and for baking ABI references into the images.
>
> The inventory file as added in this patch series defines what the community
> lab
> currently supports.
>
> If you want to build these yourself, don't try to do parallel Makefile builds
> on non-server hardware. Libabigail is built into the containers, and since it
> is not avaliable in all distros it is compiled from source for many targets.
> If embedding the abi is enabled (DPDK_CI_CONTAINERS_BUILD_ABI=Y), with
> the
> current settings, DPDK will be compiled twice for every target in the
> inventory file. This will become three times when DPDK main has ABI stability
> again. Due to how the containers are constructed, building on non-native
> architectures is especially expensive because DPDK is compiled with an
> emulated
> compiler in a qemu vm that only has one thread.
>
> Owen Hilyard (6):
> containers/docs: Add container builder start
> containers/inventory: Add inventory for container builder
> containers/builder: Dockerfile creation script
> containers/templates: Templates for Dockerfiles
> containers/container_builder: Container for python scripts
> containers/Makefile: Makefile to automate builds
>
This is a great addition to the CI repo, thanks for the effort.
Tested with podman version 4.3.0.
Reviewed-by: Ali Alnubani <alialnu@nvidia.com>
Tested-by: Ali Alnubani <alialnu@nvidia.com>
prev parent reply other threads:[~2022-10-20 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 12:53 ohilyard
2022-10-19 12:53 ` [PATCH v2 1/6] containers/docs: Add container builder start ohilyard
2022-10-19 12:53 ` [PATCH v2 2/6] containers/inventory: Add inventory for container builder ohilyard
2022-10-19 12:53 ` [PATCH v2 3/6] containers/builder: Dockerfile creation script ohilyard
2022-10-19 12:53 ` [PATCH v2 4/6] containers/templates: Templates for Dockerfiles ohilyard
2022-10-19 19:24 ` Ali Alnubani
2022-10-24 12:52 ` Owen Hilyard
2022-10-19 12:53 ` [PATCH v2 5/6] containers/container_builder: Container for python scripts ohilyard
2022-10-19 12:53 ` [PATCH v2 6/6] containers/Makefile: Makefile to automate builds ohilyard
2022-10-19 14:31 ` [PATCH v2 0/6] Community Lab Container Definitions Ali Alnubani
2022-10-19 14:55 ` Owen Hilyard
2022-10-20 8:25 ` Ali Alnubani [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=DM4PR12MB5167FAF8DF0AECC195C23FAEDA2A9@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=ohilyard@iol.unh.edu \
/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;
as well as URLs for NNTP newsgroup(s).