Status

Release Engineering
General
RESOLVED FIXED
4 years ago
13 days ago

People

(Reporter: catlee, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
We need to present our ongoing cost on the KPI dashboard.

Let's focus on AWS cost initially, and report this both as gross cost, as cost per push, and cost per CPU-hour ran on AWS.

Comment 1

4 years ago
IIRC kmoir did some work on cost-per-push earlier in the year.

Comment 2

4 years ago
(In reply to Chris Cooper [:coop] from comment #1)
> IIRC kmoir did some work on cost-per-push earlier in the year.

If nothing else, kmoir also gathers the monthly push stats. Even getting that automated as part of the dashboard would be a win.

Comment 3

4 years ago
I look at the number of pushes per month when I write the monthly blogpost.  On our internal docs, I take the AWS bill and divide by #pushes to get a cost per push. This is not accurate because it doesn't include the costs for our on premise infrastructure.  I agree that having this automatically generated would be a win because now it takes me about 1hr to do.  But it has not been a priority to automate.  fyi, here's the current process

https://wiki.mozilla.org/User:Armenzg/Data

Comment 4

4 years ago
(In reply to Kim Moir [:kmoir] from comment #3)
> I look at the number of pushes per month when I write the monthly blogpost. 
> On our internal docs, I take the AWS bill and divide by #pushes to get a
> cost per push. This is not accurate because it doesn't include the costs for
> our on premise infrastructure.  I agree that having this automatically
> generated would be a win because now it takes me about 1hr to do.  But it
> has not been a priority to automate.  fyi, here's the current process
> 
> https://wiki.mozilla.org/User:Armenzg/Data

We're not looking at anything more sophisticated for the first pass. A static cost that can be filled in with data taken directly from Amazon in the future will suffice.
(Reporter)

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Assignee)

Updated

13 days ago
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.