How does ONOS deal with traditional routing protocols?

[Chenhaitao (William)]

Hello!

May I ask several question about the routing process of ONOS? My questions are below:
1. For the traditional routing protocols OSPF, IS-IS and BGP, the process models are built-in ONOS kernel or not?
2. When the forwarder received a OSPF packet, what is the process on the Forwarder? What kind of Encapsulation Format will be adapted for the OSPF packet between the forwarder and the controller?
3. How dose ONOS realize MPLS L2/L3 VPN?
All these question are relationship with this question: is it possible to replace traditional router with ONOS Controller + Forwarder(OpenFlow based maybe)? If it's possible, when? I hope to know the roadmap of ONOS to achieve entire routing functions.

And more questions:
1. What kinds of SBI protocol will be realized by ONOS? When OpenFlow1.3, NetConf, PCEP and other SBI will be achieved? And the version of ONOS?
2. If I want to design a Metro Network based on OpenFlow1.3 + ONOS, then when will be the reasonable date?

Please reply soon. I am waiting for...

Thank you very much!

Best Regards and Good Luck!
________________________________________
Chen Haitao
Senior Marketing Manager
Russia Marketing Dept.
Russian Huawei Technologies Co., Ltd.
william.c...@huawei.com
Business Park "Krylatsky Hills", bldg."B"
Krylatskaya Str., 17
Moscow 121614, Russia

[Patrick Liu]

Hi Haitao, See inline reply...[Patrick]

-----Original Message-----
From: Chenhaitao (William) [mailto:william.c...@huawei.com]
Sent: Wednesday, August 26, 2015 6:36 PM
To: onos...@onosproject.org
Subject: [onos-dev] How does ONOS deal with traditional routing protocols?
Importance: High

Hello!

May I ask several question about the routing process of ONOS? My questions are below:
1. For the traditional routing protocols OSPF, IS-IS and BGP, the process models are built-in ONOS kernel or not?

[Patrick] by ONOS architecture, legacy protocol you listed here should be implemented as Provider, and comply with its architecture (protocol+adapter) and its abstracted interface (Link/device/....etc). ONOS core are protocol agnostic. Provider is located in south bound of ONOS.

2. When the forwarder received a OSPF packet, what is the process on the Forwarder? What kind of Encapsulation Format will be adapted for the OSPF packet between the forwarder and the controller?

[Patrick] control packet is punted to controller's Provider for processing. Control packets are not encap's into OF packet when they punted to controller and injected from controller to device. They are using its native way (e.g. TCP) to convey the control packet.

3. How dose ONOS realize MPLS L2/L3 VPN?

[Patrick] L2/L3VPN can be implemented as APP of ONOS. in Huawei's Agile VPN, we add Tunnel Manager, Label Manager into ONOS core, extended Flow Rule API for table update, and implemented L3VPN service in APP.

All these question are relationship with this question: is it possible to replace traditional router with ONOS Controller + Forwarder(OpenFlow based maybe)?

[Patrick] Yes. ONOS has implanted BGP router. See ONOS wiki for more information.

If it's possible, when? I hope to know the roadmap of ONOS to achieve entire routing functions.

And more questions:
1. What kinds of SBI protocol will be realized by ONOS? When OpenFlow1.3, NetConf, PCEP and other SBI will be achieved? And the version of ONOS?

[Patrick] By Drake release (at the end of Aug), you will see NETCONF, OF1.1/1.3, PCEP, and OVSDB

2. If I want to design a Metro Network based on OpenFlow1.3 + ONOS, then when will be the reasonable date?

[Patrick] what feature do you need? ONOS will support Cap-Grow-Drain in next release (Emu). Marc is leading this efforts. Marc may provide more details and current status for you.

Please reply soon. I am waiting for...

Thank you very much!

Best Regards and Good Luck!
________________________________________
Chen Haitao
Senior Marketing Manager
Russia Marketing Dept.
Russian Huawei Technologies Co., Ltd.
william.c...@huawei.com
Business Park "Krylatsky Hills", bldg."B"
Krylatskaya Str., 17
Moscow 121614, Russia

--
You received this message because you are subscribed to the Google Groups "ONOS Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to onos-dev+u...@onosproject.org.
To post to this group, send email to onos...@onosproject.org.
Visit this group at http://groups.google.com/a/onosproject.org/group/onos-dev/.
To view this discussion on the web visit https://groups.google.com/a/onosproject.org/d/msgid/onos-dev/D78C931DD484F74E929DEBB54EAF622B6382D797%40lhreml502-mbb.

[Luca Prete]

Hello Chen,

Please, let me just underline that wouldn't make that much sense (do you have a specific use case for this?) to implement IGP protocols like OSPF or IS-IS in ONOS. Indeed, in case of logically centralized SDN controllers like ONOS, the protocols are replaced on the controller - which has a centralized view of the network in form of a graph - by a Path Computation Element (PCE) - in our case by default Dijkstra.

By their nature, protocols like the ones mentioned by you above are created to work in a distributed fashion instead. If you would try to implement them in ONOS, you would probably loose one of the biggest technical benefit of the paradigm.

Talking instead about BGP, we've two applications so far that respectively:

- Peering router (Atrium project): transform a single OpenFlow switch into a BGP router (reference here: https://wiki.onosproject.org/display/ONOS/Peering+Router+-+ONF's+Project+Atrium)

- SDN-IP: transforms an entire OpenFlow network into a transit IP network, enabling the communication between different external (legacy and SDN) networks, using BGP. (reference here: https://wiki.onosproject.org/display/ONOS/SDN-IP)

We implemented this with the main goals of:

- keep talking to the rest of the legacy equipment and networks still out there

- provide a migration path to SDN

- make your control plane more scalable

Last, but not the least. We implement (already) at the southbound also TL1 to talk to the optical equipment.

Hope it helps, regards,

Luca

To view this discussion on the web visit https://groups.google.com/a/onosproject.org/d/msgid/onos-dev/A69C231CFD3C424481572CBD93E0CB94521FEE23%40SJCEML701-CHM.china.huawei.com.