Set cost factor for public shared runners to 1
Production Change
Change Summary
We want to set the cost factor for public shared runners to 1
.
We need to execute this code in the rails console:
Ci::Runner.where(runner_type: 1).where(public_projects_minutes_cost_factor: 0.04).update_all(public_projects_minutes_cost_factor: 1)
For more context see the gitlab/gitlab-org
issue: gitlab-org/gitlab#337245 (closed)
Change Details
- Services Impacted - ServiceCI Runners
- Change Technician - @rehab
- Change Reviewer - @allison.browne
- Time tracking - 1m
- Downtime Component - NA
Detailed steps for the change
Change Steps - steps to take to execute the change
Estimated Time to Complete (5 mins) - Estimated Time to Complete in Minutes
-
Set label changein-progress /label ~change::in-progress
-
Run the rails console for production rails -
execute Ci::Runner.where(runner_type: 1).where(public_projects_minutes_cost_factor: 0.04).count
to check how many rows will be updated. -
execute Ci::Runner.where(runner_type: 1).where(public_projects_minutes_cost_factor: 0.04).update_all(public_projects_minutes_cost_factor: 1)
- This should take less then a second to execute
-
execute Ci::Runner.where(runner_type: 1).where(public_projects_minutes_cost_factor: 1).count
to check the change -
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 (5 mins) - Estimated Time to Complete in Minutes
-
Ensure logged into the Production Rails console+} -
execute Ci::Runner.where(runner_type: 1).where(public_projects_minutes_cost_factor: 1).update_all(public_projects_minutes_cost_factor: 0.04)
-
Set label changeaborted /label ~change::aborted
Monitoring
Key metrics to observe
We should see an uptick in cost factor of .04 here
https://log.gprd.gitlab.net/goto/80fac3c0-2000-11ed-8656-f5f2137823ba https://log.gprd.gitlab.net/goto/62251df0-06cf-11ed-8656-f5f2137823ba
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 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 (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 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 Rehab