[ovs-discuss] VXLAN support in OVS 2.5.0

Michael Ben-Ami mbenami at digitalocean.com
Fri Jan 13 21:26:32 UTC 2017


Shravan, these mininet branches seem to address our problem:

https://github.com/mininet/mininet/pull/577
https://github.com/mininet/mininet/pull/524

I've had more luck with the first one.

On Fri, Jan 13, 2017 at 1:40 PM, Michael Ben-Ami <mbenami at digitalocean.com>
wrote:

> Thanks Joe, I'm looking at feasibility submitting a PR to mininet so that
> it can natively accomplish exactly this.
>
> On Fri, Jan 13, 2017 at 1:31 PM, Joe Stringer <joe at ovn.org> wrote:
>
>> On 13 January 2017 at 08:20, Michael Ben-Ami via discuss
>> <ovs-discuss at openvswitch.org> wrote:
>> > I'm in a very similar boat as Shravan. The utility for me is to be able
>> to
>> > test flow sets on arbitrary mininet topologies that simulate real world
>> > topologies that may or may not use VXLAN. The root cause as I see it is
>> that
>> > mininet must put all OVS bridges in the same namespace. This is
>> probably an
>> > OVS limitation not mininet. Has been discussed a little here:
>> > https://mail.openvswitch.org/pipermail/ovs-discuss/2015-Sept
>> ember/038543.html
>>
>> For what it's worth, I believe that this is a limitation for each OVS
>> instance - each instance can only run bridges in the namespace it is
>> running. If you ran multiple copies of OVS in different network
>> namespaces / containers, it should work. (So would running the copies
>> in different VMs)
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20170113/edc9cf96/attachment.html>


More information about the discuss mailing list