[ovs-dev] [PATCH v1 4/4] openvswitch: Userspace tunneling.
Pravin Shelar
pshelar at nicira.com
Fri Oct 24 20:43:48 UTC 2014
On Fri, Oct 24, 2014 at 12:41 PM, Kyle Mestery <mestery at mestery.com> wrote:
> On Fri, Oct 24, 2014 at 2:23 PM, Pravin Shelar <pshelar at nicira.com> wrote:
>> On Fri, Oct 24, 2014 at 7:05 AM, Thomas Graf <tgraf at noironetworks.com> wrote:
>>> First of all, great to see this work. This is awesome! I read through
>>> the code a first time. Planning to do more reviewing but looks very
>>> sane already.
>>>
>>> On 10/16/14 at 11:38am, Pravin B Shelar wrote:
>>>> + 192.168.1.1/24
>>>> + +--------------+
>>>> + | int-br | 192.168.1.2/24
>>>> + +--------------+ +--------------+
>>>> + | vxlan0 | | vxlan0 |
>>>> + +--------------+ +--------------+
>>>> + | |
>>>> + | |
>>>> + | |
>>>> + 172.168.1.1/24 |
>>>> + +--------------+ |
>>>> + | br-eth1 | 172.168.1.2/24
>>>> + +--------------+ +---------------+
>>>> + | eth1 |----------------------------------| eth1 |
>>>> + +--------------+ +----------------
>>>
>>> Might be worth finding other names than int-br and br-eth1 due to
>>> Neutron's usage of br-int and br-ethX to avoid confusion. I realize
>>> that everybody is free to name their bridges but examples tend to get
>>> used 1:1 ;-)
>>>
>>
>> Does Neutron uses br-ethX for something else to cause confusion?
>>
> Neutron uses those for the physical bridge mappings when using the OVS
> agent with the ML2 plugin [1] and VLANs.
>
> [1] http://docs.openstack.org/havana/install-guide/install/apt/content/network-node-install-plugin-openvswitch-agent.html
>
Thanks for the link.
So here we are using the name in similar way, so Why should that cause
confusion?
More information about the dev
mailing list