Dear ONAP TSC Members,

We would like to formally propose the ONAP extensibility project.

This project will describe and define requirements, guidelines and tools for 
extending ONAP. As you know, one of the major problem we encounter with large 
open source projects like ONAP, is the – sometime inevitable – need for 
downstream. This project purpose is to make sure customers – i.e. service 
providers, will be able to extend ONAP and add their own proprietary code, 
without forking out of ONAP, by defining how and where to build an extension 
point? (plugin is just one example), how to manage code extensions? how to 
execute them – running several containers, for example? etc. this project will 
cover backend extension, as well frontend extension, and will standardize it 
across ONAP

Wiki:  https://wiki.onap.org/display/DW/ONAP+Extensibility

The External API team includes participants from: Amdocs and AT&T

Thanx,
Liron

[cid:[email protected]]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc

Reply via email to