From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "ci@dpdk.org" <ci@dpdk.org>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, October 17th
Date: Tue, 17 Oct 2017 17:12:46 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23EDD69C3@IRSMSX103.ger.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
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
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: 4573 bytes --]
next reply other threads:[~2017-10-17 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 17:12 Mcnamara, John [this message]
2017-10-18 1:19 ` Xu, Qian Q
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=B27915DBBA3421428155699D51E4CFE23EDD69C3@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.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).