| kjaniak | 53ba170 | 2018-10-25 14:25:13 +0200 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. http://creativecommons.org/licenses/by/4.0 |
| 3 | |
| 4 | .. _architecture: |
| 5 | |
| 6 | High-level architecture of HV-VES |
| 7 | ================================= |
| 8 | |
| 9 | 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. |
| 10 | High Volume Collector is deployed with DCAEGEN2 via OOM Helm charts and Cloudify blueprints. |
| 11 | |
| 12 | Input messages come from TCP interface and Wire Transfer Protocol. Each frame includes Google Protocol Buffers (GPB) encoded payload. |
| 13 | Based on information provided in CommonEventHeader, domain messages are validated and published to specific Kafka topic in DMaaP. |
| 14 | |
| 15 | .. image:: ONAP_VES_HV_Architecture.png |
| 16 | |
| 17 | Messages published in DMaaP's Kafka topic will be consumed by DCAE analytics application or other ONAP component that consumes messages from DMaaP/Kafka. |
| 18 | DMaaP serves direct access to Kafka allowing other analytics applications to utilize its data. |