1601530 - Tag EBS volumes like we do for EC2 instances

Status: NEW

(Taskcluster :: Workers, task)

Description

[Chris Cooper [:coop] (he/him)]

Trink's been heroically digging through our cost data. Today he let me know that our EBS storage accounts for up to 20% of our cost, yet it is hard to tie back to instances, projects, or anything (really) because we don't tag EBS volumes at all.

We should fix that.

We should also make this a general fix so that it applies equally in GCP, Azure, and wherever else we run things.

Where do we tag instances right now? Maybe monopacker is the right place for this?

Comment 1

[Miles Crabill [:miles]]

Bug 1627116 covers this work specifically for AWS, so I'll update that as well.

I've created a PR here [0] for this functionality in aws-provider, which will make all AWS provider workers tag their EBS volumes with the same tags as their EC2 instances.

[0] https://github.com/taskcluster/taskcluster/pull/2688

Comment 2

[Miles Crabill [:miles]]

In response to the description, cloud instances are requested and tagged by the worker-manager cloud specific providers, so tagging at instance creation time makes sense.

Monopacker creates volumes / disks / images in each cloud, those images should also be tagged for accounting but make up considerably less spend. In AWS, AMIs are tagged with a name, but we do not currently tag the snapshot and volume in an easy to recognize fashion. I've created bug 1631119 to track this work for monopacker.