From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id E338EA0487 for ; Tue, 2 Jul 2019 15:35:08 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DA04E1E20; Tue, 2 Jul 2019 15:35:08 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id A4A76160 for ; Tue, 2 Jul 2019 15:35:06 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jul 2019 06:35:06 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.63,443,1557212400"; d="scan'208,217";a="362224908" Received: from irsmsx152.ger.corp.intel.com ([163.33.192.66]) by fmsmga005.fm.intel.com with ESMTP; 02 Jul 2019 06:35:04 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.46]) by IRSMSX152.ger.corp.intel.com ([169.254.6.79]) with mapi id 14.03.0439.000; Tue, 2 Jul 2019 14:35:04 +0100 From: "O'Driscoll, Tim" To: "ci@dpdk.org" Thread-Topic: DPDK Community Lab Meeting Minutes, Tuesday July 2nd Thread-Index: AdUw2JEKK0hhLXvLRdKjZBSLZ1RDCw== Date: Tue, 2 Jul 2019 13:35:03 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB78EB0CD@IRSMSX108.ger.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNjZlYmRhMzEtZjI0My00M2Q0LWFlMjItODJiZGEyOTg0OTcxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiVjJtQXVuaVwvVlNIcEJWQ0RUXC9paURCd05seVJRbCszblF6Zm45SEJTZUdwOTdtZkNNaXd0Z0IwMWIyWDlnMEM3In0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.600.7 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: multipart/alternative; boundary="_000_26FA93C7ED1EAA44AB77D62FBE1D27BAB78EB0CDIRSMSX108gercor_" MIME-Version: 1.0 Subject: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday July 2nd X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" --_000_26FA93C7ED1EAA44AB77D62FBE1D27BAB78EB0CDIRSMSX108gercor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 alloc= ation. 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 cry= pto 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 pl= an 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'l= l 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 ena= bling 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 --_000_26FA93C7ED1EAA44AB77D62FBE1D27BAB78EB0CDIRSMSX108gercor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

New hardware:

- Jeremy is working with NXP on setting up their har= dware.

- Broadcom have also provided hardware.

 

SPDK Tests:

- The SPDK team want to make sure that new DPDK chan= ges don’t break SPDK.

- Want compile testing with different operating syst= ems. This will be added to the UNH backlog.

- They would also like unit tests to be run for func= tions like memory allocation. Need to figure out if tests already exist, an= d 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 Mellan= ox hardware.

 

CI:

- Zhaoyan has done some work on CI improvement. Have= enabled virtio and crypto test cases internally. Can replicate some of the= se in the community lab. Shipping a couple more servers to UNH is not an is= sue. 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 in= put.

- 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 the= ir website – testbeds, companies that are participating, types of tes= ting performed etc. We agreed that this is a good idea and nobody had any o= bjections.

 

UNH Priority Order:

1. Get OVS tests running on Mellanox hardware

2. New hardware setup (NXP & Broadcom)

3. Compilation testing

4. Unit testing

--_000_26FA93C7ED1EAA44AB77D62FBE1D27BAB78EB0CDIRSMSX108gercor_--