Hi Michal, The SDN Agent project is not part of ONAP. SDNC component is actually the global controller which is used to integrate with 3rd party SDN controllers potentially such as ONOS So you should investigate it , e.g. adding generic plugin which call ONOS. Notices that ccsdk project is where generic plugins are developed.
As for option 2 , in SDNC the ODL is used as a generic platform from mapping from ONAP model to a 3rd party model , it's not deployed as "standard" SDN controller. So replacing ODL with ONOS will probably not serve the purpose you need. Avi, From: [email protected] [mailto:[email protected]] On Behalf Of Michal Mach Sent: Wednesday, October 18, 2017 11:59 AM To: [email protected] Cc: 'Gopinath Taget' <[email protected]> Subject: [onap-discuss] Integration with 3rd pary SDN Controllers Hello Onap! I've been evaluating possibilities to integrate ONOS controller with ONAP and I see two approaches for that: 1. Integrating via SDN Agent module, writing dedicated driver/adaptor for ONOS 2. Replacing SDNC module that is based on ODL As the second option seems to be more hack than integration I have a few question regarding the first one. Where can I find the code, designs and information about SDN Agent module? Is the API for writing Adaptor ready? I've tried to find that information on ONAP Wiki, Github and Onap jira but I failed :( [cid:[email protected]] Best regards, [cid:[email protected]] Michał Mach Samsung R&D Institute Poland Samsung Electronics 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-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
