From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id A6FD61DA4 for ; Thu, 24 May 2018 14:50:01 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 May 2018 05:50:00 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,436,1520924400"; d="scan'208,217";a="226905355" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by orsmga005.jf.intel.com with ESMTP; 24 May 2018 05:49:56 -0700 Received: from irsmsx155.ger.corp.intel.com (163.33.192.3) by IRSMSX102.ger.corp.intel.com (163.33.3.155) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 24 May 2018 13:49:55 +0100 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.150]) by irsmsx155.ger.corp.intel.com ([169.254.14.95]) with mapi id 14.03.0319.002; Thu, 24 May 2018 13:49:55 +0100 From: "O'Driscoll, Tim" To: "'ci@dpdk.org'" CC: 'Bob Noseworthy' , "Mcnamara, John" , 'Shepard Siegel' , 'Thomas Monjalon' , 'Erez Scop' , 'Shreyansh Jain' , "Xu, Qian Q" , "'pmacarth@iol.unh.edu'" , 'Matt Spencer' , 'George Zhao' , "Mishra, Shishir" , 'Lixuming' , "Tkachuk, Georgii" , 'Trishan de Lanerolle' , Sean Campbell , Ali Alnubani , 'May Chen' , "Lodha, Nishant" , "Zhang, Chun" , "'Malla, Malathi'" , 'khemendra kumar' , "'graeme.gregory@linaro.org'" , "Tran, Paul" Thread-Topic: Minutes of DPDK Lab Meeting, May 22nd Thread-Index: AdPzTzG6mLmY4moWQbm3S4vbUAdL9A== Date: Thu, 24 May 2018 12:49:54 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4B3C735@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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNjk4YWM2NDYtMjVjNC00ZTMwLThhZGMtZDlmMTMwNDQwMGU3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTUx0WHY1N3V5ZkhWZ0pQOFBaOEt0R1p1Y1dNZ1RZRW1jaGZiS1dPazBzNFdMVjM3VnlvVXhOMEVGM2pFSkxcL28ifQ== x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: multipart/alternative; boundary="_000_26FA93C7ED1EAA44AB77D62FBE1D27BAA4B3C735IRSMSX108gercor_" MIME-Version: 1.0 Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, May 22nd 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: , X-List-Received-Date: Thu, 24 May 2018 12:50:02 -0000 --_000_26FA93C7ED1EAA44AB77D62FBE1D27BAA4B3C735IRSMSX108gercor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hardware Setup: * Intel 25G hardware has been set up, but there's an issue using TR= ex with the firmware version that supports our 25G NICs. We'll swap the 25G= NICs for 40G, which allows us to avoid the issue. New hardware has been or= dered and should be delivered soon. George will work with Patrick on the se= tup. Setup of 10G NICs is also in progress. * This wasn't covered during the meeting, but in a separate email d= iscussion Cavium confirmed that they're working on getting hardware ready a= nd hope to be ready to ship to UNH by the end of this week. * Mellanox hardware has been running for a few weeks now. Ali is wo= rking on some scripts. * NXP hardware is still in progress. Test Setup: * Discussed a few corner cases for testing: o What happens when the system detects patch sets that have already been = applied? This would not normally happen, but can do if the system falls beh= ind due to load or other issues, or if patch sets are applied very quickly = which sometimes happens towards the end of a release. o If a patch set doesn't apply to master, should we try applying to next-= net and test that? This situation may occur if next-net is ahead of master.= It would mean keeping separate performance history for next-net, as this m= ay differ from master. John will discuss with Ferruh (next-net maintainer) = to see how common this situation is and if it's worth the effort of doing t= his. o For patch set dependencies, we could add a specific tag which could the= n be detected by Patchwork. Patchwork 2 may help with this as it has better= handling for patch sets. Ali and Thomas are planning to install Patchwork = 2 after 18.05 has been released. * Patrick sent email with a mock-up of the dashboard (http://dpdk.o= rg/ml/archives/ci/2018-May/000178.html). Please review and send comments to= Patrick. We also need to consider possible extension of the lab scope to c= over CI (see item below) and make sure the dashboard can be easily extended= if we add that in future. * Target is still to have tests running with public results by the = end of Q2, in time for the China DPDK Summit on June 28th. Contract Extension * The current contract runs until the end of June. * Agreed that we will extend this to the end of this year initially= . Lincoln will provide the necessary documentation to Trishan. After this, = we'll extend on an annual basis which aligns with the DPDK budgeting cycle. * Discussed extending the lab scope to include additional CI capabi= lities, similar to the FD.io CSIT lab. The Intel team are investigating som= e CI improvements. We'll discuss further internally and when we have a prop= osal on this we'll review with this group. --_000_26FA93C7ED1EAA44AB77D62FBE1D27BAA4B3C735IRSMSX108gercor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hardware Setup:

·         Intel 25G hardware has been set up, but ther= e’s an issue using TRex with the firmware version that supports our 2= 5G NICs. We’ll swap the 25G NICs for 40G, which allows us to avoid th= e issue. New hardware has been ordered and should be delivered soon. George will work with Patrick on the setup. Setup of 10= G NICs is also in progress.

·         This wasn’t covered during the meeting= , but in a separate email discussion Cavium confirmed that they’re wo= rking on getting hardware ready and hope to be ready to ship to UNH by the = end of this week.

·         Mellanox hardware has been running for a few= weeks now. Ali is working on some scripts.

·         NXP hardware is still in progress.

 

Test Setup:

·         Discussed a few corner cases for testing:

o   What happens when the system detects patch s= ets that have already been applied? This would not normally happen, but can= do if the system falls behind due to load or other issues, or if patch set= s are applied very quickly which sometimes happens towards the end of a release.

o   If a patch set doesn’t apply to master= , should we try applying to next-net and test that? This situation may occu= r if next-net is ahead of master. It would mean keeping separate performanc= e history for next-net, as this may differ from master. John will discuss with Ferruh (next-net maintainer) to see ho= w common this situation is and if it’s worth the effort of doing this= .

o   For patch set dependencies, we could add a s= pecific tag which could then be detected by Patchwork. Patchwork 2 may help= with this as it has better handling for patch sets. Ali and Thomas are pla= nning to install Patchwork 2 after 18.05 has been released.

·         Patrick sent email with a mock-up of the das= hboard (htt= p://dpdk.org/ml/archives/ci/2018-May/000178.html). Please review and se= nd comments to Patrick. We also need to consider possible extension of the lab scope to cover CI (see item belo= w) and make sure the dashboard can be easily extended if we add that in fut= ure.

·         Target is still to have tests running with p= ublic results by the end of Q2, in time for the China DPDK Summit on June 2= 8th.

 

Contract Extension

·         The current contract runs until the end of J= une.

·         Agreed that we will extend this to the end o= f this year initially. Lincoln will provide the necessary documentation to = Trishan. After this, we’ll extend on an annual basis which aligns wit= h the DPDK budgeting cycle.

·         Discussed extending the lab scope to include= additional CI capabilities, similar to the FD.io CSIT lab. The Intel team = are investigating some CI improvements. We’ll discuss further interna= lly and when we have a proposal on this we’ll review with this group.

 

 

--_000_26FA93C7ED1EAA44AB77D62FBE1D27BAA4B3C735IRSMSX108gercor_--