Holmes Rule Management Release Notes

Holmes provides alarm correlation and analysis for telecom cloud infrastructure and services, including hosts, vims, VNFs and NSs. Holmes aims to find the root reason which causes the failure or degradation of services by digging into the ocean of events collected from different levels of the telecom cloud.

Version: 1.2.6

Release Date:2019-06-13

New Features Added some tools to support the extended CCVPN use case:

Bug Fixes

  • HOLMES-204 Alarms can not be deleted from the DB when they get cleared.
  • HOLMES-223 The “ABATED” messages can not be generated in the control loop.

Known Issues

  • If the database is not stable, there may be data/status inconsistency between the rule management module and the engine management module.
  • The current horizontal scaling mechanism can not efficiently balance the load. Optimization is needed in the future.

Security Issues

HOLMES code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, some of the items that remain open have been assessed for risk and determined to be false positive and the rest are planned to be resolved in the next release.

Quick Links:

Upgrade Notes

N/A

Deprecation Notes

N/A

Other

N/A


Version: 1.2.0

Release Date:2018-11-30

New Features In the Casablanca release, Holmes provides its own GUI for rule management tasks:

  • UI Deployment This feature provides a graphic user interface for the sake of easiness of rule management. It mainly provides a rule list view and a rule editing page. Users could get an overview of all rules that have been added to Holmes and create/modify them easily by using the GUI provided by this feature.

Besides, Holmes has been enhanced to be CCVPN use case supportive. CCVPN related assistant tools are added to the common library of Holmes.

Bug Fixes

  • HOLMES-156 Rules can not be deployed after they’ve been added/removed from the engine.
  • HOLMES-133 Don’t rely on key word ‘import’ when extracting package name from rule.
  • HOLMES-130 Holmes can not be successfully registered to MSB when trying to register itself with a health check parameter.

Known Issues

  • If the database is not stable, there may be data/status inconsistency between the rule management module and the engine management module.
  • The current horizontal scaling mechanism can not efficiently balance the load. Optimization is needed in the future.

Security Issues

HOLMES code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The HOLMES open Critical security vulnerabilities and their risk assessment have been documented as part of the project.

Quick Links:

Upgrade Notes

N/A

Deprecation Notes

N/A

Other

N/A


Version: 1.1.0

Release Date:2018-06-07

New Features In the Beijing release, Holmes provides no more functionalites than the Amsterdam release. Its main features remains like follows:

  • Rule Management The feature provides interfaces for the users to create, query, update and delete rules. In this release, they are used along with the DCAE interfaces to accomplish the deployment (creation/update) of the control loop related rules.
  • Engine Management The feature is not exposed to the end user directly. It’s mainly used internally by Holmes as a container for the execution of rules. It provides interface for rule verification and deployment/un-deployment.

Besides, Holmes has been enhanced to meet the platform maturity requirements. The enhancement mainly covers:

  • Scaling: Holmes supports horizontal scale-in/scale-out operations in case it is overloaded by too large amounts of data.
  • Security: Holmes has updated all its APIs to support the HTTPS protocol.

Bug Fixes

N/A

Known Issues

  • If the database is not stable, there may be data/status inconsistency between the rule management module and the engine management module.
  • The current horizontal scaling mechanism can not efficiently balance the load. Optimization is needed in the future.

Security Issues

System Message: WARNING/2 (/home/docs/checkouts/readthedocs.org/user_builds/onap/checkouts/latest/docs/submodules/holmes/rule-management.git/docs/release-notes.rst, line 6); backlink

Duplicate explicit target name: “project”.

HOLMES code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The HOLMES open Critical security vulnerabilities and their risk assessment have been documented as part of the project.

Quick Links:

Upgrade Notes

  • HOLMES-99 Updated the Drools engine to Version 6.5.0.
  • HOLMES-104 Update all interfaces to enforce the HTTPS protocal.
  • HOLMES-112 Following the guideline of the Logging Enhancements Project to implement log collection.
  • HOLMES-106 Implemented horizontal scaling.
  • HOLMES-123 Fixed some vulnerability issues identified by Nexus IQ.

Deprecation Notes

None of the HTTP APIs provided in the Amsterdam release are available in Beijing anymore.

Other

N/A


Version: 1.0.0

Release Date:2017-11-16

New Features In the Amsterdam release, Holmes is mainly intended to support the alarm correlation analysis for the VoLTE scenario. To get us there, Holmes provides the following features:

  • Rule Management The feature provides interfaces for the users to create, query, update and delete rules. In this release, they are used along with the DCAE interfaces to accomplish the deployment (creation/update) of the control loop related rules.
  • Engine Management The feature is not exposed to the end user directly. It’s mainly used internally by Holmes as a container for the execution of rules. It provides interface for rule verification and deployment/un-deployment.

Bug Fixes

This is the initial release.

Known Issues

If the database is not stable, there may be data/status inconsistency between the rule management module and the engine management module.

Security Issues

N/A

Upgrade Notes

N/A

End of Release Notes