-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Binary pack script opt #4010
Binary pack script opt #4010
Conversation
will manually test when I got bandwidth to, plz don't review now. |
for daemon in ${daemons[@]} | ||
do | ||
if [[ ! -f $install_dir/scripts/nebula.service ]] ; then | ||
$install_dir/scripts/nebula.service stop ${daemon} |
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.
This operation can be dangerous in a production environment. I suggest that we do not do this implicitly.
@@ -141,6 +141,8 @@ function start_daemon { | |||
local command="${executable} --flagfile ${config}" | |||
INFO "Starting ${daemon_name}..." | |||
eval ${command} | |||
local port=$(get_port_from_config ${config}) | |||
wait_for_port_listening ${port} 20 || WARN "Timed out waiting for ${daemon_name} to finish starting, but it may still be running" |
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.
prefer to implement this logic in nebula process.
and the behavior should be same with running in container.
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.
or just like readinessprobe in k8s, curl a http interface?
this will be revisited later when I have bandwidth to think about it. |
closing it for now |
What type of PR is this?
What problem(s) does this PR solve?
Issue(s) number:
close #4003
close #4009
Description:
How do you solve it?
Special notes for your reviewer, ex. impact of this fix, design document, etc:
Checklist:
Tests:
Affects:
Release notes:
Please confirm whether to be reflected in release notes and how to describe: