You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This is a potential draft of a project proposal template.  It is not final or to be used until the TSC approves it.

Link to Project Proposal training materials

Project Name:

  • Proposed name for the project: Holmes
  • Proposed name for the repository: Holmes

Project description:

  • 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.

Scope:

  • Filtering: Discard events that are deemed to be irrelevant by Holmes.
  • Compression: Compress multiple occurrences of an alarm into a single alarm.
  • Aggregation: Combine similar alarms into an aggregated alarm.
  • Suppression: inhibit low-priority alarm in the presence of a higher-priority alarm.
  • Root cause analysis?use a smart analysis engine to find the root cause

Architecture Alignment:

        

  • 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.


  • Holmes is consist of a rule designer and a correlation engine.

  • Real-time Analytic application get the analysis result, which is the root cause can be used to drive the policy runtime for automation operation. 

  • 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.

  • Rule Designer provides a user-friendly GUI to design the Correlation rules.

Resources:

  • Primary Contact Person
  • Names, gerrit IDs, and company affiliations of the committers
  • Names and affiliations of any other contributors
  • Project Roles (include RACI chart, if applicable)

Other Information:

  • link to seed code (if applicable)
  • Vendor Neutral
    • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
  • Meets Board policy (including IPR)


Key Project Facts

Project Name:

  • JIRA project name:holmes
  • JIRA project prefix:holmes

Repo name:holmes
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval: 
Link to approval of additional submitters: 

  • No labels