Atrium BGP Router Application Proposal
|
manoj.krishnan@...
Hi ODL Team,
We would like to propose BGP Peering Router application that we have released as part of ONF Atrium Project (https://www.opennetworking.org/?p=1757&option=com_wordpress&Itemid=316). As part of Release 16/A we have implemented a BGP Router application on Opendaylight controller which can peer with any E-BGP compliant device and details of the implementation is available in the following links * Overview : https://github.com/onfsdn/atrium-docs/wiki/ODL-Based-Atrium-Router-16A * Source Code : https://github.com/onfsdn/atrium-odl
Kindly consider this project as part of Opendaylight Boron Release. Please let us know if any additional details are required.
Regards
Manoj |
|
|
|
Colin Dixon
Cool! I'm reading through it now. --ColinOn Wed, Mar 2, 2016 at 5:31 AM, <manoj.krishnan@...> wrote:
|
|
|
|
Robert Varga
On 03/02/2016 11:31 AM,
manoj.krishnan@... wrote:
Hello Manoj,
Looking over the architecture I have to wonder how this really fits in with projects already present in OpenDaylight. We already do have a programmable, scalable, portable BGP stack, which can peer in iBGP, eBGP and RR roles and supports a wide variety of AFI/SAFIs (with more being added in each release). Thanks, Robert |
|
|
|
JP <jp@...>
Hi Robert
There was an enhancement done on the ONOS routing application to use the FPM interface rather than iBGP peering as the northbound. It allows for interacting with routing protocols other than BGP. Would such an enhancement if done for the ODL application sufficiently differentiate?
BTW, there is another aspect of the Atrium distribution, the flow objectives interface which provides data plane portability. The changes for this portion of this code as being brought in as part of the didm project.
-JP
From: Robert Varga [mailto:nite@...]
Sent: 03 March 2016 02:31 To: manoj.krishnan@...; project-proposals@... Cc: atrium_eng@...; saurav.das@...; subhas.mondal@...; jp@...; subhash_singh@... Subject: Re: [Project-proposals] Atrium BGP Router Application Proposal
On 03/02/2016 11:31 AM, manoj.krishnan@... wrote:
|
|
|
|
Tony Tkacik
Hi, lookuped up thru code and it seems Atrium has own implementation of BGP, Are there any plans to migrate to OpenDaylight BGP protocol stack?
Tony
From: project-proposals-bounces@...
[mailto:project-proposals-bounces@...] On Behalf Of Robert Varga
Sent: Wednesday, March 02, 2016 10:01 PM To: manoj.krishnan@...; project-proposals@... Cc: atrium_eng@...; saurav.das@...; subhas.mondal@...; jp@...; subhash_singh@... Subject: Re: [Project-proposals] Atrium BGP Router Application Proposal
On 03/02/2016 11:31 AM, manoj.krishnan@... wrote:
|
|
|
|
manoj.krishnan@...
Hi Tony/Robert/Colin,
Thanks for the response. So far there is no plan to replace the BGP stack . But we will discuss in next week's atrium meeting and update you. Please let us know if that is mandatory.
Regarding the differentiators, JP already sent another mail. To summarize following are some key differentiators
* The application leverages DIDM project to install the flows in a pipeline agnostic manner
* We inherited the concept of Flow objectives which Saurav implemented in ONOS BGP Router (15/A) variant. Flow objectives expose simplified and generic APIs towards applications abstracting the pipeline complexities . * In 16/A release of ONOS Atrium, there is support for installing routes learned through other routing protocols as well - OSPF, IS-IS etc. This feature is not implemented in ODL variant yet but can be a road map item.
* 16/A ODL has pre-integrated driver for hardware switches like Novflow and many other vendors showed interest to build drivers to enable BGP routing capability. This will be an added advantage to have a ready to use routing SDN stack.
Saurav, kindly add/update above points .
Regards
Manoj
From: Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES at Cisco) <ttkacik@...>
Sent: Thursday, March 3, 2016 2:23 PM To: Robert Varga; Manoj K Nair (NEP); project-proposals@... Cc: atrium_eng@...; saurav.das@...; SUBHAS MONDAL (CISCO); jp@...; subhash_singh@... Subject: RE: [Project-proposals] Atrium BGP Router Application Proposal Hi, lookuped up thru code and it seems Atrium has own implementation of BGP, Are there any plans to migrate to OpenDaylight BGP protocol stack?
Tony
From: project-proposals-bounces@...
[mailto:project-proposals-bounces@...] On Behalf Of Robert Varga
On 03/02/2016 11:31 AM, manoj.krishnan@... wrote:
|
|
|
|
Chris
Hi Manoj, wrt: Please let us know if that is mandatory. It is most certainly not mandatory in ODL to force any design decision on projects. However I think what we would look for as a community is to understand how to bring our projects together and how to best leverage the code base that is available into a cohesive system. As such, I think there is a lot of value in investigating the similarities, differences, architecture of the BGP alternatives, finding a way, and having clear plans for, the ODL community to align around one implementation where possible. We have seen in our community that projects are able to adjust to community activity and find ways to align. I would suggest that is the right goal to have in mind here as well. / Chris From: <project-proposals-bounces@...> on behalf of <manoj.krishnan@...> Date: Thursday 3 March 2016 at 11:20 To: <ttkacik@...>, <nite@...>, <project-proposals@...> Cc: <atrium_eng@...>, <saurav.das@...>, <subhas.mondal@...>, <jp@...>, <subhash_singh@...> Subject: Re: [Project-proposals] Atrium BGP Router Application Proposal Hi Tony/Robert/Colin, Thanks for the response. So far there is no plan to replace the BGP stack . But we will discuss in next week's atrium meeting and update you. Please let us know if that is mandatory.
Regarding the differentiators, JP already sent another mail. To summarize following are some key differentiators
* The application leverages DIDM project to install the flows in a pipeline agnostic manner
* We inherited the concept of Flow objectives which Saurav implemented in ONOS BGP Router (15/A) variant. Flow objectives expose simplified and generic APIs towards applications abstracting the pipeline complexities . * In 16/A release of ONOS Atrium, there is support for installing routes learned through other routing protocols as well - OSPF, IS-IS etc. This feature is not implemented in ODL variant yet but can be a road map item.
* 16/A ODL has pre-integrated driver for hardware switches like Novflow and many other vendors showed interest to build drivers to enable BGP routing capability. This will be an added advantage to have a ready to use routing SDN stack. Saurav, kindly add/update above points . Regards Manoj From: Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES at Cisco) <ttkacik@...> Sent: Thursday, March 3, 2016 2:23 PM To: Robert Varga; Manoj K Nair (NEP); project-proposals@... Cc: atrium_eng@...; saurav.das@...; SUBHAS MONDAL (CISCO); jp@...; subhash_singh@... Subject: RE: [Project-proposals] Atrium BGP Router Application Proposal Hi, lookuped up thru code and it seems Atrium has own implementation of BGP, Are there any plans to migrate to OpenDaylight BGP protocol stack?
Tony
From: project-proposals-bounces@...
[mailto:project-proposals-bounces@...] On Behalf Of Robert Varga
On 03/02/2016 11:31 AM, manoj.krishnan@... wrote:
|
|
|
|
Colin Dixon
It would be good if you could add your project proposal here in the same format as the others: After that, there's a two-week public review period before you can schedule a creation review during the TSC meeting.https://wiki.opendaylight.org/view/Project_Proposals:Main#Proposals_Submitted_For_Review https://wiki.opendaylight.org/view/Project_Proposals:Main#Guidelines_for_your_Creation_Review On Wed, Mar 2, 2016 at 5:31 AM, <manoj.krishnan@...> wrote:
|
|
|