diff options
| author |   Morgan Richomme <morgan.richomme@orange.com> | 2017-11-08 14:33:52 +0100 |
|---|---|---|
| committer | Morgan Richomme <morgan.richomme@orange.com> | 2017-11-08 14:35:59 +0100 |
| commit | aa45bd087308d7881be0758a0ae4bc652e274ce6 (patch) | |
| tree | cbf5dec9ad2ec8b7c3b8211dd957f86d3615287f /docs/release-notes.rst | |
| parent | 54c2f258c7e991cb3b5ea7753f48aab6fdf04261 (diff) | |
Fix doc8 errors
JIRA: HOLMES-87
Change-Id: I9d6a6365652ce1120e034298f5e310c7c8fd53b5
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
Diffstat (limited to 'docs/release-notes.rst')
| -rw-r--r-- | docs/release-notes.rst | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst index 216e09f..8ec1479 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -5,10 +5,10 @@ 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. +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.0.0 @@ -20,9 +20,11 @@ Version: 1.0.0 **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 <https://jira.onap.org/browse/HOLMES-4>`_ 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 <https://jira.onap.org/browse/HOLMES-5>`_ 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. +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 <https://jira.onap.org/browse/HOLMES-4>`_ 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 <https://jira.onap.org/browse/HOLMES-5>`_ 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** |