-
Notifications
You must be signed in to change notification settings - Fork 168
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
Add maintenance mode hooks #114
Comments
Thoughts for cnsideration:
End-maintenance is sometimes aborted. For example, the user ctrl-c an On Friday, October 2, 2015, Silvia Botros [email protected] wrote:
|
We can add a timeout for the hook after which orchestrator shows a message that the hook failed, log a more detailed stack as to what line in the script failed. I wouldn't want this to be a blocker to making it clear this server was intended to be in maintenance so marking maintenance mode in orchestrator only is I think ok (at least shows that someone tried.....and it didn't go 100% as planned) yes if the reaping maintenances is defined/configured, it should also run the hooks when the maintenance status is reaped. that way the same channels are utilized. I think it is fair to say that as long as behavior on hook failure is properly documented, people can decide whether the hook should be trivial like chat ops..or more involved like actually calling out to load balancers and making changes there... |
Need to rewrite
Make sure to handle the |
omg this is almost two years old. Might actually do this. |
woohoo! Silvia Botros On August 30, 2016 at 1:05:59 PM, Shlomi Noach ([email protected]) omg this is almost two years old. Might actually do this. — |
flushInstanceWriteBuffer: correct function name in Debugf() message
In the interest of more automation, it would be great if when a server is placed in maintenance mode within orchestrator, to also support a hook there. That way placing a server in maintenance does all the work of notifying a chat room, disabling the server undergoing maintenance in any load balancers and even killing connections if we decide to add that to said hook
The text was updated successfully, but these errors were encountered: