Piotr Jaszczyk | 19736a9 | 2018-09-24 11:27:58 +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 | |
| 5 | High Volume VNF Event Streaming (HV-VES) Collector |
| 6 | ================================================== |
| 7 | |
| 8 | .. Add or remove sections below as appropriate for the platform component. |
| 9 | |
Piotr Jaszczyk | 19736a9 | 2018-09-24 11:27:58 +0200 | [diff] [blame] | 10 | |
Filip Krzywka | 4bb79b7 | 2018-09-25 10:57:17 +0200 | [diff] [blame] | 11 | **HV-VES collector** has been proposed, based on a need to process high-volumes of data generated frequently by a large |
| 12 | number of NFs. The driving use-case is described and published within presentation during Casablanca Release Developer Forum: |
| 13 | `Google Protocol Buffers versus JSON - 5G RAN use-case - comparison`_. |
| 14 | |
| 15 | .. _`Google Protocol Buffers versus JSON - 5G RAN use-case - comparison`: https://wiki.onap.org/download/attachments/25434845/Casablanca_Dev_Forum_GPB_comparison_20180621.pptx?version=1&modificationDate=1530275050000&api=v2 |
| 16 | |
| 17 | The goal of the collector is to support high volume data. It uses plain TCP connections. |
| 18 | Connections are stream-based (as opposed to request-based) and long running. |
| 19 | Payload is binary-encoded (currently using Google Protocol Buffers). |
efiacor | 9c1961e | 2022-12-12 12:07:42 +0000 | [diff] [blame^] | 20 | HV-VES uses direct connection to Kafka. |
Filip Krzywka | 4bb79b7 | 2018-09-25 10:57:17 +0200 | [diff] [blame] | 21 | All these decisions were made in order to support high-volume data with minimal latency. |
| 22 | |
| 23 | |
| 24 | High Volume VES Collector overview and functions |
| 25 | ------------------------------------------------ |
| 26 | |
| 27 | .. toctree:: |
| 28 | :maxdepth: 1 |
VENKATESH KUMAR | e21c848 | 2020-11-12 15:00:02 -0500 | [diff] [blame] | 29 | |
kjaniak | e284409 | 2018-11-14 15:42:03 +0100 | [diff] [blame] | 30 | architecture |
| 31 | design |
kjaniak | e284409 | 2018-11-14 15:42:03 +0100 | [diff] [blame] | 32 | repositories |
| 33 | deployment |
Tomasz Wrobel | 4c94b38 | 2021-10-18 14:16:14 +0200 | [diff] [blame] | 34 | installation-helm |
Filip Krzywka | 12acf3e | 2019-03-19 15:53:15 +0100 | [diff] [blame] | 35 | run-time-configuration |
kjaniak | e284409 | 2018-11-14 15:42:03 +0100 | [diff] [blame] | 36 | HV-VES Offered APIs <../../apis/ves-hv/index> |
| 37 | authorization |
| 38 | example-event |
kjaniak | 8b1223d | 2018-12-19 22:41:40 +0100 | [diff] [blame] | 39 | healthcheck-and-monitoring |
Filip Krzywka | 12acf3e | 2019-03-19 15:53:15 +0100 | [diff] [blame] | 40 | troubleshooting |