DPDK CI discussions
 help / color / mirror / Atom feed
From: Adam Hassick <ahassick@iol.unh.edu>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, "aconole@redhat.com" <aconole@redhat.com>
Subject: Re: [PATCH v6 0/6] Community Lab Containers and Builder Engine
Date: Thu, 22 Jun 2023 15:28:41 -0400	[thread overview]
Message-ID: <CAC-YWqiz5_0ifHtjqFY5U33MCo0ae-B_s5WHdAZzAgkUUN3iKQ@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB516732821EB666810694C58CDA22A@DM4PR12MB5167.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3008 bytes --]

These changes are based off of an internal copy that should've been kept
up-to-date with the latest patch series. This internal copy is what we're
running in production to build our images. This is where I made my changes
when adding documentation for new features. I'll make sure that the changes
Owen was asked to add between the initial patchset and the v4 patchset are
present in what we have running in production and in the next patch.

On an unrelated note, the version of the arch dockerfile template in this
patch no longer builds without error. This is due to a change in the arch
base image that prevents the installation of pip packages in the root
environment. I will include those changes in the next patchset as well.

On Thu, Jun 22, 2023 at 11:29 AM Ali Alnubani <alialnu@nvidia.com> wrote:

> > -----Original Message-----
> > From: Adam Hassick <ahassick@iol.unh.edu>
> > Sent: Thursday, May 25, 2023 8:15 PM
> > To: ci@dpdk.org
> > Cc: aconole@redhat.com; Ali Alnubani <alialnu@nvidia.com>; Adam Hassick
> > <ahassick@iol.unh.edu>
> > Subject: [PATCH v6 0/6] Community Lab Containers and Builder Engine
> >
> > 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. Support for
> > building the Coverity Scan container image has also been added.
> >
> > 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 thrice for every target in the
> > inventory file. 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.
> >
>
> Hi Adam,
>
> Are you sure your changes were based on Owen's most recent patchset (v4)?
> I noticed that the README no longer mentions the dependency on podman
> v4.0.0. See:
> https://inbox.dpdk.org/ci/DM4PR12MB51677D9D8DBCD1A3D7D3997DDA2B9@DM4PR12MB5167.namprd12.prod.outlook.com/
>


-- 
*Adam Hassick*
Senior Developer
UNH InterOperability Lab
ahassick@iol.unh.edu
iol.unh.edu <https://www.iol.unh.edu/>
+1 (603) 475-8248

[-- Attachment #2: Type: text/html, Size: 4667 bytes --]

  reply	other threads:[~2023-06-22 19:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 17:14 Adam Hassick
2023-05-25 17:15 ` [PATCH v6 1/6] containers/docs: Add container builder start Adam Hassick
2023-05-25 17:15 ` [PATCH v6 2/6] containers/inventory: Add inventory for container builder Adam Hassick
2023-05-25 17:15 ` [PATCH v6 3/6] containers/builder: Dockerfile creation script Adam Hassick
2023-06-22 15:55   ` Ali Alnubani
2023-06-22 16:18     ` Adam Hassick
2023-06-22 16:52       ` Ali Alnubani
2023-05-25 17:15 ` [PATCH v6 4/6] containers/templates: Templates for Dockerfiles Adam Hassick
2023-06-22 15:40   ` Ali Alnubani
2023-06-22 16:08     ` Adam Hassick
2023-06-22 16:51       ` Ali Alnubani
2023-05-25 17:15 ` [PATCH v6 5/6] containers/container_builder: Container for python scripts Adam Hassick
2023-05-25 17:15 ` [PATCH v6 6/6] containers/Makefile: Makefile to automate builds Adam Hassick
2023-06-22 15:29 ` [PATCH v6 0/6] Community Lab Containers and Builder Engine Ali Alnubani
2023-06-22 19:28   ` Adam Hassick [this message]
2023-06-23 14:11     ` Aaron Conole

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=CAC-YWqiz5_0ifHtjqFY5U33MCo0ae-B_s5WHdAZzAgkUUN3iKQ@mail.gmail.com \
    --to=ahassick@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    /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).