-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
gNOI HLD for OS, reboot, File, Reset services #1762
base: master
Are you sure you want to change the base?
Conversation
Adding @vvolam @lguohan @qiluo-msft and @hdwhdw for review. Thanks! |
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.
Maybe consider separating different services (OS, System, File, ....) into different HLDs. It is a bit difficult to keep track of what we have already done/implemented inside each service already and what is added inside these services.
|
||
a. Set the version field of the ActivateRequest message to be the same as the version specified in the TransferRequest message above. | ||
|
||
b. Set the no_reboot flag to true. |
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.
Is this a server-side requirement (so as the standby_supervisor)? I am all for this but we should probably document, so client don't make unsupported rpc calls.
* Verify the standby supervisor version. | ||
* Expect that the VerifyResponse.verify_standby has the same version in messages above. | ||
|
||
Configuration push verification post OS update. |
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.
Should this be a subtiltle?
|
||
## Scope | ||
|
||
This document describes the high level design of adding the capability to support gNOI APIs for OS, Reboot, File, Factory Reset services in the telemetry server. |
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 we be a bit more specific about what RPC exactly (maybe make a list) that we implement? For example, OS has three RPCs but Reboot is a RPC under System service, so it doesn't make that much sense to put them side by side.
No description provided.