Closed Bug 1316112 Opened 8 years ago Closed 8 years ago

please deploy balrog 2.13 to stage/prod

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: mostlygeek)

References

Details

Balrog version 2.13 is ready to be pushed to stage. Please deploy the new Docker image (master-2016-11-08-20-17) the admin and public webapps, and the new Docker image for the Agent (master-2016-11-08-20-17).

We'd like the production push for this to happen sometime between 11am and 1pm pacific on Wednesday, November 9th, 2016.

This push requires a schema change that needs to be done _prior_ to the new code going out. That can be performed by running the Docker image with the "upgrade-db" command, with DBURI set. This should result in the creation of a few new tables (user_roles, user_roles_history, rules_scheduled_changes_conditions, and rules_scheduled_changes_conditions_history).

Also of note in this push are https://github.com/mozilla/balrog/pull/170, which bumps Cache-Control to 90s, and bug 1312562, which should fix a high-frequency Traceback we're seeing on Sentry, and reduce load on the public nodes.
Stage database updated and both admin/web have been updated.
Stage looks good, we're ready to deploy after the usual nightly spike of admin requests dies down.
Blocks: 1311827
Deployed to production yesterday.
Appears the new settings have reduced some of the balrog load and the number of servers at peak by about 20% from the previous stack. The effects of adding sentry are still about double the number of servers with sentry disabled.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Blocks: 1317358
You need to log in before you can comment on or make changes to this bug.