Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titleThe location of Holmes

Holmes should be an independent project instead of being a sub-project of DCAE for following reasons:

  1. Holmes supports different data sources, including but not limited to DCAE. If Holmes is made a sub-project of DCAE, when other components want to use Holmes as their analysis tool, they have to deploy DCAE first and then convert their data format to the VES standard.
  2. Holmes is a realtime or quasi-realtime data stream analysis system. DCAE is a big data platform, which means there will be a delay before any data get to Holmes after they are received by DCAE due to the pre-processes provided by DCAE. This will impact the performance of Holmes.

Therefore, we suggest Holmes to be approved as an independent project (as a potential data consumer of DCAE).



Scope:

  • Alarm Correlation Rule Management

    • Holmes provides basic rule management functionalities which allow users to design, create or modify rules via a rule designer.
  • Collect Alarms from Different Alarm Sources

    • Holmes supports different kinds of alarm sources, including NFV, SDN and any other legacy systems (as long as the corresponding interfaces of the source system are exposed).
  • Alarm Analysis
    • Holmes can pick out the root cause from the ocean of alarms with the assistance of the topology information provided by other related systems.
  • Persistence of the Results of Data Analyses
    • All analytic results are written to DB for persistence.
    • Holmes provides the functionality for users to view the statistical result of data analysis.
  • Publish the Analytic Results to Subscribers
    • Besides result persistence, Holmes publishes the analytic results to a specific topic. Any potential users can subscribe to the topic to get the results in real time. 

...