From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK Bug 1374] Stop using xmlrpc server for handling scapy on the TG, move to sending scapy commands via a remote shell.
Date: Thu, 25 Jan 2024 19:59:19 +0000 [thread overview]
Message-ID: <bug-1374-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1374
Bug ID: 1374
Summary: Stop using xmlrpc server for handling scapy on the TG,
move to sending scapy commands via a remote shell.
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: dts
Assignee: dev@dpdk.org
Reporter: probb@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
This is a significant effort to move to a solution which (at best) has feature
parity with our current approach. I agree with Juraj's assessment from the 1/24
DTS meeting that the cost/benefit of this work right now is not compared to
other tickets. So, in my view this can be deprioritized or dropped altogether.
But, just making the ticket anyways so that our meeting topics are represented
here and anyone can chime in if they want.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3115 bytes --]
reply other threads:[~2024-01-25 19:59 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=bug-1374-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).