2024-09-03 Reset monthly minutes

Production Change

Change Summary

{+ We need to reset the monthly minutes due to incident #18489 (closed). +}

Change Details

  1. Services Impacted - ServiceCI Runners
  2. Change Technician - @ayeung
  3. Change Reviewer - @allison.browne
  4. Time tracking -
  5. 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

Run this script:

# reset all usage for september
first_id = 26660842
last_id = Ci::Minutes::NamespaceMonthlyUsage.last.id
batch_size = 100
expected_batches = (last_id - first_id) / batch_size
puts "expected at least #{expected_batches} batches"
batch_numb = 1

Ci::Minutes::NamespaceMonthlyUsage
.where("ci_namespace_monthly_usages.id >= #{first_id} and amount_used > 0")
.in_batches(of: batch_size) do |batch|
  batch.includes(:namespace).each do |usage|
    next unless usage.namespace

      begin
        Ci::Minutes::ResetUsageService.new(usage.namespace).execute
        puts "Reset for #{usage.namespace.id} completed"
      rescue => e
        puts "Error resetting usage for #{usage.namespace.id}: #{e.message}"
      end  
  end

  puts "batch #{batch_numb} completed"
  batch_numb += 1
end

This script can be retried multiple times as it is idempotent.

Change Steps - steps to take to execute the change

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

  • Set label changein-progress /label ~change::in-progress
  • check the amount of minutes used for the month: Ci::Minutes::NamespaceMonthlyUsage.current_month.sum(:amount_used)
  • Run the above script
  • check the amount of minutes used for the month: Ci::Minutes::NamespaceMonthlyUsage.current_month.sum(:amount_used) it should be close to 0
  • Set label changecomplete /label ~change::complete

Rollback

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

We can't easily roll this change back without first creating a snapshot of the Ci::Minutes::NamespaceMonthlyUsage table.

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

Monitoring

Key metrics to observe

Ci::Minutes::NamespaceMonthlyUsage.current_month.sum(:amount_used)

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

Change Reviewer checklist

C4 C3 C2 C1:

  • 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.

C2 C1:

  • 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 Adeline Yeung