Thanks Yang, Very informative. I just have one last query. Regarding LCM, should EMS then, be introduced as S-VNFM under VF-C ? If so, are there any specs / docs ?
BR, Viswa <http://www.verizon.com> Viswanath Kumar Skand Priya Architect Verizon India ( VDSI ) On Mon, Jan 29, 2018 at 3:14 PM, Yan Yang <[email protected]> wrote: > Hi Viswa, > > > > Please see my response to your question below. Hope this helps. > > > > > > > > Best Regards, > > Yan > > *发件人:* Kumar Skand Priya, Viswanath V [mailto:viswanath. > [email protected]] > *发送时间:* 2018年1月29日 13:06 > *收件人:* Yan Yang > *抄送:* Kedar Ambekar; [email protected] > *主题:* Re: [E] [onap-discuss] 答复: [vf-c] Query regarding EMS Driver > > > > Hi Yan, > > > > I have few follow-up questions based on your reply to Kedar. > > - When you term Vendor can develop their own EMS driver, what would be > the interface mechanism between VF-C and EMS driver ? Or in other words, > how does VF-C knows the presence of this EMS driver ? > > [A] There is no direct interface between EMS driver and VF-C. As I > explained in the previous email , EMS driver as a microservice, it directly > interacted with EMS and DACE VES collector. > > For all EMS, they should be registered as external system In ESR Portal. > And we can get their information from A&AI. > > - How & when does VF-C instructs this EMS driver to start streaming > VES data to DCAE VES collector ? > > [A] When EMS driver starts, it will detect the registered EMS > information from A&AI. When find registered EMS, it will create connection > and collect the data from EMS , when received data , it will translate data > to VES format and then report to DCAE VES collector. > > - Does every EMS has to mandatorily provide data in VES format only ? > > [A] No, they can have their own data format, but if they want report data > to DCAE and do some analysis, they should do the data format conversion. > > - Does the functionalities of EMS includes only FCAPS & VES data > translation only ? What if EMS wants to also do LCM of a VNF ? > > [A] In VoLTE use case in Amsterdam release, we only use EMS to collect > FCAPS data. VNFM is responsible for VNF LCM > > - Does vendor NMS also takes the same flow as EMS ? > > [A] Currently only integrated ems > > BR, > > Viswa > > > > > <http://www.verizon.com> > > > > Viswanath Kumar Skand Priya > > Architect > > Verizon India ( VDSI ) > > > > > > On Mon, Jan 29, 2018 at 6:51 AM, Yan Yang <[email protected]> > wrote: > > Hi KeDar, > > > > Thanks for your question. > > Please see my response below in your email in green. > > > > > > > > Best Regards, > > Yan > > *发件人:* [email protected] [mailto:onap-discuss-bounces@ > lists.onap.org] *代表 *Kedar Ambekar > *发送时间:* 2018年1月26日 19:57 > *收件人:* [email protected] > *主题:* [onap-discuss] [vf-c] Query regarding EMS Driver > > > > Hi, > > > > I have couple of doubts on EMS driver in VF-C. > > > > 1. Is the EMS driver generic to integrate with any external vendor > EMS ? > > [A] No, it’s not generic EMS driver. Vendor can implement their own EMS > driver to integrate their EMS. > > 2. Which EMS is used to test this driver for Amsterdam release ? > > [A] In VoLTE closed-loop scenario of healing in Amsterdam > release, this EMS driver was used to collect FCAPS data from ZTE EMS. > > 3. What mechanism this driver currently support to integrate itself > with EMS ? > > [A] This driver functions include collecting FCAPS data from > EMS, converting data format to VES, reporting VES data to DCAE VES > collector. > > 4. If the answer of # 1 is no, is there any document to develop > driver for a vendor EMS ? > > [A] No document, as I mentioned above, vendor can implement their > own EMS driver to integrate their EMS. > > > > Appreciate reply on these ! Thank you. > > > > Regards, > > KeDar > > ============================================================ > ================================================================ > > Disclaimer: This message and the information contained herein is > proprietary and confidential and subject to the Tech Mahindra policy > statement, you may review the policy at http://www.techmahindra.com/ > Disclaimer.html > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMFbw&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=ZKZT2E1mC-ZHv5uGYH7Xdpb6vVyISDJTZN9L3wFPRKA&s=_v6puMLt_LHMCaPy1VMFQYH7qjVNVCvcLcc-LSQ2imA&e=> > externally http://tim.techmahindra.com/tim/disclaimer.html > <https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMFbw&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=ZKZT2E1mC-ZHv5uGYH7Xdpb6vVyISDJTZN9L3wFPRKA&s=LzzGuoHRDycQpUSCyyZXClQivRKxy6cdbLzBs62oRH4&e=> > internally within TechMahindra. > > ============================================================ > ================================================================ > > > _______________________________________________ > onap-discuss mailing list > [email protected] > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. > onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c= > udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE- > 2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=ZKZT2E1mC- > ZHv5uGYH7Xdpb6vVyISDJTZN9L3wFPRKA&s=gy736bRsjQJkmus0kzCjp6zRtBQYB7 > LrRESUWdrw8xU&e= > > >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
