Many thanks Lizi, I just wanted to clarify one point – in the meeting, we didn’t finalize that ESR would be positioned as a sub-project of A&AI. This decision can be made once we have the clarification around the difference between sub-project and standalone project. Other than that, I agree with your summary and thank you for the constructive meeting!
Hope that’s ok. Colin From: li.z...@zte.com.cn [mailto:li.z...@zte.com.cn] Sent: 08 June 2017 15:42 To: onap-tsc@lists.onap.org Cc: amani...@att.com; jf2...@att.com; Colin Burns <coli...@amdocs.com> Subject: 答复: [onap-tsc] Fw: RE: RE: Re: [onap-discuss] Project Proposal: External System Register Dear TSC, We took the action from today's project review feedback of ESR proposal. After discussion with A&AI team, we have reached consensus about the scope of the ESR and its relationship with A&AI. A&AI team will add ESR as a sub-project in tomorrow's A&AI project proposal. One comment from A&AI team is that is there a clear definition of sub-project and what's the management model for sub-project, I think TSC can clarify that part in tomorrow's meeting. Thanks, Lizi 原始邮件 发件人：李滋00164331 收件人： ＜onap-tsc@lists.onap.org＞; 日 期 ：2017年06月06日 10:02 主 题 ：[onap-tsc] Fw: RE: RE: Re: [onap-discuss] Project Proposal: External System Register Hi guys, I would like to know anybody from A&AI could give me a feedback for pre-email. Since the June developers event is drawing near and the limited time, i think it would be better for us to reach a consensus about consolidating ESR and A&AI before the meeting. Thanks a lot. Lizi 发件人：李滋00164331 收件人： ＜amani...@att.com＞; 抄送人： ＜colin.bu...@amdocs.com＞;赵化冰10201488;孟照星10024238; ＜jf2...@att.com＞; 日 期 ：2017年06月02日 15:22 主 题 ：答复: RE: Re: [onap-tsc] [onap-discuss] Project Proposal: External System Register Hi Jimmy and Manisha, According to the suggestion of Mazin and community, there are certain levels of repetition of technology and algorithms between ESR and A&AI. Just as I have mentioned in my last letter, ESR also provides the function of health cheack of external system and a management portal which are beyond the scope of A&AI. I have clarified the scope of ESR according to the comment of ONAP community. For more detail, please view https://wiki.onap.org/pages/viewpage.action?pageId=5734948 . After the discussion of our team, we have two suggestion about how to consolidate ESR and A&AI. Method1: to merge ESR with A&AI. We move the requirements from ESR into A&AI. Add our team members to A&AI as committers/contributors. We contribute codes to A&AI repository, including the function "Register/query/update/delete function of external systems", "Provide a portal to manage the external systems" and "check whether the external systems are reachable". Method2: put ESR as a subproject under A&AI umbrella We move the ESR subproject proposal under A&AI What do you think about these two approaches? Please let me know your preference. Thanks, LiZi 发件人： ＜amani...@att.com＞; 收件人：李滋00164331; ＜colin.bu...@amdocs.com＞; 抄送人：赵化冰10201488;孟照星10024238; ＜jf2...@att.com＞; 日 期 ：2017年05月31日 11:40 主 题 ：RE: Re: [onap-tsc] [onap-discuss] Project Proposal:ExternalSystemRegister +Jimmy Hi Li Zi, Thank you for your email. We will review the ESR project and then follow-up with you to discuss this further. Thanks, Manisha From: li.z...@zte.com.cn<mailto:li.z...@zte.com.cn> [mailto:li.z...@zte.com.cn] Sent: Friday, May 19, 2017 3:26 AM To: AGGARWAL, MANISHA ＜amani...@att.com＞; colin.bu...@amdocs.com<mailto:colin.bu...@amdocs.com> Cc: zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>; meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn> Subject: Re: Re: [onap-tsc] [onap-discuss] Project Proposal: ExternalSystemRegister Hi Manisha and Colin, I post a proposal about External System Register in ONAP several days ago. The project scope and description can be found in this wiki page 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=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=uSmMgGUSbiZGznUZaqcRyA&m=BuUxCSsPVk4SLNz9HqR1EhITotRnFKdon1MkETO0kCs&s=1p2pmNSfFVNsaudPV2mjL86l0EtBk-jQow2hr9zs1gM&e=>. The feedback from the community suggests that there are certain levels of repetition of technology and algorithms between ESR and A&AI. While we agree with that, we also think there're also some area A&AI haven't covered in its scope such as the registration and health check of external system, the model definition of VNFM and EMS. That's why I'm reaching out today. I would like to discuss the overlapping scope and the potential of cooperation between ESR and A&AI. What do you think? Regards, LiZi 原始邮件 发件人：李滋00164331 收件人： ＜ma...@research.att.com＞; 抄送人： ＜avi.chap...@amdocs.com＞; ＜onap-disc...@lists.onap.org＞; ＜onap-tsc@lists.onap.org＞; 日 期 ：2017年05月19日 15:06 主 题 ：答复: Re: [onap-tsc] [onap-discuss] Project Proposal: ExternalSystemRegister Hi Mazin, Thanks for you suggestion. Yes, there are certain levels of repetition of technology and algorithms between ESR and A&AI. And there're also some area A&AI haven't covered in its scope such as the registration and health check of external system, the model definition of VNFM and EMS. I will contact with A&AI team to figure out how to address these issues and the potential of cooperation . Thanks, LiZi 发件人： ＜ma...@research.att.com＞; 收件人：李滋00164331; 抄送人： ＜avi.chap...@amdocs.com＞; ＜onap-disc...@lists.onap.org＞; ＜onap-tsc@lists.onap.org＞; 日 期 ：2017年05月17日 19:42 主 题 ：Re: [onap-tsc] [onap-discuss] Project Proposal: ExternalSystemRegister LiZi, Thanks for putting the proposal together. The TSC will be continuing a review cycle over the next 2 weeks. I realize the difference and the need of having a system register for external communications, but the question is whether this should be a separate project that may cause further dilution. If the technology and the algorithms used for supporting ESR are similar to others like those used in A&AI, but the type of data is different then I don’t see the need for separate systems. I can see many situations like life cycle management of VNFs using closed loop automation where doing post health checks are critical after repairing a failure. So having both platform and external system data available in one place are key. In general, the TSC will look very closely on projects that need merger to help unify the community and strengthen the developer ecosystem. You are getting good feedback from the community and I suggest you look closer. Regards, Mazin On May 17, 2017, at 5:31 AM, li.z...@zte.com.cn<mailto:li.z...@zte.com.cn> wrote: Hi Avi, ESR will not only store and manage configuration of VIM, but also the configuration of VNFM/SDNC/EMS. It provides a service to centralized management of the information of different kinds of external systems. And it will be used by SO/SDC/VF-C etc. When comes to multi-vim, we suggest that multi-vim using ESR as a dependency component, obtaining the connect information and status of VIM from ESR. For this point, we can have a further discussion. Best regards, LiZi _______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=5FX921RLo79NTx7tKLHbXyljepFXw2thQpj9A1brOP0&s=_OpHzCu-kDteWkDZA7f3ajsdoETVzQ2k4RKRj-9SF8w&e= 发件人： ＜avi.chap...@amdocs.com<mailto:avi.chap...@amdocs.com>＞; 收件人： ＜dr6...@att.com<mailto:dr6...@att.com>＞;李滋00164331; ＜jpianigi...@juniper.net<mailto:jpianigi...@juniper.net>＞; 抄送人： ＜onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap..org>＞; ＜onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>＞; 日 期 ：2017年05月17日 00:31 主 题 ：RE: [onap-tsc] [onap-discuss] Project Proposal: External SystemRegister Hi, Reading the project scope it seems to me a real time configuration repository for external system location and credential specifically for VIM. Probably this should be part of the multi-vim project which should own and manage this configuration. I assume that the component which is used for storing/managing this configuration can be shared across different projects and/or might offered to be a service which any component can use. Avi, From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists..onap.org>] On Behalf Of ROSE, DANIEL V Sent: Tuesday, May 16, 2017 6:51 PM To: li.z...@zte.com.cn<mailto:li.z...@zte.com.cn>; jpianigi...@juniper.net<mailto:jpianigi...@juniper.net> Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> Subject: Re: [onap-tsc] [onap-discuss] Project Proposal: External System Register 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: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of li.z...@zte.com.cn<mailto:li.z...@zte.com.cn> Sent: Tuesday, May 16, 2017 12:49 AM To: jpianigi...@juniper.net<mailto:jpianigi...@juniper.net> Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 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 原始邮件 发件人： ＜jpianigi...@juniper.net<mailto:jpianigi...@juniper.net>＞; 收件人：李滋00164331; 抄送人： ＜stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>＞; ＜onap-...@lists.onap..org<mailto:onap-tsc@lists.onap.org>＞; ＜onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>＞; 日 期 ：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, "li.z...@zte.com.cn<mailto:li.z...@zte.com.cn>" ＜li.z...@zte.com.cn<mailto:li.z...@zte.com.cn>＞ 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 发件人： ＜jpianigi...@juniper.net<mailto:jpianigi...@juniper.net>＞; 收件人： ＜stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>＞;李滋00164331; ＜onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>＞; ＜onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>＞; 日 期 ：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: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen Terrill Sent: Monday, May 15, 2017 10:10 AM To: li.z...@zte.com.cn<mailto:li.z...@zte.com.cn>; onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org> 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: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of li.z...@zte.com.cn<mailto:li.z...@zte.com.cn> Sent: 15 May 2017 04:32 To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org> 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: li.z...@zte.com.cn<mailto:li.z...@zte.com.cn> 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=> 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=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=5FX921RLo79NTx7tKLHbXyljepFXw2thQpj9A1brOP0&s=04OlNSOQ60yNY-VCGRFaauYTlCTHrUFeste5bMF_cxw&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 <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
