2024-04-15: Update package registry limits for the Ultimate_trial_paid_customer plan
Production Change
Change Summary
We need to update the package registry file size limits for the Ultimate_trial_paid_customer
plan like we did for CI runners here. The values should match the ones for Ultimate
.
See this page (and screenshot below).
Change Details
- Services Impacted - ServiceArtifactRegistry
- Change Technician - @cmcfarland
- Change Reviewer - @devin
- Time tracking - 10 minutes
- Downtime Component - N/A
Set Maintenance Mode in GitLab
If your change involves scheduled maintenance, add a step to set and unset maintenance mode per our runbooks. This will make sure SLA calculations adjust for the maintenance period.
Detailed steps for the change
Steps here may be similar to https://gitlab.com/gitlab-com/gl-infra/production/-/issues/17446.
Change Steps - steps to take to execute the change
Estimated Time to Complete (mins) - 5
-
Set label changein-progress /label ~change::in-progress
-
Access GitLab admin console -
Navigate to Settings > CI/CD
-
Locate the Package Registry
section, click on the "Expand" button -
Locate the Package file size limits
section -
Locate the Ultimate_trial_paid_customer
tab, click on it -
(Optional) Save a backup of the current values in case a rollback is needed -
Fill the limit values with the same values from the Ultimate
tab -
Click on the Save Ultimate_trial_paid_customer size limits
button -
Set label changecomplete /label ~change::complete
Rollback
Rollback steps - steps to be taken in the event of a need to rollback this change
Estimated Time to Complete (mins) - Estimated Time to Complete in Minutes
-
Access GitLab admin console -
Navigate to Settings > CI/CD
-
Locate the Package Registry
section, click on the "Expand" button -
Locate the Package file size limits
section -
Locate the Ultimate_trial_paid_customer
tab, click on it -
Restore the values to what they were before -
Click on the Save Ultimate_trial_paid_customer size limits
button -
Set label changeaborted /label ~change::aborted
Monitoring
Key metrics to observe
I am not aware of any relevant metrics here. The page being updated to the new values should be enough verification.
Change Reviewer checklist
-
Check if the following applies: - The scheduled day and time of execution of the change is appropriate.
- The change plan is technically accurate.
- The change plan includes estimated timing values based on previous testing.
- The change plan includes a viable rollback plan.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
-
Check if the following applies: - The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
- The change plan includes success measures for all steps/milestones during the execution.
- The change adequately minimizes risk within the environment/service.
- The performance implications of executing the change are well-understood and documented.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
- If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
- The change has a primary and secondary SRE with knowledge of the details available during the change window.
- The change window has been agreed with Release Managers in advance of the change. If the change is planned for APAC hours, this issue has an agreed pre-change approval.
- The labels blocks deployments and/or blocks feature-flags are applied as necessary.
Change Technician checklist
-
Check if all items below are complete: - The change plan is technically accurate.
- This Change Issue is linked to the appropriate Issue and/or Epic
- 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.
- The change execution window respects the Production Change Lock periods.
- For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
- For C1 and C2 change issues, the 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.) - For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
- For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
- Release managers have been informed prior to any C1, C2, or blocks deployments change being rolled out. (In #production channel, mention
@release-managers
and this issue and await their acknowledgment.) - There are currently no active incidents that are severity1 or severity2
- If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.
Edited by Cameron McFarland