-
Notifications
You must be signed in to change notification settings - Fork 86
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
sonic-host-services changes for gNOI Warm Reboot #191
base: master
Are you sure you want to change the base?
Conversation
e42ae0a
to
76f70db
Compare
host_modules/gnoi_reboot.py
Outdated
|
||
# Timeout for SONiC Host Service to be killed during reboot | ||
REBOOT_TIMEOUT = 260 | ||
|
||
EXECUTE_COLD_REBOOT_COMMAND = "sudo reboot" | ||
EXECUTE_NSF_REBOOT_COMMAND = "/etc/init.d/gpins-nsf-boot nsf-reboot" | ||
EXECUTE_WARM_REBOOT_COMMAND = "/usr/local/bin/warm-reboot -v" |
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.
@hdwhdw @qiluo-msft Can you pls confirm this is the right command to invoke warm reboot in SONiC ?
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.
@github76543 Joh, can you PTAL and signoff. |
a230e6e
to
f71371e
Compare
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 you please look at ff73070 and see if this is something you can reuse?
host_modules/gnoi_reboot.py
Outdated
|
||
# Timeout for SONiC Host Service to be killed during reboot | ||
REBOOT_TIMEOUT = 260 | ||
|
||
EXECUTE_COLD_REBOOT_COMMAND = "sudo reboot" | ||
EXECUTE_NSF_REBOOT_COMMAND = "/etc/init.d/gpins-nsf-boot nsf-reboot" | ||
EXECUTE_WARM_REBOOT_COMMAND = "/usr/local/bin/warm-reboot -v" |
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.
Thanks @hdwhdw for the reference. The reboot dbus service also needs a request/response framework which is what this PR does and IIUC @vvolam went with the other one as a stop gap solution. Adding @github76543 (John) for additional inputs. |
@kishanps thanks for clarifying. If so consider renaming the service to something more general than gnoi_reboot. Maybe 'async_system'? Having one module for each gnoi service can clutter the dbus codebase. Also does it make sense to add your api to systemd service and call it async reboot, alongside @vvolam API? |
f71371e
to
12e3f91
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@hdwhdw @github76543 @rkavitha-hcl @jaanah-hcl I discussed with John, Dawei Huang & @vvolam and we all agree that reboot will be a separate dbus service and hence rename gnoi_reboot to just reboot. And remove the commit id ff73070 alongwith this PR to avoid the duplication. |
12e3f91
to
f568f97
Compare
/azp run |
Pull request contains merge conflicts. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
No description provided.