[neutron] OVS tunnels and VLAN provider networks on the same interface

Rodolfo Alonso Hernandez ralonsoh at redhat.com
Wed Jun 23 10:30:16 UTC 2021


Hello Krzysztof:

If I understand correctly, what you need is to share a single interface to
handle VLAN and tunneled traffic.

IMO, you can replicate the same scenario as with OVS-DPDK:
https://docs.openvswitch.org/en/latest/howto/userspace-tunneling/

   - The VLAN traffic exits the host using the physical bridge that is
   connected to the external interface.
   - The tunneled traffic is sent to br-tun. There the traffic is tagged
   and sent to the physical bridge and then through the physical interface.

Regards.

On Wed, Jun 23, 2021 at 10:14 AM Krzysztof Klimonda <
kklimonda at syntaxhighlighted.com> wrote:

> Hi All,
>
> What is the best practice for sharing same interface between OVS tunnels
> and VLAN-based provider networks? For provider networks to work, I must
> "bind" entire interface to vswitchd, so that it can handle vlan bits, but
> this leaves me with a question of how to plug ovs tunnel interface (and os
> internal used for control<->compute communication, if shared). I have two
> ideas:
>
> 1) I can bind entire interface to ovs-vswitchd (in ip link output it's
> marked with "master ovs-system") and create vlan interfaces on top of that
> interface *in the system*. This seems to be working correctly in my lab
> tests.
>
> 2) I can create internal ports in vswitchd and plug them into ovs bridge -
> this will make the interface show up in the system, and I can configure it
> afterwards. In this setup I'm concerned with how packets from VMs to other
> computes will flow through the system - will they leave openvswitch to host
> system just to go back again to be sent through a tunnel?
>
> I've tried looking for some documentation regarding that, but came up
> empty - are there some links I could look at to get a better understanding
> of packet flow and best practices?
>
> Best Regards,
>
> --
>   Krzysztof Klimonda
>   kklimonda at syntaxhighlighted.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210623/22d97b03/attachment.html>


More information about the openstack-discuss mailing list