-
Notifications
You must be signed in to change notification settings - Fork 260
feat: [NPM] define transport shim layer using gRPC #1163
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
feat: [NPM] define transport shim layer using gRPC #1163
Conversation
Signed-off-by: Nitish Malhotra <nitishm@microsoft.com>
|
how are you generating the pb.go? would be nice to define gen targets in the makefile for consistency 🙂 |
Sure I can do that. Are we using it any place else today? I did see a few proto files across the code base. |
@nitishm https://github.com/Azure/azure-container-networking/blob/master/npm/pkg/dataplane/Makefile Check this, Mat has created this MakeFile for auto-generating go mock. You can do something similar. My opinion is this does not have to be in global MakeFile, since we will only generate this once in a while. |
Signed-off-by: Nitish Malhotra <nitishm@microsoft.com>
Signed-off-by: Ubuntu <nitishm@microsoft.com>
a526847 to
ffa077f
Compare
…https://github.com/nitishm/azure-container-networking into nitishm/feat/AB#12707965/transport-event-model-proto
ffa077f to
f414dcd
Compare
|
To test this out use the following instructions: Download the protoc binary Install the grpc go gen tool Run generate target |
vakalapa
left a comment
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.
Approving with minor comments.
Signed-off-by: Ubuntu <nitishm@microsoft.com>
|
@vakalapa can I get another approval. Also any idea why the CI doesn't like it? |
ramiro-gamarra
left a comment
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.
Got curious about this, so I'm leaving a few comments/questions :)
- Implemented the reg and dereg of client on connection establishment and disconnection respectively - Added sample server program to test this out Signed-off-by: Ubuntu <nitishm@microsoft.com>
vakalapa
left a comment
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.
Minor comments, please resolve all lints.
Signed-off-by: Nitish Malhotra <nitishm@microsoft.com>
Signed-off-by: Nitish Malhotra <nitishm@microsoft.com>
Signed-off-by: Nitish Malhotra <nitishm@microsoft.com>
Signed-off-by: Nitish Malhotra <nitishm@microsoft.com>
Signed-off-by: Nitish Malhotra <nitishm@microsoft.com>
- Move all proto files to npm/pkg/protos - Rename pod and node fields to pod_name and node_name in transport.proto Signed-off-by: Nitish Malhotra <nitishm@microsoft.com>
…working into nitishm/feat/AB#12707965/transport-event-model-proto
Signed-off-by: Nitish Malhotra <nitishm@microsoft.com>
5f6d760 to
c65e7c1
Compare
User story AB#12707964
Reason for Change:
Define protobuf message and services for transport shim
Issue Fixed:
AB#12707965
Requirements:
Tasks:
Signed-off-by: Nitish Malhotra nitishm@microsoft.com
Notes: