Manoj:

We are trying to go slow. We have not finalized on the protocol to use. We can 
certainly consider using GPB. I have forwarded your email to my architects for 
their input. I will keep you updated. BTW we also have a JAVA library 
completed. It will take some time to show up in ONAP gerrit (need to go through 
 the process),  but you can pick it up from our github: 
https://github.com/att/evel-library/files/1145800/VESJavaLibrary.tar.gz


Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com<mailto:ag1...@att.com>

From: Manoj K Nair [mailto:manoj.k.n...@netcracker.com]
Sent: Friday, July 14, 2017 5:01 AM
To: GUPTA, ALOK <ag1...@att.com>
Cc: onap-discuss@lists.onap.org
Subject: [dcae] Google Protocol Buffer support for VES

Hi Alok,

We reviewed the VES specification you shared after the presentation in DCAE 
weekly meeting couple of weeks back.  We understand that currently VES supports 
a REST based interface with JSON payload to push telemetry data and events from 
the VNF to DCAE VES collector. For telemetry control an HTTP response channel 
is being used as per the test code link you published in the presentation.

Just wondering if GPB is considered as one of potential options for VES.  You 
have noted the use of Avro as one potential option as future enhancement. 
Wondering if GPB is also a potential option you are considering. Some of the 
advantages we see for GPB are.
•        Uses binary formatting during serialization, which densily packs the 
payload (which is good for PM/telemetry data)
•        Faster than the VES proposed JSON payload (which is good for events 
and alarms)
•        Can define the structure (schema) of events/telemetry data in a 
protocol definition file (.proto) which is similar to the JSON schema that is 
available in OPNFV VES project
•        Availability of code generators in multiple programming languages for 
encoding and decoding - Can generate code in C#, C++,  Java, Python, Go . 
Options in other languages available as well.

While we have noted the dynamic schema capabilities in Avro, one key advantage 
we see with GPB is the serialization code generation in multiple languages 
without limiting to the C language based library which is currently available 
and open source tool sets available for GPB. Moreover many network vendors and 
open source monitoring solutions (e.g. Prometheus, 
link<https://urldefense.proofpoint.com/v2/url?u=https-3A__prometheus.io_docs_instrumenting_exposition-5Fformats_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=iccs1VIxoa5SRlt4QotAwA&m=XXhoW1oGu9w5ICuKXVTHEoj6jTy7JFzclXWnliVMEq4&s=-ZxUYr0a4WhAPcklP8EeMp8ah8uMFbczyPm-vlo9--0&e=>)
   support GPB already. We would be glad to share more information on the 
potential GPB usage if required.

Regards

Manoj
[cid:image002.png@01D2FC7C.E35B2030][https://www.netcracker.com/assets/img/netcracker-social-final.png]ƕ



________________________________
The information transmitted herein is intended only for the person or entity to 
which it is addressed and may contain confidential, proprietary and/or 
privileged material. Any review, retransmission, dissemination or other use of, 
or taking of any action in reliance upon, this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and delete the material from any computer.
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to