summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGuangrong Fu <fu.guangrong@zte.com.cn>2017-11-09 08:48:36 +0000
committerGerrit Code Review <gerrit@onap.org>2017-11-09 08:48:36 +0000
commitc1911e7cc30fb4998851478a4322c33e10c8cbed (patch)
tree563759f3f1f70a98c42cb6099b0b61c319c733e9
parentcb503f858112a7d6ff1b3b07e39d2bcdb6c72fb1 (diff)
parentaa45bd087308d7881be0758a0ae4bc652e274ce6 (diff)
Merge "Fix doc8 errors"
-rw-r--r--docs/release-notes.rst16
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**