DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Mykola Kostenok <mko-plv@napatech.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
	"aconole@redhat.com" <aconole@redhat.com>,
	 "lylavoie@iol.unh.edu" <lylavoie@iol.unh.edu>,
	Maksym Kovaliov <mak-plv@napatech.com>,
	 Christian Koue Muf <ckm@napatech.com>,
	Rasmus Carlson <rc@napatech.com>,
	 Vitalii Vrublevskyi <vvr-plv@napatech.com>
Subject: Re: Napatech participation in DPDK. Open questions.
Date: Tue, 8 Aug 2023 09:54:32 -0400	[thread overview]
Message-ID: <CAJvnSUCMUq5OvS8Br8czNUBixV892zwSvzmkgJNxoPt9C2cqBg@mail.gmail.com> (raw)
In-Reply-To: <AS1P190MB1797DA0E1228BF521A3D3EAC9F0DA@AS1P190MB1797.EURP190.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 2706 bytes --]

Hi Mykola,

I'm copy and pasting my reply and Aaron's reply from Slack here, as I see
you have some additional Napatech people CC'd.

1. 2 servers would be required for a testbed, in order to align with the
recommended topology for DTS.
2. only one testbed is needed. It is normal for us to test a few NICs on
one testbed, if that is a concern of yours.
3. [Aaron Conole] "Yes - there is specific member level for adding hardware
to the lab.  You need to be Gold member with the project, unless there is
an exception granted by the Gov Board. but for that, you would need to send
mail to gov board and ask them for consideration, and I don't think they
are going to do that currently"
4. Napatech will have ssh access to the lab testbed to do any desired
maintenance, updates, testing tuning, or anything else. Lab employees are
also available to help with all of this, of course.
5. The only final thing I would note is you asked about upstreaming DTS
testsuites 2.5 weeks ago at the ci meeting. As there has been no movement
on that thread for the dts mailing list, I encourage you to go ahead and
submit patchseries adding your testsuites to DTS as soon as your are able
to do so. I don't think you're going to get blocked due to scheduling rules.

On Tue, Aug 8, 2023 at 5:34 AM Mykola Kostenok <mko-plv@napatech.com> wrote:

> Hi.
>
>
>
>    - If we follow the option of sending Napatech NIC to DPDK lab, how
>    many servers are required for 1 testbed?
>    - How many testbeds are needed? Please confirm that no yearly fee is
>    required, Just contribution in the form of servers.
>    - What is the procedure of upgrade of Napatech NIC software? Will
>    Napatech engineers have access to the LAB? Or should Napatech share the
>    instructions on how to upgrade NICs to the LAB engineers?
>    - Is a specific membership tier required for hardware inclusion in the
>    lab?
>    - There was mentioned that governing board approval might be required
>    to get new vendor into community LAB. How to get this approval?
>    - Who is right contact person for this and next questions?
>
>
>
>
>
> Best regards,
>
> Mykola Kostenok.
>
>
> Disclaimer: This email and any files transmitted with it may contain
> confidential information intended for the addressee(s) only. The
> information is not to be surrendered or copied to unauthorized persons. If
> you have received this communication in error, please notify the sender
> immediately and delete this e-mail from your system.
>


-- 

Patrick Robb

Technical Service Manager

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

www.iol.unh.edu

[-- Attachment #2: Type: text/html, Size: 7225 bytes --]

      reply	other threads:[~2023-08-08 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  9:34 Mykola Kostenok
2023-08-08 13:54 ` Patrick Robb [this message]

Reply instructions:

You may reply publicly 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=CAJvnSUCMUq5OvS8Br8czNUBixV892zwSvzmkgJNxoPt9C2cqBg@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=ckm@napatech.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=mak-plv@napatech.com \
    --cc=mko-plv@napatech.com \
    --cc=rc@napatech.com \
    --cc=vvr-plv@napatech.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).