From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dts@dpdk.org
Cc: ci@dpdk.org,
"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Tu, Lijuan" <lijuan.tu@intel.com>
Subject: DTS Improvement Working Group Meeting Minutes, August 10, 2022
Date: Wed, 10 Aug 2022 09:52:37 -0400 [thread overview]
Message-ID: <CAHx6DYBu86jamREoQxHSqaTdoBZTBFj1=WwFHriKn7Zv3rxp_A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3722 bytes --]
meeting link:
https://armltd.zoom.us/j/97503259680?pwd=VVlmWnlnTXJkVGkwR2JOU3R3b3Vndz09&from=addon
next meeting: August 17, 1:00 PM UTC Attendees
-
Owen Hilyard
-
Juraj Linkes
-
Maksym Vynnyk
-
Lijuan Tu
Agenda
-
Additions to the agenda
-
Merging DTS into DPDK
-
Community Engagement
-
Review/Carry forward pending action items
MinutesMerging DTS into DPDK - Current Status
-
Logger - 2 log types - One for human readability, one for debugging DTS
failures for automated processing. Owen/Juraj will work on a patch for the
future-dts gitlab repo.
-
It should be possible to run functional and performance tests in the
same execution of the DTS.
-
Scapy traffic generator patch is ready. We can send it to the DPDK
community for review
-
Juraj will continue to work on the ‘hello world test case’ patch. - In
Progress
-
Smoke tests to validate the test setup will be another patch series.
This has a dependency on the hello world patch.
Community Engagement
-
Try to get information from vendors so that DTS can replace internal
test harnesses
-
Owen can act as a place to share information that vendors don’t want
to be public but is needed for DTS to replace an internal test harness
-
Ask vendors what they would like us to do for visibility
-
Tag specific people in the update emails?
-
Send out the link again?
-
Developer survey
-
Programming languages
-
Paradigms (OOP, Functional, Procedural)
Review Action Items
-
Lijuan - To create the DTS test suite developer document.
The documentation needs to be based on the changes being done in the
future-dts branch. It is better to write this document incrementally as the
new patches are sent out. The ‘SSH connection’ patch is self explanatory
and does not need documentation. But the documentation would be introduced
with ‘hello world test case patch’. - Blocked until hello world test case
is submitted
-
Owen/Honnappa - Communication on the future-dts branch to DTS community
- Will happen through the presentation at DPDK summit
-
Owen - Add gitlab runner to run devtools for dts on MRs
-
Owen - Make vscode mount the DPDK directory, not the DTS directory, so
that it includes .git
Action Items
-
Honnappa - Patches to DPDK to address DPDK modifications that DTS does.
-
Honnappa - Review the must have list from
https://docs.google.com/spreadsheets/d/1s_Y3Ph1sVptYs6YjOxkUI8rVzrPFGpTZzd75gkpgIXY/edit#gid=1128536548
to ensure correct priority
-
Owen - devtools scripts - Work on feedback
-
Owen/Honnappa - Communication on the future-dts branch to DTS community
- Will happen through the DPDK summit presentation
-
All - Review Juraj’s email about the DTS user guide, the email is old,
so changing the definitions should also be included. - Done
-
Juraj will continue to work on the ‘hello world test case’ patch. - In
Progress
-
Owen - The next step is to create smoke tests to validate the test
setup. The traffic generator abstract APIs can be used in smoke tests. -
Blocked by hello world
-
Owen - Send Scapy traffic generator patch to DPDK community - In progress
-
Honnappa - Send out an email to various company representatives to
review DTS patches in the community
Any other business
-
Next Meeting: Aug 17th, 2022
[-- Attachment #2: Type: text/html, Size: 24328 bytes --]
reply other threads:[~2022-08-10 13:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAHx6DYBu86jamREoQxHSqaTdoBZTBFj1=WwFHriKn7Zv3rxp_A@mail.gmail.com' \
--to=ohilyard@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=ci@dpdk.org \
--cc=dts@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=lijuan.tu@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
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).