From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>, "ci@dpdk.org" <ci@dpdk.org>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"Liu, Yong" <yong.liu@intel.com>,
"Pei, Yulong" <yulong.pei@intel.com>,
"Wang, FeiX Y" <feix.y.wang@intel.com>
Subject: Re: [dpdk-ci] Minutes of DPDK Lab Meeting, October 17th
Date: Wed, 18 Oct 2017 01:19:31 +0000 [thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E3B7DB38F@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23EDD69C3@IRSMSX103.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
Add some updates for DTS and Trex inline.
From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of Mcnamara, John
Sent: Wednesday, October 18, 2017 1:13 AM
To: ci@dpdk.org
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, October 17th
Contract:
* UNH/Bob has added Warranty to the Statement of work. UNH legal are
reviewing the changes. This should allow all parties to close the
contract phase.
Hardware availability:
* Intel: Hardware being configured in their lab.
* NXP: Slight delay with hardware, stuck in procurement.
* Mellanox: Hardware installed in lab. Waiting for resources to start
testing.
* Atomic rules: Will follow with hardware at a later stage.
Software testing with DTS and TRex:
* No updates
Currently we have the draft code to make TREX as traffic generator, and it's working in the internal lab, but the patch need to be refined before merging to DTS.
Result database and web front-end:
* Targeted for Q1 - Q2 of next year.
* Design should be a Marketing decision - will need input
Other:
* Atomic Rules/Shep: What OS should we use as the default test platform.
Input requested from the partners.
[-- Attachment #2: Type: text/html, Size: 5818 bytes --]
prev parent reply other threads:[~2017-10-18 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 17:12 Mcnamara, John
2017-10-18 1:19 ` Xu, Qian Q [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=82F45D86ADE5454A95A89742C8D1410E3B7DB38F@shsmsx102.ccr.corp.intel.com \
--to=qian.q.xu@intel.com \
--cc=ci@dpdk.org \
--cc=feix.y.wang@intel.com \
--cc=john.mcnamara@intel.com \
--cc=yong.liu@intel.com \
--cc=yulong.pei@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).