From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 650B54D27 for ; Thu, 24 Jan 2019 17:38:07 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Jan 2019 08:38:06 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,517,1539673200"; d="scan'208";a="141003776" Received: from irsmsx109.ger.corp.intel.com ([163.33.3.23]) by fmsmga001.fm.intel.com with ESMTP; 24 Jan 2019 08:38:05 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.205]) by IRSMSX109.ger.corp.intel.com ([169.254.13.133]) with mapi id 14.03.0415.000; Thu, 24 Jan 2019 16:38:04 +0000 From: "O'Driscoll, Tim" To: "ci@dpdk.org" CC: "Stokes, Ian" Thread-Topic: OVS Testing in DPDK Community Lab Thread-Index: AdS0Ak+GrK1/ceGXTLqBJvrzGYS+sg== Date: Thu, 24 Jan 2019 16:38:04 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB782F7CC@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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiN2ZlZGVhY2QtNDc4Yy00M2FkLWExY2MtYzY0Y2VlMTU3YWZmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTXI5ZDZ2T3ZVRjFPekFIeFwvTHN2QkxCSXNOTXNobFhzSlNnbVwvenFtZzdJVFdQcVdmeEpNQ0RVV00wQitBUXB1In0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [dpdk-ci] OVS Testing in DPDK Community Lab 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 Jan 2019 16:38:08 -0000 At our last DPDK lab meeting we discussed the proposal to add OVS testing t= o our community lab. Ian Stokes from our OVS team has been involved in disc= ussions on this and provided some additional detail on the testing that the= OVS project would like to use the lab for. Proposal for co-location of OVS DPDK test infrastructure with existing DPDK= labs. OVS DPDK supports various hardware network devices e.g. Intel XL710, Intel = 82599ES, Mellanox connectx-4, Mellanox connectx-5 etc. A problem inherent t= o supporting such a wide range of devices in that proposed software solutio= ns submitted by one vendor to enable a particular feature in OVS for their = particular device may impact negatively for other vendor devices, introduci= ng performance regressions or even loss of functionality. The purpose of th= is lab deployment would be to provide a consolidated test bed where OVS DPD= K patches could be verified using OVS DPDK unit tests and OVS DPDK function= al tests to ensure no breakage/regression for all supported devices. The re= quired infrastructure for automated patch application and testing for OVS D= PDK is already available and is handled by the OVS 0-day robot. Companies involved (Initial List): Intel, Red Hat, Mellanox. (However other= HW=A0 vendors may contribute HW devices in the future and also become invo= lved) People involved: Aaron Conole from Red Hat is responsible for implementing = the OVS 0-day robot and has offered to help deploy any hardware received an= d setup the 0 day robot on the given hardware (he is located 1 hours' drive= from the existing University DPDK lab). Input from engineers in the commun= ity may also be used (Ian Stokes Intel, Ophir Munk Mellanox.) We can discuss again at our next meeting on Tuesday. Trishan has also set u= p a separate call with Rashid Khan to get a perspective from Red Hat, as we= agreed at our last call.