-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support proto encoding for DASH_VNET_ROUTE #7
base: bluefield
Are you sure you want to change the base?
Conversation
string underlay_ip = 8; | ||
string overlay_sip = 9; | ||
string overlay_dip = 10; | ||
string metering_bucket = 11; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this put a dependency on schema changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, you are right.
This PR is a POC, if we want to support protobuf encoding with sonic db schema, then we have to manually create proto definition.
And we can support protobuf encoding with sonic yang schema in the future, because ygot can translate yang models to proto format.
Vnet string `protobuf:"bytes,5,opt,name=vnet,proto3" json:"vnet,omitempty"` | ||
CustomerAddr string `protobuf:"bytes,6,opt,name=customer_addr,json=customerAddr,proto3" json:"customer_addr,omitempty"` | ||
Appliance string `protobuf:"bytes,7,opt,name=appliance,proto3" json:"appliance,omitempty"` | ||
UnderlayIp string `protobuf:"bytes,8,opt,name=underlay_ip,json=underlayIp,proto3" json:"underlay_ip,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be IP address instead of string?
Why I did it Update telemetry container to support new gnmi config interface. How I did it Use new target to support mixed schema, and we can enable/disable telemetry and gnmi config interface. How to verify it Build target and run unit test.
Why I did it
Json deserialization performance is poor, and DASH_VNET_ROUTE needs better performance.
How I did it
Update gnmi server and client to support proto encoding for DASH_VNET_ROUTE.
How to verify it
Run unit test.
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)