DPDK CI discussions
 help / color / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "ci@dpdk.org" <ci@dpdk.org>
Subject: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday July 2nd
Date: Tue, 2 Jul 2019 13:35:03 +0000
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB78EB0CD@IRSMSX108.ger.corp.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]

New hardware:
- Jeremy is working with NXP on setting up their hardware.
- Broadcom have also provided hardware.

SPDK Tests:
- The SPDK team want to make sure that new DPDK changes don't break SPDK.
- Want compile testing with different operating systems. This will be added to the UNH backlog.
- They would also like unit tests to be run for functions like memory allocation. Need to figure out if tests already exist, and if not then who could help develop these tests. We'll need to meet with the SPDK team to discuss this further.

OVS Tests:
- Tests are running on the Intel hardware.
- Jeremy has figured out the problem with the Mellanox hardware.

CI:
- Zhaoyan has done some work on CI improvement. Have enabled virtio and crypto test cases internally. Can replicate some of these in the community lab. Shipping a couple more servers to UNH is not an issue. We'll work on a plan for this.
- Have also integrated SPDK build testing. If Jeremy has issues with SPDK, Zhaoyan can help.
- Have also enabled Windows build testing internally.

DPDK Userspace Event:
- Aaron has a talk accepted for the Userspace event and will cover CI. He'll work with others offline to include their input.
- Ali has a talk on services offered by DPDK.org.

Unit Test:
- Improvements have been made to the Unit Test suite. We should look at enabling these in UNH.

UNH IOL Website:
- UNH would like to include detail on the lab in their website - testbeds, companies that are participating, types of testing performed etc. We agreed that this is a good idea and nobody had any objections.

UNH Priority Order:
1. Get OVS tests running on Mellanox hardware
2. New hardware setup (NXP & Broadcom)
3. Compilation testing
4. Unit testing

[-- Attachment #2: Type: text/html, Size: 4633 bytes --]

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">New hardware:<o:p></o:p></p>
<p class="MsoNormal">- Jeremy is working with NXP on setting up their hardware.<o:p></o:p></p>
<p class="MsoNormal">- Broadcom have also provided hardware.<o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal">SPDK Tests:<o:p></o:p></p>
<p class="MsoNormal">- The SPDK team want to make sure that new DPDK changes don&#8217;t break SPDK.<o:p></o:p></p>
<p class="MsoNormal">- Want compile testing with different operating systems. This will be added to the UNH backlog.<o:p></o:p></p>
<p class="MsoNormal">- They would also like unit tests to be run for functions like memory allocation. Need to figure out if tests already exist, and if not then who could help develop these tests. We&#8217;ll need to meet with the SPDK team to discuss this further.<o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal">OVS Tests:<o:p></o:p></p>
<p class="MsoNormal">- Tests are running on the Intel hardware.<o:p></o:p></p>
<p class="MsoNormal">- Jeremy has figured out the problem with the Mellanox hardware.<o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal">CI:<o:p></o:p></p>
<p class="MsoNormal">- Zhaoyan has done some work on CI improvement. Have enabled virtio and crypto test cases internally. Can replicate some of these in the community lab. Shipping a couple more servers to UNH is not an issue. We&#8217;ll work on a plan for this.<o:p></o:p></p>
<p class="MsoNormal">- Have also integrated SPDK build testing. If Jeremy has issues with SPDK, Zhaoyan can help.<o:p></o:p></p>
<p class="MsoNormal">- Have also enabled Windows build testing internally.<o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal">DPDK Userspace Event:<o:p></o:p></p>
<p class="MsoNormal">- Aaron has a talk accepted for the Userspace event and will cover CI. He&#8217;ll work with others offline to include their input.<o:p></o:p></p>
<p class="MsoNormal">- Ali has a talk on services offered by DPDK.org.<o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal">Unit Test:<o:p></o:p></p>
<p class="MsoNormal">- Improvements have been made to the Unit Test suite. We should look at enabling these in UNH.<o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal">UNH IOL Website:<o:p></o:p></p>
<p class="MsoNormal">- UNH would like to include detail on the lab in their website &#8211; testbeds, companies that are participating, types of testing performed etc. We agreed that this is a good idea and nobody had any objections.<o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal">UNH Priority Order:<o:p></o:p></p>
<p class="MsoNormal">1. Get OVS tests running on Mellanox hardware<o:p></o:p></p>
<p class="MsoNormal">2. New hardware setup (NXP &amp; Broadcom)<o:p></o:p></p>
<p class="MsoNormal">3. Compilation testing<o:p></o:p></p>
<p class="MsoNormal">4. Unit testing<o:p></o:p></p>
</div>
</body>
</html>

                 reply index

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

Reply instructions:

You may reply publically 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=26FA93C7ED1EAA44AB77D62FBE1D27BAB78EB0CD@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@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

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox