On Thu, Feb 08, 2024 at 05:09:27PM +0100, Miroslav Suchý wrote:
Yesterday I finally deleted all Fedora-AtomicHost AMIs and associated
snapshots (it took whole night to finish).
This time, I know we have to start with AMIs first (and only then delete snapshots).
Where I can continue witht the cleanup? There is several dozen thousand of
AMIs. At the end of this email I will give random sample from the list.
I am very afraid of deleting something that is still currently in use and that is
somewhere listed as golden image.
Or we do not care about anything but images of stable Fedoras and everything
that matches 'Fedora.*-X-.*' where X is number bellow < 38?
So... my take:
I think we should leave "GA" images. Even thought they are EOL for the
most part, I think it's still possibly nice to be able to spin one up to
test something or the like. We can find the names on our download
server, ie,
https://dl.fedoraproject.org/pub/archive/fedora/linux/releases/35/Cloud/x...
Fedora-Cloud-Base-35-1.2 is the GA for fedora 35 cloud.
We should exclude all 'current' releases (ie, 38/39/40)
We should exclude "Rawhide" ones that are 2024? I don't think we need to
keep all the old ones there. We have them koji if we really need them.
(At least the last month or two)
Perhaps for the coreos ones use similar rules? Dusty?
I am unsure about the CentOS ones. We should check with them on that.
Would it be worth it to rename the ones we plan to delete with a 'about
to delete' name, wait a while and then delete? Or is there any way to
tell who/how many people are using a ami?
kevin