From: Hangbin Liu <liuhangbin@gmail•com>
To: Jay Vosburgh <jv@jvosburgh•net>
Cc: netdev@vger•kernel.org, Andy Gospodarek <andy@greyhouse•net>,
"David S . Miller" <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
Eric Dumazet <edumazet@google•com>,
Nikolay Aleksandrov <razor@blackwall•org>,
Simon Horman <horms@kernel•org>,
Aaron Conole <aconole@redhat•com>,
Ilya Maximets <i.maximets@ovn•org>,
Adrian Moreno <amorenoz@redhat•com>,
Stanislas Faye <sfaye@redhat•com>
Subject: Re: [Discuss] ARP monitor for OVS bridge over bonding
Date: Sat, 14 Sep 2024 10:01:57 +0000 [thread overview]
Message-ID: <ZuVfFfCYK0NLPSFH@fedora> (raw)
In-Reply-To: <385751.1726158973@famine>
On Thu, Sep 12, 2024 at 09:36:13AM -0700, Jay Vosburgh wrote:
> >
> >The br-ex is not upper link of bond0. ovs-system, instead, is the master
> >of bond0. This make us unable to make sure the br-ex and bond0 is in the
> >same datapath.
>
> I'm guessing that this is in the context of an openstack
> deployment, as "br-ex" and "br-int" are names commonly chosen for the
> OVS bridges in openstack.
It's on a OCP (OpenShift Container Platform) that build with OVN Kubernetes.
>
> But, yes, OVS bridge configuration is very different from the
> linux bridge, and the ARP monitor was not designed with OVS in mind.
>
> I'll also point out that OVS has its own bonding, although it
> does not implement functionality equivalent to the ARP monitor.
>
> However, OVS does provide an implementation of RFC 5880 BFD
> (Bidirectional Forwarding Detection). The openstack deployments that
> I'm familiar with typically use the kernel bonding in LACP mode along
> with BFD. Is there a reason that OVS + BFD is unsuitable for your
> purposes?
LACP need switch config. While arp monitor doesn't need any switch config.
> A single "arp_src_iface" parameter won't scale if there are
> multiple ARP targets, as each target might need a different
> "arp_src_iface."
>
> Also, the original purpose of bond_verify_device_path() is to
> return VLAN tags in the device stack so that the ARP will be properly
> tagged.
Ah, yes, makes sense.
>
> I think what you're really asking for is a "I know what I'm
> doing" option to bypass the checks in bond_arp_send_all(). That would
> also skip the VLAN tag search, so it's not necessarily a perfect
> solution.
Yes.
> Before considering such a change, I'd like to know why OVS + BFD
> over a kernel bond attached to the OVS bridge is unsuitable for your use
> case, as that's a common configuration I've seen with OVS.
As upper comment, this need switch config.
Thanks
Hangbin
next prev parent reply other threads:[~2024-09-14 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 10:17 [Discuss] ARP monitor for OVS bridge over bonding Hangbin Liu
2024-09-12 16:36 ` Jay Vosburgh
2024-09-14 10:01 ` Hangbin Liu [this message]
2024-09-17 9:10 ` Adrián Moreno
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=ZuVfFfCYK0NLPSFH@fedora \
--to=liuhangbin@gmail$(echo .)com \
--cc=aconole@redhat$(echo .)com \
--cc=amorenoz@redhat$(echo .)com \
--cc=andy@greyhouse$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=i.maximets@ovn$(echo .)org \
--cc=jv@jvosburgh$(echo .)net \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=razor@blackwall$(echo .)org \
--cc=sfaye@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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