2021-09-17: Deploy MR to prepare for traffic increase to canary during hard PCL

Production Change

Change Summary

We want to deploy a change for shortening the session TTL for anonymous blob access to canary during the ongoing hard PCL to be prepared for a traffic increase in emergency.

Change Details

1. Services Impacted - ServiceWeb
2. Change Technician - @hphilipps
3. Change Reviewer - @marin
4. Time tracking - 60 minutes
5. Downtime Component - none

Detailed steps for the change

Pre-Change Steps - steps to be completed before execution of the change

Estimated Time to Complete (mins) - 5m

• Set label changein-progress on this issue
• get approval
• inform EOC
• make sure there is no current deployer pipeline close to promoting to canary

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 60m

• lock gprd /chatops run deploy lock gprd
• unlock canary /chatops run deploy unlock gprd-cny
• restart the preparation job of the first gprd-cny pipeline containing the MR: https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/pipelines/796724
• lock canary right after the canary deploy finished: /chatops run deploy lock gprd-cny

Post-Change Steps - steps to take to verify the change

Estimated Time to Complete (mins) - Estimated Time to Complete in Minutes

• make sure there is no other pipeline deploying to canary after the change: https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/pipelines

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - 5m

• drain canary: chatops run canary disable --production

Monitoring

Key metrics to observe

• Metric: Metric Name
  • Location: Dashboard URL
  • What changes to this metric should prompt a rollback: Describe Changes

Summary of infrastructure changes

• Does this change introduce new compute instances?
• Does this change re-size any existing compute instances?
• Does this change introduce any additional usage of tooling like Elastic Search, CDNs, Cloudflare, etc?

Summary of the above

Changes checklist

• This issue has a criticality label (e.g. C1, C2, C3, C4) and a change-type label (e.g. changeunscheduled, changescheduled) based on the Change Management Criticalities.
• This issue has the change technician as the assignee.
• Pre-Change, Change, Post-Change, and Rollback steps and have been filled out and reviewed.
• This Change Issue is linked to the appropriate Issue and/or Epic
• Necessary approvals have been completed based on the Change Management Workflow.
• Change has been tested in staging and results noted in a comment on this issue.
• A dry-run has been conducted and results noted in a comment on this issue.
• SRE on-call has been informed prior to change being rolled out. (In #production channel, mention @sre-oncall and this issue and await their acknowledgement.)
• Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
• There are currently no active incidents.