Using ONOS as SDN controller for configuring VxLAN tunneling in Open vSwitch

303 views
Skip to first unread message

Sakthivel Vengatachalam

unread,
Oct 18, 2016, 3:12:17 PM10/18/16
to ONOS Developers
Hi Folks,

I am working on creating a multi tenant private cloud in a Datacenter which hosts lakhs of VMs, using VxLAN & OVS. Its a pure software based solution.

My requirement is to setup a SDN controller, so i choose ONOS.
The goal i want to achieve is to setup vxlan tunneling for VMs using OVS(Open vSwitch) with 3 hypervisor machines (KVM), and the flows should be automatically learnt by SDN when new Hypervisors join the network.

So far, I have installed and configured KVM, OVS, in the hypervisor, and VMs are running with static ip address.
Now i am trying to setup vxlan in ovs, and i do not want to mention the remote_ip of VTEP as options in each ovs switch.
I am doing this now;
>> ovs-vsctl add-port s1 vxlan0 -- set Interface vxlan type=vxlan options:remote_ip="172.17.151.24"

Instead i want the ONOS SDN to do this job for me by doing automatic VTEP discovery whenever a new hypervisor is joined in the network.

I couldn't figure out a way on how to do this.

Am i on the wrong track?
should the ovs-vxlan tunnel be done in some other way in ONOS? any pointers to howto guides would be helpful for me.

What i want to achieve is;
If a new hypervisor joins the network, the SDN should find the VTEP details automatically, and based on the VxLan VNI_ID it should automatically route the packets.
I won't give the remote_ip while configuring each OVS switch.

Is there any APP i need to activate in ONOS? here is the active app list.
onos> apps -a -s
* 9 org.onosproject.ovsdbhostprovider 1.5.1 ONOS information providers and control/management protocol adapter
* 14 org.onosproject.lldpprovider 1.5.1 ONOS LLDP link provider.
* 16 org.onosproject.openflow-base 1.5.1 OpenFlow protocol southbound providers
* 18 org.onosproject.ovsdb-base 1.5.1 OVSDB protocol southbound providers
* 22 org.onosproject.hostprovider 1.5.1 ONOS host location provider.
* 26 org.onosproject.fwd 1.5.1 Reactive forwarding application using flow subsystem.
* 38 org.onosproject.ovsdb 1.5.1 OVSDB southbound meta application
* 64 org.onosproject.drivers 1.5.1 Default device drivers
* 67 org.onosproject.openflow 1.5.1 OpenFlow southbound meta application

Sakthivel Vengatachalam

unread,
Oct 19, 2016, 3:56:48 AM10/19/16
to ONOS Developers
Any help guys?

Jorge Humberto Gomez Velasquez

unread,
Mar 22, 2017, 7:31:53 PM3/22/17
to ONOS Developers, vsakth...@gmail.com
El miércoles, 19 de octubre de 2016, 9:56:48 (UTC+2), Sakthivel Vengatachalam escribió:
> Any help guys?

Did you find any solution ?
Reply all
Reply to author
Forward
0 new messages