From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7CD1BA034C; Wed, 9 Nov 2022 18:06:35 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 62399400EF; Wed, 9 Nov 2022 18:06:35 +0100 (CET) Received: from mail-pj1-f52.google.com (mail-pj1-f52.google.com [209.85.216.52]) by mails.dpdk.org (Postfix) with ESMTP id 04C08400D4 for ; Wed, 9 Nov 2022 18:06:34 +0100 (CET) Received: by mail-pj1-f52.google.com with SMTP id c15-20020a17090a1d0f00b0021365864446so2497387pjd.4 for ; Wed, 09 Nov 2022 09:06:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=siyfWt+f1lQGn0NsLLevxdYMgr/iWpfAl+tuvOIVo9E=; b=hImcXCDxb/3l8yASMeLPZiPgkp6//KvEEnCWMKX4wtRRC0lmeLLj/+lZqVcC6gPfDe QqLzxPLwhhHNj6BgzuCLwGbCmiP06cdy7puQFIScjEJpt+8B+yK6ADTLWpVoUaB03Nm5 wUpnnMEG2vPto94VE1F1t93qsY0/pa5OBYLSg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=siyfWt+f1lQGn0NsLLevxdYMgr/iWpfAl+tuvOIVo9E=; b=t8StLBefGNeRXbWtG7nTeTtNrR51MLsAs5tGeFeEkNTfdR1kV/BR3pJXu60yr2i9bn lQ4eLNUhPfcbGIew5t7ksd2aJp1/xcQPtppNV5n6UG2WnRQD60HptppE6U1+rZSsxkIo 2CFq27zoDN+iMcRrvTscmiGiDvYdr7EsTUaC4/xTNS/c0Vsri+O+kp9KfKAiA/ph4rrV WvoMX7LUxd9adMRkr2UB31bux24fXv7gqM09feV6cVRuHew2Fd4BUgQw9fTERUXca67Z EOuRRQpdKaj+M1lhFAB/O5TyklHQkLbU/X0o77UNMK6cHJItrN0rlX4R43/6vzrWIHkK T6ow== X-Gm-Message-State: ANoB5plpq9nfL78KvnINWdPVgYyzaJLfFRinpptxriBO9Mz5DWihAuu3 zM9jqi+teKqxCg/UxALhVxYs3ZtOu1FFbCocqrZaWA== X-Google-Smtp-Source: AA0mqf7A8Er42zlW+9vmWb8hyvB3CHRnDNeu8N6TgJC9s3egQ0IRLktuEwUx1N6lexEISd1WODX/fXR75QlnZpS3xe8= X-Received: by 2002:a17:902:7fc1:b0:188:64b0:99ad with SMTP id t1-20020a1709027fc100b0018864b099admr29581652plb.162.1668013593231; Wed, 09 Nov 2022 09:06:33 -0800 (PST) MIME-Version: 1.0 References: <20221103151934.450887-1-juraj.linkes@pantheon.tech> <20221104110523.511367-1-juraj.linkes@pantheon.tech> <3234001.rnzMqkiUVr@thomas> In-Reply-To: From: Owen Hilyard Date: Wed, 9 Nov 2022 12:05:56 -0500 Message-ID: Subject: Re: [PATCH v8 0/9] dts: ssh connection to a node To: Honnappa Nagarahalli Cc: "thomas@monjalon.net" , "lijuan.tu@intel.com" , =?UTF-8?Q?Juraj_Linke=C5=A1?= , "kda@semihalf.com" , "bruce.richardson@intel.com" , "dev@dpdk.org" , "david.marchand@redhat.com" , nd Content-Type: multipart/alternative; boundary="000000000000b49cb205ed0caddb" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --000000000000b49cb205ed0caddb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Nov 9, 2022 at 11:23 AM Honnappa Nagarahalli < Honnappa.Nagarahalli@arm.com> wrote: > > > > > > 04/11/2022 12:05, Juraj Linke=C5=A1: > > > All the necessary code needed to connect to a node in a topology with > > > a bit more, such as basic logging and some extra useful methods. > > > > Applied, thanks. > > > > That's the first step towards integration of DTS in DPDK repository. > > Nice to see this becoming a reality. > Thanks Thomas and the community for the reviews and suggestions. This is > the first important step, hopefully we can continue the collaboration in > the future releases. > > > > > [...] > > > This is our current roadmap: > > > 1. Review this patchset and do the rest of the items in parallel, if > > > possible. > > > 2. We have extracted the code needed to run the most basic testcase, > > > HelloWorld, which runs the DPDK Hello World application. We'll split > > > this along logical/functional boundaries and send after 1 is done. > > > 3. Once we have 2 applied, we're planning on adding a basic functiona= l > > > testcase - pf_smoke. This send a bit of traffic, so the big addition > > > is the software traffic generator, Scapy. There's some work already > > > done on Traffic generators we'll be sending as a dependence on this > > > patch series. > > > 4. After 3, we'll add a basic performance testcase which doesn't use > > > Scapy, but Trex or Ixia instead. > > > 5. This is far in the future, but at this point we should have all of > > > the core functionality in place. What then remains is adding the rest > > > of the testcases. > > > > Let's join the force and help making this project a pleasant tool. > > > > I would also like to thank everyone for their reviews and suggestions toward DTS. The primary goal of this rewrite is make it as easy as possible to write robust tests so that DPDK can be heavily and reliably tested. This rewrite allows us at the DTS Working Group to leverage more than 8 years of experience with the prior DTS to help make it much easier for anyone to write tests or set up their own testing, but we also want feedback from the community, so please take a look and give us more feedback. I would also like to remind everyone that if you have any features that you want to see in DTS you should bring them to us as soon as possible. We are starting with support for NICs, but want to be able to branch out to test all DPDK-supported devices. If you have concerns or required features that you don't want to discuss on the mailing list for some reason, you can send your concerns directly to me and I will make sure your needs are represented in discussions around DTS. Planned but Unimplemented Features: * telnet connections for the DUT * scapy traffic generator (low performance but easy to use) * trex traffic generator (DPDK-based software traffic generator) * IXIA traffic generator (hardware traffic generator) * Traffic generator abstraction layer * Automatic skipping of tests based on the hardware under test, os and other factors * Abstractions to test development to allow simple tests (send this list of packets then expect this list, etc) to be written as easily as possible. * Automatic setup and teardown of virtual machines for virtio testing * The ability to cross compile for a given target on the system running DTS (assuming relevant libraries/compilers are installed), then install onto the system under test (intended for embedded systems or SOCs). * Structured logging for automated analysis * and many more --000000000000b49cb205ed0caddb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Nov 9, 2022 at 11:23 AM Honnappa = Nagarahalli <Honnappa.Na= garahalli@arm.com> wrote:
<snip>

