Mazin and Junjie, As I was preparing the DCAE project proposal, I had the same impression as Mazin that Holmes correlation engine appeared to align well with DCAE's micro service analytics architecture. Hence I put in a placeholder for possible harmonization with Holmes.
However this afternoon I had some time to briefly scan through Holmes Mercury source code and now I am actually feeling less confident about this impression. Holmes implementation appears to consist of code around two major functional components, a DB (mysql) and a rule engine (Drools). The rules are stored in DB, and loaded into Drools engine. The Drools engine monitors Active MQ topics for alarms, then matches alarms with some rules. Is this high level understanding correct? If so, this actually appears to resemble some of the Policy Engine implementations more than DCAE analytics (cc-ing Pam, who is Policy Engine lead). I think we need to schedule a deep dive meeting finding how to best align. Given now it is already Friday afternoon in China, shall we target early next week? Thanks, Lusheng -------- Original message -------- From: liu.junj...@zte.com.cn Date: 5/11/17 11:10 PM (GMT-05:00) To: gilb...@mail.linuxfoundation.org, "GILBERT, MAZIN E (MAZIN E)" <ma...@research.att.com> Cc: fu.guangr...@zte.com.cn, onap-tsc@lists.onap.org Subject: [onap-tsc] 答复: Re: Proposal for Holmes project Hi Yes, I agree with your suggestion, Holmes will be a Microservice application running in DCAE just like all analytics Microservices. Holmes is not a independence application without DCAE structure. 刘军杰 liujunjie GA产品经理 GA Product Manager 服务及MANO产品部/系统产品 Service & MANO Product Dept./System Product 原始邮件 发件人： ＜ma...@research.att.com＞; 收件人： ＜dr6...@att.com＞;刘军杰10037236; 抄送人： ＜onap-tsc@lists.onap.org＞;付光荣10144542; 日 期 ：2017年05月12日 10:40 主 题 ：Re: [onap-tsc] Proposal for Holmes project Liu, Interesting. I need to spend time looking at Holmes a bit closer. From a first glance, the rule designer seems like a GUI for writing policies. The correlation engine is an algorithm that ingest data and provides signatures based on those correlations. If my interpretation is right, then I suggest putting the correlation engine as a Microservice running in DCAE just like all analytics Microservices. The GUI is similar to CLAMP. CLAMP allows you to design open and closed loop systems besides just putting the policies and rules. CLAMP connects with ONAP during both design and runtime. Something to think about. thanks mazin On May 11, 2017, at 10:29 AM, ROSE, DANIEL V ＜dr6...@att.com<mailto:dr6...@att.com>＞ wrote: ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. The dcae proposal includes holmes as a sub part (* Holmes: this is an OpenO project that performs similar/related role to DCAE. Further information is needed for identifying path for normalization.) Did you talk to anyone from dcae about overlap? If so what was the differences between your projects? Just trying to wrap my head around the difference for my own edification. Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of liu.junj...@zte.com.cn<mailto:liu.junj...@zte.com.cn> Sent: Thursday, May 11, 2017 4:32 AM To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> Cc: fu.guangr...@zte.com.cn<mailto:fu.guangr...@zte.com.cn> Subject: [onap-tsc] Proposal for Holmes project Dear all Holmes project provides alarm correlation and analysis for Telecom cloud infrastructure and services, including host, vim, vnf and ns. Homels aims to find the reason which cause the fail or degradation of services by digging into the ocean of events collected from different levels of Telecom cloud. Holmes is a application that processes events published by managed resources or other applications that detect specific conditions. Based on defined root cause analysis rules about the network, an application of this kind would determine root cause for various conditions and notify other interested applications. ＜image001.png＞ Holmes is consist of a rule designer and a correlation engine.Rule Designer provides a user-friendly GUI to design the Correlation rules. Correlation Engine receives original alarms from monitor and output the result back to monitor after analysis based on rules and the resources relationships from AAI. Real-time Analytic application get the analysis result, which is the root cause can be used to drive the policy runtime for automation operation. ＜image002.png＞ https://wiki.onap.org/display/DW/Holmes<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Holmes&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=Def-eo3qaTtwrD5xDw94jFkzNZ4BDlZSFUX4kaN_jsU&s=fNWGz0RF4pgAEVAy5O-eM1j3Wy32KqC8FszIxUSJrTs&e=> _______________________________________________ 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=Def-eo3qaTtwrD5xDw94jFkzNZ4BDlZSFUX4kaN_jsU&s=6Zy6nCT9YhCL6c9oASVcOQXXfhxJA-Skj-Du9CSWFpg&e=
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
