-
Notifications
You must be signed in to change notification settings - Fork 119
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
Set lengthier timeout for CVD creation under Docker #476
Conversation
b/317170946 for the context |
frontend/debian/cuttlefish-orchestration.cuttlefish-host_orchestrator.default
Outdated
Show resolved
Hide resolved
The failing test is unrelated to your code, I will update the branch (so that a change with a larger timeout applies) and re-run it, if it fails again just push it bypassing the test. |
frontend/debian/cuttlefish-orchestration.cuttlefish-host_orchestrator.default
Outdated
Show resolved
Hide resolved
frontend/debian/cuttlefish-orchestration.cuttlefish-host_orchestrator.init
Outdated
Show resolved
Hide resolved
@@ -24,6 +24,10 @@ orchestrator_https_port=2443 | |||
# Defaults to "/tmp/<uid>/cvd_artifacts" | |||
orchestrator_cvd_artifacts_dir=/var/lib/cuttlefish-common | |||
# | |||
# Timeout for CVD creation | |||
# Defaults to 7 mins | |||
orchestrator_cvd_creation_timeout=7 |
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 line be uncommented? I think there's a default value in golang code.
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.
Changed to comment and also changed value of the variable.
Running CVD under docker can take much longer time to complete creation. To prevent CVD instance being killed by host orchestrator while booting instance, set lengthier timeout for CVD creation.
…imeout Change docker specific CVD creation timeout configuration to generic CVD with 7 mins default, and change the configuration for docker to 30 mins.
To be more clear for the timeout value of CVD creation, change unit to seconds and specified the unit at names.
Change orchestrator_cvd_creation_timeout_secs to comment and orchestrator will use golang default value for this. This simplifies making custom option for specific environment. Change Dockerfile to use echo command to apply orchestrator_cvd_creation_timeout_secs
Running CVD under docker can take much longer time to complete creation. To prevent CVD instance being killed by host orchestrator while booting instance, set lengthier timeout for CVD creation.