DPDK CI discussions
 help / color / Atom feed
From: "Stokes, Ian" <ian.stokes@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	"ci@dpdk.org" <ci@dpdk.org>,  Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-ci] Minutes of DPDK Lab Meeting, February 26th
Date: Mon, 4 Mar 2019 08:49:13 +0000
Message-ID: <CD7C01071941AC429549C17338DB8A528953FAE1@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <3087301.JtsJcBCixJ@xps>



> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Monday, March 4, 2019 8:40 AM
> To: Stokes, Ian <ian.stokes@intel.com>
> Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; ci@dpdk.org; Aaron Conole
> <aconole@redhat.com>
> Subject: Re: [dpdk-ci] Minutes of DPDK Lab Meeting, February 26th
> 
> 04/03/2019 09:06, Stokes, Ian:
> > > -----Original Message-----
> > > From: O'Driscoll, Tim
> > > Sent: Thursday, February 28, 2019 3:25 PM
> > > To: Thomas Monjalon <thomas@monjalon.net>; ci@dpdk.org
> > > Cc: Aaron Conole <aconole@redhat.com>; Stokes, Ian
> > > <ian.stokes@intel.com>
> > > Subject: RE: [dpdk-ci] Minutes of DPDK Lab Meeting, February 26th
> > >
> > > > -----Original Message-----
> > > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > > Sent: Thursday, February 28, 2019 3:20 PM
> > > > To: ci@dpdk.org
> > > > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>
> > > > Subject: Re: [dpdk-ci] Minutes of DPDK Lab Meeting, February 26th
> > > >
> > > > Hi,
> > > >
> > > > 28/02/2019 15:49, O'Driscoll, Tim:
> > > > > OVS Tests:
> > > > > - Jeremy and Aaron are working on setup of the temporary hardware.
> > > > > - There are two options for hardware to run this on when the
> > > > > setup is
> > > > complete: 1) use existing vendor hardware; 2) obtain standalone
> > > > servers for OVS testing. The OVS team's preference is option 2.
> > > > It's not realistic to expect a vendor to provide hardware to run a
> > > > competitor's products so we'd need to find a different way to
> > > > procure this. Aaron will check with Rashid to see if budget is
> > > > available from Red Hat. I'll check with Trishan to see if the DPDK
> > > > project budget could
> > > cover this.
> > > > > - The OVS focus is on functional tests, not performance tests.
> > > > > The
> > > > DPDK lab is currently set up so that each vendor has complete
> > > > control over performance tests & results on their hardware. If we
> > > > use separate hardware for the OVS tests, we need to ensure that we
> > > > restrict scope to functional tests so that it does not conflict
> > > > with this principle in future.
> > > >
> > > > I am not sure to understand.
> > > > In my opinion, the purpose of this lab is to have properly tuned
> > > > hardware for running a large set of tests. We should be able to
> > > > run various tests on the same machine. So the OVS tests, like any
> > > > new test scenario, should be run on the same machine as the
> performance tests.
> > > > I think we just need to have a job queue to run tests one by one,
> > > > avoiding a test to disturb results of another one.
> > > >
> > > > Why are we looking for additional machines?
> > >
> > > That was my assumption too. I believe the reason is that the OVS
> > > team want to validate with multiple vendor NICs to be sure that
> nothing is broken.
> > > We only have Intel and Mellanox hardware in our lab at present, so
> > > we don't cover all vendors.
> > >
> > > Aaron and Ian can provide more details.
> >
> > Hi Thomas,
> >
> > So from the OVS point of view, one of challenges when consuming DPDK is
> ensuring device compatibility across the community, in particular with the
> ongoing/upcoming HWOL development work. There is a risk that the
> implementation for HWOL for vendor x may not be compatible or suitable for
> vendor y etc.
> >
> > To help address this risk, it was proposed back in DPDK userspace 2018
> that if the OVS community could provide a server, it could be used to co-
> locate a variety of vendor NICs. We could then leverage the OVS Zero Day
> robot to apply and conduct functional testing for OVS development patches
> and ensure patches do not break existing functionality.
> 
> Yes it seems to be the scope of the DPDK Community Lab.
> 
> > To date Aaron has received a number of NICs from various vendors,
> however a server (possibly 2) would still be needed to deploy the NICS.
> >
> > It was proposed that possibly the DPDK Lab in UNL aid with this.
> >
> > The aim here is purely functional and the system would not be used to
> benchmark the NICs in question. It would be purely to stop regressions
> being introduced into OVS DPDK and also act as a feedback to the DPDK
> community if changes were needed in DPDK itself.
> 
> So far I don't see the need for new servers.

Maybe there isn't, I guess when this was proposed originally, knowledge WRT what HW was available was limited.
> 
> > It might be possible to run the tests on the existing hardware in UNL
> but I guess this might not cover the NIC vendors Aaron has received to
> date. I wonder would it interrupt the existing DPDK workloads on those
> servers also so there was an open question on whether OVS DPDK should be
> deployed on a separate board.
> 
> Which vendor is not available in the DPDK Community Lab?
> 

I'm not sure which vendor Aaron has NICs for already, if this can be shared I guess this needs to be compared to which vendors are in the lab already.

Thanks
Ian

> > @Aaron, have I missed anything from your side?
> >
> > Thanks
> > Ian
> 

  reply index

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 14:49 O'Driscoll, Tim
2019-02-28 15:20 ` Thomas Monjalon
2019-02-28 15:24   ` O'Driscoll, Tim
2019-03-04  8:06     ` Stokes, Ian
2019-03-04  8:40       ` Thomas Monjalon
2019-03-04  8:49         ` Stokes, Ian [this message]
2019-03-04 13:06     ` Aaron Conole
2019-03-04 16:59       ` Lincoln Lavoie
2019-03-04 17:40         ` Thomas Monjalon
2019-03-08 21:24           ` Aaron Conole
2019-03-08 23:22             ` Thomas Monjalon

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=CD7C01071941AC429549C17338DB8A528953FAE1@IRSMSX101.ger.corp.intel.com \
    --to=ian.stokes@intel.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=tim.odriscoll@intel.com \
    /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