DPDK CI discussions
 help / color / mirror / Atom feed
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 2/6] containers/inventory: Add inventory for container builder
Date: Tue, 11 Oct 2022 20:24:18 +0000	[thread overview]
Message-ID: <DM4PR12MB5167636D47F87F8403021755DA239@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221011165255.506428-3-ohilyard@iol.unh.edu>

> -----Original Message-----
> From: ohilyard@iol.unh.edu <ohilyard@iol.unh.edu>
> Sent: Tuesday, October 11, 2022 7:53 PM
> To: ci@dpdk.org
> Cc: aconole@redhat.com; Owen Hilyard <ohilyard@iol.unh.edu>
> Subject: [PATCH 2/6] containers/inventory: Add inventory for container
> builder
> 
> From: Owen Hilyard <ohilyard@iol.unh.edu>
> 
> Adds a yaml file used to define what containers should be built, what
> packages the containers should have, what platforms to build for and how
> they
> should be tagged.
> 
> Also adds a JSON schema, which can be used to validate that the
> inventory file is well-formed.
> 
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
> ---
>  containers/template_engine/inventory.yaml     | 360 ++++++++++++++++++
>  .../template_engine/inventory_schema.json     | 153 ++++++++
>  2 files changed, 513 insertions(+)
>  create mode 100644 containers/template_engine/inventory.yaml
>  create mode 100644 containers/template_engine/inventory_schema.json
> 
> diff --git a/containers/template_engine/inventory.yaml
> b/containers/template_engine/inventory.yaml
> new file mode 100644
> index 0000000..e1781b1
> --- /dev/null
> +++ b/containers/template_engine/inventory.yaml
> @@ -0,0 +1,360 @@
> +# SPDX-License-Identifier: BSD-3-Clause
> +# Copyright (c) 2022 University of New Hampshire
> +---
> +abi:
> +  # versions should also include the abi versions for all stable ABIs.
> +  versions:
> +    - major: 20 # oldest supported lts
> +      minor: 11
> +      git_tag: v20.11
> +    - major: 21 # most recent lts
> +      minor: 11
> +      git_tag: v21.11
> +    # - major: 22 # current abi
> +    #   minor: 07
> +    #   git_tag: v22.07
> +
> +dockerfiles:
> +  groups:
> +    all:
> +      package_manager_command: "NO_INSTALL_COMMAND_SET"
> +      parent: "NONE"
> +      packages:
> +        - gcc
> +        - make
> +        - git
> +        - sudo
> +        - curl
> +        - automake
> +        - autoconf
> +        - flex
> +        - bison
> +        - bc
> +    rpm:
> +      parent: "all"
> +      package_manager_command: yum install -y
> +      packages:
> +        - diffutils
> +        - pkg-config
> +        - python3
> +        - python3-pip
> +        - librdmacm
> +        - rdma-core-devel
> +        - libmnl-devel
> +        - ccache
> +        - zip
> +        - flex

Parent already has 'flex' package. Same for the other child groups.
May I also suggest sorting the package lists alphanumerically? It makes spotting duplicates easier.

[..]

  reply	other threads:[~2022-10-11 20:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 16:52 [PATCH 0/6] Community Lab Container Definitions ohilyard
2022-10-11 16:52 ` [PATCH 1/6] containers/docs: Add container builder start ohilyard
2022-10-11 16:52 ` [PATCH 2/6] containers/inventory: Add inventory for container builder ohilyard
2022-10-11 20:24   ` Ali Alnubani [this message]
2022-10-11 16:52 ` [PATCH 3/6] containers/builder: Dockerfile creation script ohilyard
2022-10-11 16:52 ` [PATCH 4/6] containers/templates: Templates for Dockerfiles ohilyard
2022-10-11 20:24   ` Ali Alnubani
2022-10-11 16:52 ` [PATCH 5/6] containers/container_builder: Container for python scripts ohilyard
2022-10-11 20:24   ` Ali Alnubani
2022-10-11 16:52 ` [PATCH 6/6] containers/Makefile: Makefile to automate builds ohilyard

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=DM4PR12MB5167636D47F87F8403021755DA239@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).