Date
Attendees
LFN Staff: Kenny Paul, Casey Cain
Community: Abirami Thangavel ,@Ahmed Sawaf, @ArunChapagain, @Dan TImoney, @felix katz, @gennadi gorey, Herakliusz Lipiec , @hussain harboosh, @Kaluankumar Asangi, @Khaled Ibrahim, @kingsley lawrence, Krzysztof Kajkowski , @Kuldeep Negi, @lulah Alshogeir, @MD Ishrad Sheikh, @mishal alshahrani, @m suleman tariq, @muhammad sajjad, @munthir alotaibi, Prabhjot Singh Sethi, Sai Pujita T , Ranny Haiby, @reddi sekhar, sagar Chitnis, Soujanya R M, @stefan garcia, Subramanian M @vasyl razinkov
Overview
Discussion on the integration architecture and the work needed to get the integration done
- Schedule: https://teamup.com/event/show/id/Dp4eZkYiouDzfZjT8QY7qFjLdugkpR
- Recording:
- Slides:
Minutes
- Presentation by Prabhjot
- Benefits for TF community - additional developers, CNF use cases
- ONAP community - SDN functionality, variety in SDN controllers, LFN synergy
- There is a history of integration between ECOMP and Contrail - the commercial "parents" of ONAP and TF
- Possible integration was discussed in the recent LFN Whitepaper - https://www.lfnetworking.org/resources/2020/04/28/lf-networking-whitepaper/
- TF extends the OpenStack networking API with templating capabilities. Offering BGP peering, service chaining, etc.
- TF has integration with both OpenStack and K8S. But the functionality exposed through standard OpenStack and K8S APIs is limited. Real value is provided through extensions.
- There is an expectation from the TF side to see a standardization of interfaces towards an SDN controller, for providing the required functionality such as BGP.
- Potential integration should cover both orchestration and E2E monitoring
- Open discussion
- One low hanging fruit could be re-using the code from the ECOMP/Contrail integration. This will require legal approval from the AT&T side
- legacy code may be obsolete at this point
- typical end-users of TF are both Telco and Enterprise
- APIs alone are probably not a significant driver
- In ONAP Aarna is working on virtual central office (VCO) for telcos - may be a good use-case for collaboration
- Both communities are limited as to available developer and test resources to perform work
- Technical followup meeting is necessary - joint meeting between TSCs would be appropriate. Should be a "sales pitch" to ONAP
Action items
- @Dan Timoney follow-up within AT&T on the possibility of bringing in legacy seed code
- Kenny Paul , Casey Cain schedule time at an upcoming ONAP TSC meeting for a presentation from TF TSC