From: Aaron Conole <aconole@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, dev@openvswitch.org,
linux-kselftest@vger.kernel.org
Subject: Re: selftests: openvswitch: Questions about possible enhancements
Date: Thu, 25 Apr 2024 15:58:32 -0400 [thread overview]
Message-ID: <f7t1q6t9puf.fsf@redhat.com> (raw)
In-Reply-To: <20240424173000.21c12587@kernel.org> (Jakub Kicinski's message of "Wed, 24 Apr 2024 17:30:00 -0700")
Jakub Kicinski <kuba@kernel.org> writes:
> On Wed, 24 Apr 2024 17:44:05 +0100 Simon Horman wrote:
>> I have recently been exercising the Open vSwitch kernel selftests,
>> using vng,
>
> Speaking of ovs tests, we currently don't run them in CI (and suffer
> related skips in pmtu.sh) because Amazon Linux doesn't have ovs
> packaged and building it looks pretty hard.
>
> Is there an easy way to build just the CLI tooling or get a pre-built
> package somewhere?
As Simon notes - we would need some support in the ovs-dpctl.py to set
up the tunnel interfaces, and probably need to set them up for lwt and
classic tunnels.
I have a test branch where I have support for the former, and I can
clean it up and submit it.
> Or perhaps you'd be willing to run the OvS tests and we can move
> the part of pmtu.sh into OvS test dir?
I guess either would be fine, as long as they can get run.
prev parent reply other threads:[~2024-04-25 19:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 16:44 selftests: openvswitch: Questions about possible enhancements Simon Horman
2024-04-24 17:37 ` [ovs-dev] " Simon Horman
2024-04-24 17:59 ` Benjamin Poirier
2024-04-24 18:14 ` Aaron Conole
2024-04-25 7:33 ` Simon Horman
2024-04-24 18:14 ` Aaron Conole
2024-04-25 7:40 ` Simon Horman
2024-04-25 20:00 ` Aaron Conole
2024-04-25 0:30 ` Jakub Kicinski
2024-04-25 8:26 ` Simon Horman
2024-04-25 18:57 ` [ovs-dev] " Simon Horman
2024-04-25 19:21 ` Jakub Kicinski
2024-04-25 20:04 ` Aaron Conole
2024-04-26 7:05 ` Simon Horman
2024-04-25 19:58 ` Aaron Conole [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=f7t1q6t9puf.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=dev@openvswitch.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.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).