blablacar / ggn

Link container builds with envs to end up into low level orchestration
35 stars 9 forks source link

Add a hard timeout for each service update #56

Open sinfomicien opened 8 years ago

sinfomicien commented 8 years ago

As of today, if a server is declared in Fleet Cluster, but is in an unknown network state... You have to wait for at least 30 minutes before getting that something is wrong. Would be better to put a 'hard timeout' on the update. If the update is not finished after the timeout, cancel everything, and go to the next update.