Hi Maopeng, all, I let External Controller functionality proposal answer the raised questions. As to the project’s impact, as we are not talking about SD-WAN’s –only External Controller now, I believe that also project impacts should be taken separately not within the scope of SD-WAN only, rather generalized.
Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D34338.2AFD76C0] From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] Sent: Thursday, October 12, 2017 4:27 AM To: Alla Goldner <alla.gold...@amdocs.com> Cc: pdrag...@research.att.com; onap-tsc@lists.onap.org; onap-...@lists.onap.org; onap-usecase...@lists.onap.org Subject: 答复: Re: [onap-tsc] [Onap-arc] External controller support in BeijingRelease hi Alla There are projects impact in the wiki. Could we refer it? thanks. https://wiki.onap.org/pages/viewpage.action?pageId=11929755 Interface appearance: [Image removed by sender.] Project Impact: [Image removed by sender.] BR Maopeng 原始邮件 发件人： <alla.gold...@amdocs.com>; 收件人： <pdrag...@research.att.com>; <onap-tsc@lists.onap.org>; 抄送人： <onap-...@lists.onap.org>; <onap-usecase...@lists.onap.org>; 日 期 ：2017年10月10日 13:10 主 题 ：Re: [onap-tsc] [Onap-arc] External controller support in BeijingRelease Thanks, Pam, Here is the updated list with also one typo corrected. 1. AAI, incl. ESR 2. SDC, VNF SDK, Modelling 3. SO 4. VID 5. External API 6. DCAE, HOLMES, Policy, CLAMP Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D34338.2AFD76C0] From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com] Sent: Monday, October 09, 2017 7:05 PM To: Alla Goldner <alla.gold...@amdocs.com>; onap-tsc@lists.onap.org P <onap-tsc@lists.onap.org> Cc: onap-...@lists.onap.org; onap-usecase...@lists.onap.org Subject: Re: [Onap-arc] External controller support in Beijing Release Alla, If you intend to use the External Controller for any control loop use cases then you will need Policy. With that being said, the request from the Policy team is a single common Controller SDK to be implemented by all controllers for performing any type of action on a VM/VNF. And as simplistic an API as possible. The current API implementations for SO/APPC/VFC are overly complicated and require too much interaction with A&AI. Thanks, Pam From: <onap-arc-boun...@lists.onap.org<mailto:onap-arc-boun...@lists.onap.org>> on behalf of Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> Date: Monday, October 9, 2017 at 11:50 AM To: "onap-tsc@lists.onap.org P<mailto:onap-tsc@lists.onap.org%20P>" <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Cc: "onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>" <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>, "onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>" <onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>> Subject: [Onap-arc] External controller support in Beijing Release Hi all, We (Usecase subcommittee) would like to initiate a discussion with a different involved projects on potential implementation of External controller in Beijing Release. Next week, we need to present and get a view from the following affected projects: 1. AAI, ESI 2. SDC, VNF SDK 3. Modelling 4. SO 5. VID 6. External API 7. DCAE, HOLMES 8. CLAMP And, of course, from the architecture and modelling subcommittees. (Ramesh, please add any potentially affected projects I may have forgotten). One way is to schedule a new meeting. The alternative way is to ask Chris for Architecture subcommittee meeting’s time and discuss it there ☺ What do you think? Chris, is there any possibility to host this discussion next week? Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image002.png@01D34338.2AFD76C0] 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=BPpbIMtWz3IWAh_XsuepRoZss7N0GWC9-v6pYEh_unk&s=r-g9j6tieoh0RKObysLSW_mLXqTV4Ai1PR7UMHXazGE&e=> 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 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 ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
