diff options
author | Katel34 <cl664y@att.com> | 2018-06-06 09:03:09 +0200 |
---|---|---|
committer | Katel34 <cl664y@att.com> | 2018-06-06 09:04:07 +0200 |
commit | 56c8610f708a4f6a20cb86428a88d917289fb651 (patch) | |
tree | 32f9451fec10bed1b8531bdda65beb345a0dbd21 | |
parent | 2bc21cc9a4f0e7810449b692587608af1762932c (diff) |
Fix the identation issue
Change-Id: Ia576d38e61cdb8452ea510fa41105184f0471ebb
Signed-off-by: Katel34 <cl664y@att.com>
Issue-ID: DOC-273
-rw-r--r-- | docs/platform/architecture.rst | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/docs/platform/architecture.rst b/docs/platform/architecture.rst index 351f7af..97f8ddc 100644 --- a/docs/platform/architecture.rst +++ b/docs/platform/architecture.rst @@ -1,15 +1,13 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. -ONAP-level 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. .. image:: images/overall-architecture-in-onap.png -Holmes Architecture -^^^^^^^^^^^^^^^^^^^ Taking a deep dive into Holmes, could observe that it mainly consists of three modules, which are: the rule management module, the engine management module and the data source adapter module respectively. |