Re: AWS cleanup - what to delete next?

2024-02-09 Thread Miroslav Suchý

Dne 09. 02. 24 v 18:27 Kevin Fenzi napsal(a):

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/x86_64/images/
Fedora-Cloud-Base-35-1.2 is the GA for fedora 35 cloud.


Nod. I was about to ask how can I find them... but the name match nicely. And going manualy over 35 names is likely not 
big deal.


I will tag them. Then they disappear from my radar.

I propose tag

FedoraGroup=ga-archives

Any objections?


We should exclude all 'current' releases (ie, 38/39/40)


*nod*



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)

*nod*

I am unsure about the CentOS ones. We should check with them on that.
I want to put CentOS aside for now. There is "only" 2k out of 145k that are related to centos. We can work on them in a 
later step.

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?


All operation are reference to AMI are using ami-id. If I change name, likely 
no one will a notice.

But I can do what I did with volumes - first tag it with FedoraGroup=garbage-collector and only then delete it. This can 
lower the human error on my side.


I can rename too. That will be no problem for me, but I would not bet on that 
somebody notice of diferent name.

--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
--
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: AWS cleanup - what to delete next?

2024-02-09 Thread Kevin Fenzi
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/x86_64/images/
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


signature.asc
Description: PGP signature
--
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: HEADS UP - deletion of Fedora Atomic Hosts AMIs

2024-02-09 Thread Dusty Mabe


On 2/7/24 13:39, Miroslav Suchý wrote:
> Dne 09. 12. 23 v 9:21 Miroslav Suchý napsal(a):
>> As mentioned in previous thread - I plan to delete from AWS all Fedora 
>> Atomic Hosts and related snapshots.
>>
>> Atomic Host EOLed at 2019 and we have the images stored elsewhere too.
>>
>> To protect Christmas calm period. I will delete is no sooner than 2024-01-09.
> 
> It took a bit longer, but I finally get to this.
> 
> All AMIs with name 'Fedora-AtomicHost-*' are deleted. It was 12 074 AMIs.

May they rest in peace!

Dusty
--
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue