Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira
serverONAP Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-433

VES-HV Collector

...

(Option 1)

HV-VES collector has been proposed, based on a need to process high-volumes of data generated frequently by a large number of NFs.  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). 

...

  • Added dependency on HV-VES DCAE components

Kafka Interfacing using DMaaP client

...

(Option 2)

Message router is added as an additional layer on top of DMaaP to support message service API interaction with the ZooKeeper/Kafka. DmaapClient is a deliverable jar that can be used to interact with the DMaaP message Router api.

...

  • Additional overhead as an additional layer Message Router would be added between CPS and Kafka. 

Kafka Direct interface without using DMaaP client: To be used in CPS (Option 3)

Pros:

  • No additional layer used between CPS and DMaaP Kafka. 
  • Spring boot enables easier configuration.
  • CPS can make a direct interface with Kafka using spring-kafka. Spring-kafka used in CPS also provides support for Message-driven POJOs for publishing and subscribing events. CPS does not require message service API for interacting with Kafka.

...


Note: AAF integration is not included in this documentation as there is already a Jira to handle the integration 
CPS-281 which is still under discussion.



draw.io Diagram
bordertrue
diagramNameUntitled Diagram
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth1281
revision4