If use GRPC not TCP/UDP, that will have standard function, you will not need to write “DECODE_FN_MAP…”, function will auto generate, direct to use. Simple list steps:
[root@telemetry grpc-dailout]# ls -l
total 36
-rw-r--r--. 1 root root 2695 Aug 10 16:16 cisco_grpc_dialout_pb2_grpc.py #Contains the server Stub class and the client Stub class, as well as the service RPC interface to be implemented.
-rw-r--r--. 1 root root 3805 Aug 10 16:16 cisco_grpc_dialout_pb2.py #message serialization classes
-rw-r--r--. 1 root root 484 Aug 10 15:36 mdt_grpc_dialout.proto
-rw-r--r--. 1 root root 3722 Aug 10 16:11 service_grpc_dialout_no_tls.py #service python
-rw-r--r--. 1 root root 19220 Aug 10 15:58 telemetry_pb2.py #decode gpb-kv messages, generate as below
At some times, we only have a qcow2 image, but ESXI(vCenter) only supports vmdk, how to do deploy? In the video guide, I will show how to convert img to vmdk from qcow2, then deploy by import exist hardware(vmdk).
Btw, xrv9k supports only 3 virtual interfaces: e1000, virtio, and VMXnet3. Please notices not support e1000e!