DPDK CI discussions
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "'ci@dpdk.org'" <ci@dpdk.org>
Cc: 'Trishan de Lanerolle' <tdelanerolle@linuxfoundation.org>,
	"'Bob Noseworthy'" <ren@iol.unh.edu>,
	'Shreyansh Jain' <shreyansh.jain@nxp.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	'Shepard Siegel' <shepard.siegel@atomicrules.com>,
	'Thomas Monjalon' <thomas@monjalon.net>,
	'Erez Scop' <erezsc@mellanox.com>,
	"Xu, Qian Q" <qian.q.xu@intel.com>,
	"'Matt Spencer'" <Matt.Spencer@arm.com>,
	"pmacarth@iol.unh.edu" <pmacarth@iol.unh.edu>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, October 31st
Date: Thu, 2 Nov 2017 11:47:04 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4A5DD8A@IRSMSX108.ger.corp.intel.com> (raw)

Here are some brief minutes of our call on Tuesday.

Contract:
- The warranty clause was updated in the contract as per input from Erez.
- The contract is complete and has been signed by both the LF and UNH. This is a big step forward for the project!
- For the Usage Agreement, every participating company other than Atomic Rules is already working with UNH on other projects so has already agreed the terms of the Usage Agreement. If any companies do have concerns over the Usage Agreement they should follow up with Bob directly.

Hardware:
- Intel, Mellanox and NXP are all working on getting hardware ready. We should aim to provide hardware as soon as possible to UNH.
- Systems used for testing (DUT and packet generator) will be maintained by the vendors. This means the vendors will manage any OS/kernel updates (to be limited as much as possible in order to keep things stable), BIOS changes etc. If a system recovery is required, vendors will either need to provide an image or else provide directions for UNH to follow.
- Systems used for CI will be maintained by UNH. 

Infrastructure:
- Qian's team have made progress on getting TRex integrated into DTS. Patches are available (see the dts@dpdk.org archives for September at http://dpdk.org/ml/archives/dts/), but further work is required on these so they have not yet been merged into DTS. This work will continue after the 17.11 release testing has completed.
- Mellanox and NXP are both working on setting up DTS and TRex. The aim is to standardize on DTS as the common test framework, and TRex as the packet generator, unless we run into problems.
- Patrick has started investigating patchwork integration and is able to pull down patches and run simple tests against them. He'll follow up with Thomas offline to discuss this in more detail, as Thomas is the DPDK patchwork expert.
- Patrick has created an initial database schema which will be shared for review on the ci@dpdk.org mailing list.
- Infrastructure for VPN access, zoning, firewalls etc. has been set up.

Next Meeting:
- Those of us attending the DPDK Summit will discuss in person then. I'll cancel the call for that week. If there are any issues that need UNH involvement, we'll discuss via email.
    

                 reply	other threads:[~2017-11-02 11:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=26FA93C7ED1EAA44AB77D62FBE1D27BAA4A5DD8A@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=Matt.Spencer@arm.com \
    --cc=ci@dpdk.org \
    --cc=erezsc@mellanox.com \
    --cc=john.mcnamara@intel.com \
    --cc=pmacarth@iol.unh.edu \
    --cc=qian.q.xu@intel.com \
    --cc=ren@iol.unh.edu \
    --cc=shepard.siegel@atomicrules.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=tdelanerolle@linuxfoundation.org \
    --cc=thomas@monjalon.net \
    /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).