diff options
author | 2018-10-25 14:25:13 +0200 | |
---|---|---|
committer | 2018-10-26 08:46:00 +0200 | |
commit | 53ba1707f0da9d64aae53a43d59a5257dd4e12ce (patch) | |
tree | 057744540b68ddba3ca4b782e95eed5b80b16537 /docs/sections/services/ves-hv/architecture.rst | |
parent | 86cd893e8dbbbd02a1b3209baa6da60337ae417a (diff) |
Publish HV-VES documentation including perf3gpp
Change-Id: I8d3e926ce6bc99f981d52eb72fcbe92e8ce67cde
Signed-off-by: kjaniak <kornel.janiak@nokia.com>
Issue-ID: DCAEGEN2-859
Diffstat (limited to 'docs/sections/services/ves-hv/architecture.rst')
-rw-r--r-- | docs/sections/services/ves-hv/architecture.rst | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/docs/sections/services/ves-hv/architecture.rst b/docs/sections/services/ves-hv/architecture.rst new file mode 100644 index 00000000..986e8bb3 --- /dev/null +++ b/docs/sections/services/ves-hv/architecture.rst @@ -0,0 +1,18 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 + +.. _architecture: + +High-level architecture of HV-VES +================================= + +HV-VES Collector is a part of DCAEGEN2. Its goal is to collect data from xNF (PNF/VNF) and publish it in DMaaP's Kafka. +High Volume Collector is deployed with DCAEGEN2 via OOM Helm charts and Cloudify blueprints. + +Input messages come from TCP interface and Wire Transfer Protocol. Each frame includes Google Protocol Buffers (GPB) encoded payload. +Based on information provided in CommonEventHeader, domain messages are validated and published to specific Kafka topic in DMaaP. + +.. image:: ONAP_VES_HV_Architecture.png + +Messages published in DMaaP's Kafka topic will be consumed by DCAE analytics application or other ONAP component that consumes messages from DMaaP/Kafka. +DMaaP serves direct access to Kafka allowing other analytics applications to utilize its data. |