From 4bb79b722985784e650243248e7450e279485fa9 Mon Sep 17 00:00:00 2001 From: Filip Krzywka Date: Tue, 25 Sep 2018 10:57:17 +0200 Subject: HV-VES main documentation draft Change-Id: I2416a73b703494bdbc8ef35c3608711ea2807018 Issue-ID: DCAEGEN2-831 Signed-off-by: Filip Krzywka --- docs/sections/services/ves-hv/index.rst | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) (limited to 'docs/sections/services/ves-hv/index.rst') diff --git a/docs/sections/services/ves-hv/index.rst b/docs/sections/services/ves-hv/index.rst index 0662660e..483ddbd7 100644 --- a/docs/sections/services/ves-hv/index.rst +++ b/docs/sections/services/ves-hv/index.rst @@ -7,5 +7,29 @@ High Volume VNF Event Streaming (HV-VES) Collector .. Add or remove sections below as appropriate for the platform component. + +**HV-VES collector** has been proposed, based on a need to process high-volumes of data generated frequently by a large +number of NFs. The driving use-case is described and published within presentation during Casablanca Release Developer Forum: +`Google Protocol Buffers versus JSON - 5G RAN use-case - comparison`_. + +.. _`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 + +The goal of the collector is to support high volume data. It uses plain TCP connections. +Connections are stream-based (as opposed to request-based) and long running. +Payload is binary-encoded (currently using Google Protocol Buffers). +HV-VES uses direct connection to DMaaP's Kafka. +All these decisions were made in order to support high-volume data with minimal latency. + + High Volume VES Collector overview and functions +------------------------------------------------ + +.. toctree:: + :maxdepth: 1 + ./design.rst + ./configuration.rst + ./delivery.rst + ./installation.rst + `Offered APIs`_ +.. _`Offered APIs`: ../../apis/ves-hv.rst \ No newline at end of file -- cgit 1.2.3-korg