On Thu, Nov 02, 2023 at 10:32:20AM +0100, Miroslav Suchý wrote:
We have (almost) all instances and volumes properly tagged. Now let
check Snapshots.
Thanks for continuing to drive this forward. ;)
OMG - there are A LOT of them. The list has 97k lines! Because of the
size I
will not attach it and instead provide link to download it:
https://k00.fr/8p59mvcw
If you help me to identify something, I can either delete or tag it for you.
Few things I spotted:
* snapshots of volumes that no longer exists. Can it be deleted?
* lots of snapshots like fedora-coreos-36.20221030.2.3-aarch64 - do we still need 36 and
older?
* Fedora-Cloud-Base-29-20190729.0.x86_64-hvm-us-east-1-standard-0 - is this
snapshots used to generate AMIs for getfedora.org? Do we still need it?
If you have snapshots that are important, please check that it have tag FedoraGroup=*
So, if the non coreos ones are mostly fedimg, it doesn't tag things. ;(
It predates our tagging setup entirely...
I've not dug into it, but yeah, I think it uses snapshots to make the
ami's... but it's unclear to me if it does or should clean those up
after the ami is made?
https://github.com/fedora-infra/fedimg/blob/develop/docs/services/ec2.md
I'm not sure how we can tell which of these are fedimg related and wich
aren't. Can we tell when something was created? I guess we could mount
them on a instance and see whats in them, but that doesn't seem
practical for 97k snapshots. ;)
Can we get what volume they are snapshots of? Perhaps the volume name
would help us figure things out?
Open to ideas on how to clean it up.
kevin