Re: [OVSDB MDSAL] Creating VXLAN tunnel

Koontz, Marcus G <marcus.g.koontz@...>


I am indeed working on the overlay model provider that will stand up a tunnel using the OVSDB Southbound, but functionality is a work in progress. The overlay would function by sitting on top of the ovsdb southbound and abstract the effort needed now to create the tunnel but some pieces are not yet in place. If you want to see the direction I'm headed so far (warning: it is not yet working as desired):

I haven't been able to create a tunnel using only OVSDB Southbound to date. Stay tuned.


-----Original Message-----
From: Sam Hague [mailto:shague@...]
Sent: Monday, April 13, 2015 4:34 AM
To: Andrej Kincel -X (akincel - Pantheon Technologies SRO at Cisco); Koontz, Marcus G
Cc: ovsdb-dev; Paul Quinn (paulq); Reinaldo Penno (rapenno@...)
Subject: Re: [ovsdb-dev] [OVSDB MDSAL] Creating VXLAN tunnel


are you asking for how to find the vtep ip addresses so you can set the local_ip and remote_ip addresses? If so then we get that from using the other_config:local_ip value in the Open_vSwitch table.

This commit brought the other_config support into ovsdb: [1].

The value is set manually on the ovsdb node with the following:

ipaddr=<ipaddr of vtep>
read ovstbl <<< $(ovs-vsctl get Open_vSwitch . _uuid) ovs-vsctl set Open_vSwitch $ovstbl other_config={"local_ip"="$ipaddr"}

Then you read that value from the operational and use it in your add-port. local_ip is read from the local and remote ovsdb nodes and supplied to the add-port command.

Marcus is working on a tunnel overlay yang model that might do some of this work. It isn't ready yet so doing the above should work until then. Marcus is cc'ed on the email to add info on the overlay model.

Thanks, Sam


----- Original Message -----
From: "Andrej Kincel -X (akincel - Pantheon Technologies SRO at
Cisco)" <akincel@...>
To: "<ovsdb-dev@...>"
Cc: "Paul Quinn (paulq)" <paulq@...>, "Reinaldo Penno
(rapenno@...)" <rapenno@...>
Sent: Monday, April 13, 2015 4:20:14 AM
Subject: [ovsdb-dev] [OVSDB MDSAL] Creating VXLAN tunnel

Hello guys,

I would like to ask for an advice on how to configure VXLAN tunnel
between two OVS Bridges, while using purely only OVSDB MDSAL Southbound API.

I can configure Port/Interface (TerminationPoint) as VXLAN requires,
in other words with use of OVSDB I’m able to reproduce command:

Bridge1: ovs-vsctl add-port br1 vxlan12 -- set interface vxlan12
options:local_ip= options:remote_ip=

Bridge2: ovs-vsctl add-port br2 vxlan21 -- set interface vxlan21
options:local_ip= options:remote_ip=

However, the tunnel will not work unless the entered IP addresses are
not corresponding to IP addresses of network interfaces of machine,
where OVS is running (please correct me if I’m wrong). So the question
is, how to get these IPs or how to set them using OVSDB.

Before, we were usually manually configuring virtual network
interfaces for VXLAN tunnel purposes.



ovsdb-dev mailing list

Join to automatically receive all group messages.