Change-Id: I6ebb658881877cc13fb4bb77dc836c6af36ba3b3
Issue-ID: HOLMES-377
Signed-off-by: GuangrongFu <fu.guangrong@zte.com.cn>
project: onap
# Change this to ReleaseBranchName to modify the header
project: onap
# Change this to ReleaseBranchName to modify the header
Holmes Architecture
-------------------
Holmes Architecture
-------------------
-Basically, Holmes itself is an independent component in ONAP, which means it could be deployed as an ONAP-level component. In the Beijing release, Holmes is more generally a DCAE analytic application. It is deployed by DCAE and run as an analytic application on top of it. Also, it could be considered as a filter of the Policy component because it reduces the number of the input messages of Policy.
+Basically, Holmes itself is an independent component in ONAP, which means it could be deployed as an ONAP-level component. In the Guilin release, Holmes is more generally a DCAE analytic application. It is deployed by DCAE and run as an analytic application on top of it. Also, it could be considered as a filter of the Policy component because it reduces the number of the input messages of Policy.
.. image:: images/overall-architecture-in-onap.png
.. image:: images/overall-architecture-in-onap.png
Configuration
-------------
Configuration
-------------
-No machanism for customized configurtions is provided in the El Alto release. Such functionalities will be provided in the future if necessary.
+No machanism for customized configurtions is provided in the Guilin release. Such functionalities will be provided in the future if necessary.
Consumed APIs
-------------
Consumed APIs
-------------
-In the Amsterdam release, Holmes mainly depends on the APIs provided by DCAE, A&AI, DMaaP and MSB.
+In the Guilin release, Holmes mainly depends on the APIs provided by DCAE, A&AI, DMaaP and MSB.
Target Users
^^^^^^^^^^^^
Target Users
^^^^^^^^^^^^
-The human interfaces provided in the Beijing release by Holmes is intended for the developers rather than the end users.
+The human interfaces provided in the Guilin release by Holmes is intended for the developers rather than the end users.
Interface Type
^^^^^^^^^^^^^^
Interface Type
^^^^^^^^^^^^^^
Installation
------------
Installation
------------
-In the El Alto release, Holmes is deployed as an analytic application by the DCAE controller. So the users do not have to install it on their own.
+In the Guilin release, Holmes is deployed as an analytic application by the DCAE controller. So the users do not have to install it on their own.
In case the users want to deploy Holmes independently, the steps for the installation is as follows.
In case the users want to deploy Holmes independently, the steps for the installation is as follows.
Logging & Diagnostic Information
---------------------------------
Logging & Diagnostic Information
---------------------------------
-In the El Alto release, the logs are kept inside the docker containers, which means that you can get the log information only when the docker is still running.
+In the Guilin release, the logs are kept inside the docker containers, which means that you can get the log information only when the docker is still running.
Where to Access Information
^^^^^^^^^^^^^^^^^^^^^^^^^^^
Where to Access Information
^^^^^^^^^^^^^^^^^^^^^^^^^^^