Re: [onap-tsc] Comments about Holmes
Thanks for your comments. This will be discussed and decided at the TSC. Best regard. Roberto De : fu.guangr...@zte.com.cn [mailto:fu.guangr...@zte.com.cn] Envoyé : mercredi 7 juin 2017 16:42 À : KUNG Roberto OLN/QOP Cc : t...@lists.onap.org Objet : 答复: Comments about Holmes Hi Roberto, Thanks for your information. For the overlap, I have to clarify again that although Holmes and Policy are both based on Drools, the goal of them is totally different. Holmes is targeted to find out the correlation among tens of thousands (even more) of alarms while Policy is aimed to which action should be taken to accomplish auto-scaling/auto-healing tasks. I think systems should be defined by what their functions rather than the technologies they adopt. Besides, to make our systems easier to maintain, we have to hold on to the Single Responsibility Principle. If we merge Holmes with Policy, the logic of the policy rules will get much more complicated, which makes it rather hard to trace or fix the problem/bug if any occurs in the futher. For the reasons above, I still suggest we make Holmes an independent project in ONAP. Guangrong 原始邮件 发件人： ＜roberto.k...@orange.com＞; 收件人：付光荣10144542; 抄送人： ＜t...@lists.onap.org＞; 日 期 ：2017年06月07日 04:17 主 题 ：Comments about Holmes https://wiki.onap.org/display/DW/Initial+Project+Proposal+Feedback+From+the+TSC. I have seen that you have taken into account our feedback. I have provided a summary below. · Clarity: Project description and scope are clear. · Overlap: It is felt that the project should be split and combine with DCAE (for the correlation engine), Policy engine (for Drools), and CLAMP (for designing the open loop). · Risk management: this addition to other projects should be discussed with other projects with the objective to add mature/production level code in R1, or could be targeted to subsequent Rs if delivery may be felt difficult · Relevance and prioritization: this is relevant to the ONAP release. I hope this will help with your preparations for next week’s meeting. Roberto _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
[onap-tsc] Comments about Holmes
Dear Guangrong, TSC members reviewed the Holmes project. We would like to provide feedback with the goal of streamlining project reviews and approval next week. Our detailed feedback is available on the wiki: https://wiki.onap.org/display/DW/Initial+Project+Proposal+Feedback+From+the+TSC. I have seen that you have taken into account our feedback. I have provided a summary below. * Clarity: Project description and scope are clear. * Overlap: It is felt that the project should be split and combine with DCAE (for the correlation engine), Policy engine (for Drools), and CLAMP (for designing the open loop). * Risk management: this addition to other projects should be discussed with other projects with the objective to add mature/production level code in R1, or could be targeted to subsequent Rs if delivery may be felt difficult * Relevance and prioritization: this is relevant to the ONAP release. I hope this will help with your preparations for next week's meeting. Roberto _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
[onap-tsc] Feedback about DCAE
Dear Lusheng TSC members reviewed the DCAE project. We would like to provide feedback with the goal of streamlining project reviews and approval in Beijing. Our detailed feedback and questions are available on the wiki: https://wiki.onap.org/display/DW/Initial+Project+Proposal+Feedback+From+the+TSC. You have already with your comments given some answers to the TSC. I would like to underline the following points: * Clarity: Project description and scope are clear. However, the subprojects structure should be clarified, especially what is related to the platform, and what is related to service/applications (VES, collectors, analytics). In particular who are the committers per subproject? Some comments in the wiki may be confusing (for instance, cloud events are out of the DCAE platform, but part of DCAE applications that is part of the DCAE project as I understood it). It has been clarified that DCAE portal is to be used to monitor the DCAE. For applications, this is left to the application level. If this understanding is correct, it means that other projects (SDC, portal) have to take this. * Overlap: the TSC thinks that the relevant part of Holmes should be considered. * Risk management: the project should identify relevant part considered as mature (production level for R1) and identify additions/modification that could be delivered with the similar maturity for R1. * Relevance and prioritization: this is relevant to the ONAP release. I hope this will help with your preparations for next week's meeting. Roberto _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
[onap-tsc] tsc merting
dear all, i will not be able to attend the tsc today. But jamil will attend for me, with eric and vincent. Roberto _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
Re: [onap-tsc] Coordinators
Orange (me) is willing to candidate for SDO/Opensource. RK De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] De la part de GILBERT, MAZIN E (MAZIN E) Envoyé : mercredi 17 mai 2017 13:33 À : onap-tsc Objet : [onap-tsc] Coordinators Team ONAP, This is a reminder that the deadline for self nominations for the open source coordinator and SDO coordinator is today at 9pm PST thanks mazin _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
