I have to agree with Jacopo and Steve, that’s not business logic that’s basic endpoint health checking.
So to clarify on my and their inputs, it still seems like to me that the entire scope of this project is covered by some combination of A&AI, ONAP OM or MSB depending on who you ask / how you look at it. ONAP Operations manager in particular mentions (Which seems to cover most of your stuff.) • Platform Monitoring & healing: Monitor platform state, Platform health checks, fault tolerance and self-healing Can you please work with someone like David Sauvageau on that project to be sure you have no overlap? Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, May 16, 2017 12:49 AM To: [email protected] Cc: [email protected]; [email protected] Subject: Re: [onap-discuss] [onap-tsc] Project Proposal: External System Register Hi Jacopo, Thanks for your quick response. The business logic can be information verification before store the data to A&AI, and heartbeat detection of the system state. For example, a user sent the authentic url, tenant, username and password of VIM to ESR. ESR try to connect the VIM with these information. After authentic succeed, ESR store these VIM information to A&AI, do heartbeat detection for VIM status and present the system status to user. Best regards, LiZi 原始邮件 发件人： ＜[email protected]＞; 收件人：李滋00164331; 抄送人： ＜[email protected]＞; ＜[email protected]＞; ＜[email protected]＞; 日 期 ：2017年05月16日 11:32 主 题 ：Re: [onap-tsc] Project Proposal: External System Register Not clear what the business logic is. Sent from my iPhone On May 15, 2017, at 8:21 PM, "[email protected]<mailto:[email protected]>" ＜[email protected]<mailto:[email protected]>＞ wrote: Hi Jacopo, Steve: Actually, ESR has some business logic to deal with about external system, such as information verification, which is out the scope of A&AI. When comes to the realization, ESR will be realized relying on A&AI (store the external system data in A&AI). Thanks, LiZi 发件人： ＜[email protected]<mailto:[email protected]>＞; 收件人： ＜[email protected]<mailto:[email protected]>＞;李滋00164331; ＜[email protected]<mailto:[email protected]>＞; ＜[email protected]<mailto:[email protected]>＞; 日 期 ：2017年05月16日 01:19 主 题 ：RE: [onap-tsc] Project Proposal: External System Register Hi, I would agree with Steve about the need to limit overlap between subprojects Jacopo From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Stephen Terrill Sent: Monday, May 15, 2017 10:10 AM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [onap-tsc] Project Proposal: External System Register Hi, While I agree with the need of the external elements to be registered, is there a reason for why we need a separate register in addition to A&AI? (note: I saw that Catherine had a comment with a similar lines). It may also relate to catalogue - LiZi, have you had a chance to chat with the A&AI Project (https://wiki.onap.org/pages/viewpage.action?pageId=3246952<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D3246952&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=VN3D_ogcaDxSbpIsuaSzQJZn7YNp9wDp9ishaCFqQmQ&s=5UHi4PknjAuvCiZXoxTCIOfWV6x2f_FZOaXKQ24Qk1Y&e=> ). Best Regards, Steve. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: 15 May 2017 04:32 To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [onap-tsc] Project Proposal: External System Register Dear ONAP TSC, We would like to formally propose the External System Register project for ONAP. ONAP components need to talk with external systems such as VIM/VNFM/SDNC/EMS to orchestrate a network service, for example, SO/VF-C need to talk with VIM to allocate resource and VNFM to deploy a VNF. So they should get the information of available external systems from a registry before call the Interfaces of these external systems. ESR provides a service to centralized management of the information (name, vendor, version, acess end point, etc.) of external systems. So the ONAP components can get the system information with unified API from a logical single point. The proposal wiki page, which includes details of the project description (including sub projects), project scopes, and proposed repo names, can be found at: https://wiki.onap.org/display/DW/External+System+Register<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_External-2BSystem-2BRegister&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=VN3D_ogcaDxSbpIsuaSzQJZn7YNp9wDp9ishaCFqQmQ&s=mNWGGu-z0aiFTahzuTk_Thvt-Cr4uNP2hPfApRysvWM&e=> Thanks, LiZi 李滋 lizi IT开发工程师 IT Development Engineer 网管及服务开发二部/中心研究院/系统产品 Network Management & Service Development Dept. II/Central R＆D Institute/System Product ＜image001.gif＞ ＜image002.gif＞ 成都市高新区天府大道中段800号中兴通大厦 ZTE Corporation Building, No. 800 Middle Section Tianfu Avenue, Chengdu, P..R.China, 610041 M: +86 15583405168 E: [email protected]<mailto:[email protected]> www.zte.com.cn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.zte.com.cn_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=VN3D_ogcaDxSbpIsuaSzQJZn7YNp9wDp9ishaCFqQmQ&s=W85AWNVdNYPmht6lSL1aU00reo6nKA50wsDPlVKVyVM&e=>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
