summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGuangrong Fu <fu.guangrong@zte.com.cn>2017-11-10 11:04:03 +0800
committerGuangrong Fu <fu.guangrong@zte.com.cn>2017-11-10 11:04:03 +0800
commit16b5099fe413c629c9760482144677aa4baf356d (patch)
treef3577f0498c7ea8946fefa74e59ef3528cb020cf
parentc1911e7cc30fb4998851478a4322c33e10c8cbed (diff)
Add the Missing Part of the Release Notes
Change-Id: I66faebe40b2c32829c1088da4be5190bd2498fb7 Issue-ID: HOLMES-85 Signed-off-by: Guangrong Fu <fu.guangrong@zte.com.cn>
-rw-r--r--docs/release-notes.rst16
1 files changed, 14 insertions, 2 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index 8ec1479..7ce2f7e 100644
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -14,30 +14,42 @@ ocean of events collected from different levels of the telecom cloud.
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 <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**
+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**
+This is the inital release.
+
**Deprecation Notes**
+N/A
+
**Other**
+N/A
+
===========
End of Release Notes