https://bugzilla.wikimedia.org/show_bug.cgi?id=47393
Web browser: ---
Bug ID: 47393
Summary: git-deploy should allow separate restarts
Product: Wikimedia
Version: wmf-deployment
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: Unprioritized
Component: git-deploy
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Classification: Unclassified
Mobile Platform: ---
Currently, git-deploy automatically restarts the service after every
deployment. For Parsoid, this is kind of evil, for two reasons.
First, we have two repositories, one for the code and one for the config. If we
make dependent changes to these, deploying one of them will break the service,
and deploying the second one will fix it again. When doing a deployment like
this, we'd want to deploy both, then restart the service.
Second, even when only deploying one repo, it's generally desirable to test the
change on one backend first. So it would be nice if we could deploy the change,
restart one backend, sanity-test it, and then restart the rest of the cluster
if it's fine. With the way things work currently, deploying broken code will
instantly break the entire cluster.
So I'd like git-deploy to have a restart operation that restarts a service,
either on the entire cluster or on one specific minion (this is needed to
restart one backend for testing, because deployers don't necessarily have
root), and for the restart-on-deploy behavior to be disableable.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