>
> 04/11/2022 12:05, Juraj Linke=C5=A1:
> > All the necessary code needed to connect to a node in a topology = with
> > a bit more, such as basic logging and some extra useful methods.<= br> >
> Applied, thanks.
>
> That's the first step towards integration of DTS in DPDK repositor= y.
> Nice to see this becoming a reality.
Thanks Thomas and the community for the reviews and suggestions. This is th= e first important step, hopefully we can continue the collaboration in the = future releases.

>
> [...]
> > This is our current roadmap:
> > 1. Review this patchset and do the rest of the items in parallel,= if
> > possible.
> > 2. We have extracted the code needed to run the most basic testca= se,
> > HelloWorld, which runs the DPDK Hello World application. We'l= l split
> > this along logical/functional boundaries and send after 1 is done= .
> > 3. Once we have 2 applied, we're planning on adding a basic f= unctional
> > testcase - pf_smoke. This send a bit of traffic, so the big addit= ion
> > is the software traffic generator, Scapy. There's some work a= lready
> > done on Traffic generators we'll be sending as a dependence o= n this
> > patch series.
> > 4. After 3, we'll add a basic performance testcase which does= n't use
> > Scapy, but Trex or Ixia instead.
> > 5. This is far in the future, but at this point we should have al= l of
> > the core functionality in place. What then remains is adding the = rest
> > of the testcases.
>
> Let's join the force and help making this project a pleasant tool.=
>


I would also like to thank everyone for their rev= iews and suggestions toward DTS. The primary goal of this rewrite is make i= t as easy as possible to write robust tests so that DPDK can be heavily and= reliably tested. This rewrite allows us at the DTS Working Group to levera= ge more than 8 years of experience with the prior DTS to help make it much = easier for anyone to write tests or set up their own testing, but we also w= ant feedback from the community, so=C2=A0please take a look and give us mor= e feedback.=C2=A0

I would also like to remind=C2=A0everyo= ne that if you have any features that you want to see in DTS you should bri= ng them to us as soon as possible. We are starting with support for NICs, b= ut want to be able to branch out to test all DPDK-supported devices. If you= have concerns or required features that you don't want to discuss on t= he mailing list for some reason, you can send your concerns directly to me = and I will make sure your needs are represented in discussions around=C2=A0= DTS.=C2=A0

Planned but Unimplemented Features:
* telnet connectio= ns for the DUT
* scapy traffic generator (low performance but easy to us= e)
* trex traffic generator (DPDK-based software traffic generator)
*= IXIA traffic generator (hardware traffic generator)
* Traffic ge= nerator abstraction layer
* Automatic skipping of tests based on the har= dware under test, os and other factors
* Abstractions to test developmen= t to allow simple tests (send this list of packets then expect this list, e= tc) to be written as easily as possible.
* Automatic setup and teardown = of virtual machines for virtio testing
* The ability to cross compile fo= r a given target on the system running DTS (assuming relevant libraries/com= pilers are installed), then install onto the system under test (intended fo= r embedded systems or SOCs).
* Structured logging for automated analysis=
* and many more

--000000000000b49cb205ed0caddb--