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>,
	'Patrick MacArthur' <patrick@patrickmacarthur.net>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, October 3rd
Date: Thu, 5 Oct 2017 15:56:44 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4078C92@IRSMSX101.ger.corp.intel.com> (raw)

Here are some brief minutes of our call on Tuesday.

Contract:
- The only remaining issue is the wording on warranty. This is waiting on guidance from the LF legal team.
- Trishan: Any update from the LF legal team on this?

Lab visit by Cisco and Atomic Rules:
- Shep and some of his team, along with John Daley from Cisco, visited UNH on Friday 22nd to meet Bob, Patrick and the team there, and discuss setup of the lab.
- I spoke to John Daley last week in Dublin, and he was very impressed.

Hardware availability:
- No significant update on this. Vendors are still working through the procurement/setup process. Hopefully we can ship some hardware to UNH by the end of October.
- Bob asked if each vendor will contribute their own hardware for packet generators, so vendor tests can be run concurrently. Confirmed that vendors will provide hardware for packet generators as well as DUT.

DTS:
- Agreed that it's better to standardize on DTS as the test framework if we can. The alternative is to allow the framework to be vendor-specific.
- Qian should be the first point of contact if Mellanox/NXP run into problems and need help getting DTS running. The PRC team are out of the office at the moment for their Ntional Day holidays, but return to work next week.

                 reply	other threads:[~2017-10-05 15:56 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=26FA93C7ED1EAA44AB77D62FBE1D27BAA4078C92@IRSMSX101.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=ci@dpdk.org \
    --cc=erezsc@mellanox.com \
    --cc=john.mcnamara@intel.com \
    --cc=patrick@patrickmacarthur.net \
    --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).