5d63e9aff5
We currently do not have a separate billing rate for GitHub runners. Instead, charges are applied for the underlying VM and IPv4 address. We have introduced a new billing rate for GitHub runners, which are x10 less expensive than the default GitHub runner rates. Customers will be billed for individual GitHub runner. I added the location as 'global' because GitHub runner rates do not depend on location; they are uniform across all locations. Currently, we have a separate location for GitHub runners. However, once we eliminate our btrfs requirement, we will no longer need a separate location. Instead, we can provision new runners in the most underutilized location. "VmCores" has a single billing rate for all VM sizes, whereas "GitHubRunnerMinutes" has a unique rate for each size. In the case of "VmCores", we sell "cores", hence "billing_record.amount" corresponds to the number of cores. For "GitHubRunnerMinutes", we sell "minutes", so "billing_record.amount" corresponds to the number of minutes. Different runner sizes have varying costs, resulting in distinct billing rates for each. We bill some records based on the amount, others on duration. For 'VmCores' billing records, the core counts are stored in the amount column and charges are based on duration. For example, 10 minutes of standard-4 vm usage would be calculated as `10 (duration) x 2 (amount) x rate_for_standard_core`. 'GitHubRunnerMinutes' billing records, on the other hand, store used minutes in the amount column and charges are based on this amount. For instance, 10 minutes of standard-4 runner usage would be calculated as `1 (duration) x 10 (amount) x rate_for_standard_4_runner_minute`. 'GitHubRunnerMinutes' is the only category we currently bill by amount, though network costs could potentially be another suitable candidate. At present, we only perform this check for 'GitHubRunnerMinutes'. While a more generic solution may be beneficial, we are waiting to gather more data points before undertaking a more significant refactor.
51 lines
2.3 KiB
Ruby
51 lines
2.3 KiB
Ruby
# frozen_string_literal: true
|
|
|
|
require_relative "../model"
|
|
|
|
class BillingRecord < Sequel::Model
|
|
many_to_one :project
|
|
|
|
dataset_module do
|
|
def active
|
|
where { {Sequel.function(:upper, :span) => nil} }
|
|
end
|
|
end
|
|
|
|
include ResourceMethods
|
|
|
|
def duration(begin_time, end_time)
|
|
# We bill some records based on the amount, others on duration. For
|
|
# 'VmCores' billing records, the core counts are stored in the amount column
|
|
# and charges are based on duration. For example, 10 minutes of standard-4
|
|
# vm usage would be calculated as `10 (duration) x 2 (amount) x rate_for_standard_core`.
|
|
# 'GitHubRunnerMinutes' billing records, on the other hand, store used
|
|
# minutes in the amount column and charges are based on this amount. For
|
|
# instance, 10 minutes of standard-4 runner usage would be calculated as
|
|
# `1 (duration) x 10 (amount) x rate_for_standard_4_runner_minute`.
|
|
# 'GitHubRunnerMinutes' is the only category we currently bill by amount,
|
|
# though network costs could potentially be another suitable candidate. At
|
|
# present, we only perform this check for 'GitHubRunnerMinutes'. While a
|
|
# more generic solution may be beneficial, we are waiting to gather more
|
|
# data points before undertaking a more significant refactor.
|
|
return 1 if billing_rate["resource_type"] == "GitHubRunnerMinutes"
|
|
# begin_time and end_time refers to begin and end of the billing window. Duration of
|
|
# BillingRecord is subjective to the billing window we are querying for. For example
|
|
# if span of the BillingRecord is ['2023-06-15', '2023-08-20'] and billing window is
|
|
# ['2023-06-01', '2023-07-01'], then we are only interested in duration of billing
|
|
# record that was active in June. This is effectively calculating the intersection of
|
|
# two time ranges.
|
|
# One complication comes from the fact billing window might have nil end point if it
|
|
# is still active. We check for that case with span.unbounded_end?.
|
|
duration_begin = [span.begin, begin_time].max
|
|
duration_end = span.unbounded_end? ? end_time : [span.end, end_time].min
|
|
(duration_end - duration_begin) / 60
|
|
end
|
|
|
|
def finalize
|
|
self.class.where(id: id).update(span: Sequel.lit("tstzrange(lower(span), now())"))
|
|
end
|
|
|
|
def billing_rate
|
|
@billing_rate ||= BillingRate.from_id(billing_rate_id)
|
|
end
|
|
end
|