Updated docs

[holmes/rule-management.git] / docs / release-notes.rst

diff --git a/docs/release-notes.rst b/docs/release-notes.rst
deleted file mode 100644 (file)
index 7c5b9ff..0000000
--- a/docs/release-notes.rst
+++ /dev/null
@@ -1,55 +0,0 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-
-
-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.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