-
Notifications
You must be signed in to change notification settings - Fork 529
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
[System ready] Report ready state to Sysmonitor daemon #3126
base: master
Are you sure you want to change the base?
Conversation
970b334
to
44dc7c8
Compare
@fastiuk please refer to the comment provided. also please update the PR description of what are you are trying to fix and the scope. if this is a bug to whihc branches it should go? |
44dc7c8
to
0107ebe
Compare
0107ebe
to
455d78c
Compare
Signed-off-by: Yevhen Fastiuk <yfastiuk@nvidia.com>
455d78c
to
91dd091
Compare
@prsunny any more comments? |
/azpw run Azure.sonic-swss |
/AzurePipelines run Azure.sonic-swss |
Azure Pipelines successfully started running 1 pipeline(s). |
/* | ||
* Notify "System ready" feature that we are ok. | ||
*/ | ||
FieldValueTuple app_state("up_status", "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.
There should be some code to set it "false"?
- when orchagent starts
- when orchagent exited gracefully
- when orchagent receive a signal and exited
- etc.
depends-on: sonic-net/sonic-buildimage#18817
What I did
This change implements swss's ability to report it's readines to sysmonitor
Why I did it
The motivation is to report
PortInitDone
to sysmonitor and not just the startup of swssHow I verified it
sysmonitor
Details if related