ReleaseEngineering/How To/Shut off all updates: Difference between revisions

ReleaseEngineering/How To/Shut off all updates (view source)

Revision as of 02:57, 29 March 2016

316 bytes removed , 29 March 2016

Update to 2016 spec

NThomas

Confirmed users

4,293

edits

@@ Line 2: / Line 2: @@
 On occasion we need to shut off all updates for all products/branches. This could happen because of a disastrous update scenario, a downtime, or some other unforeseen reason.
-Currently our updates are split across two different systems (AUS3 and Balrog), so we need to make changes to both of those systems to do this:
+= Shutting off updates =
-= Shutting off updates in AUS3 =
+* Go to [https://aus4-admin.mozilla.org/rules the Balrog Admin interface's rules page], VPN is required.
-* Log on to aus3-staging via ssh (you should be able to log in with your own LDAP account)
+* Find the rule with "Global shut off" in its "Comment" field. Change its priority to "10000" and click its "Update" button. Double check that the priority is the highest, so that it overrides all other rules
-* Run the following:
- sudo su -
- chmod 700 /opt/aus2/incoming
 == Re-enabling ==
-Run the following:
+* Go to [https://aus4-admin.mozilla.org/rules the Balrog Admin interface's rules page].
- chmod 755 /opt/aus2/incoming
+* Find the rule with "Global shut off" in its "Comment" field. Change its priority to "1" and click the "Update" button.
-= Shutting off updates in Balrog =
-* Go to [https://aus4-admin.mozilla.org/rules.html the Balrog Admin interface's rules page].
-* Find the rule with "Global shut off" in its "Comment" field. Change its priority to "100" and click its "Update" button.
-== Re-enabling ==
-* Go to [https://aus4-admin.mozilla.org/rules.html the Balrog Admin interface's rules page].
-* Find the rule with "Global shut off" in its "Comment" field. Change its priority to "1" and click its "Update" button.