FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
In this step I plan to keep the associated snapshots. So if I break something we can still restore the AMI.
BTW - quick summary where we are with the cleanup stuff:
* all VM, volumes have tag FedoraGroup
* all gp2 volumes are migrated to gp3
* All AMIs with name 'Fedora-AtomicHost-*' are deleted. Including associated snapshots
* all Fedora GA AMIs and snapshots are tagged with FedoraGroup.
* all old (2021-) snapshots with no associated AMIs are deleted.
On Thu, Mar 14, 2024 at 09:58:47AM +0100, Miroslav Suchý wrote:
FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
Sure, but note that freeze is only over once we ship a beta. ;)
But I don't knot that this needs to wait on that. It seems pretty safe.
In this step I plan to keep the associated snapshots. So if I break something we can still restore the AMI.
BTW - quick summary where we are with the cleanup stuff:
all VM, volumes have tag FedoraGroup
all gp2 volumes are migrated to gp3
All AMIs with name 'Fedora-AtomicHost-*' are deleted. Including associated snapshots
all Fedora GA AMIs and snapshots are tagged with FedoraGroup.
all old (2021-) snapshots with no associated AMIs are deleted.
Thanks again for moving this forward.
kevin
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deleted all AMIs that does not have tag FedoraGroup and that were older than 2019-01-01.
For the record, the list of deleted AMIs is in attachement. And the script that I used is https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered 36996 AMIs. The associated snapshots still exists.
On Tue, Apr 02, 2024 at 07:13:56AM +0200, Miroslav Suchý wrote:
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deleted all AMIs that does not have tag FedoraGroup and that were older than 2019-01-01.
For the record, the list of deleted AMIs is in attachement. And the script that I used is https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered 36996 AMIs. The associated snapshots still exists.
Hurray!
Thanks again for doing this.
kevin
Dne 02. 04. 24 v 7:45 odp. Kevin Fenzi napsal(a):
On Tue, Apr 02, 2024 at 07:13:56AM +0200, Miroslav Suchý wrote:
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deleted all AMIs that does not have tag FedoraGroup and that were older than 2019-01-01.
For the record, the list of deleted AMIs is in attachement. And the script that I used is https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered 36996 AMIs. The associated snapshots still exists.
Hurray!
Thanks again for doing this.
You are welcome. But I have to say I am scared. I just ask myself: and centos AMIs are stored under which account?
Our account, is the answer!
So, I have just tagged all AMIs from
https://www.centos.org/download/aws-images/
with FedoraGroup=ga-archives
Any idea if I missed something else before I start deleting the more recent ones?
On Tue, Apr 02, 2024 at 09:39:46PM +0200, Miroslav Suchý wrote:
Dne 02. 04. 24 v 7:45 odp. Kevin Fenzi napsal(a):
On Tue, Apr 02, 2024 at 07:13:56AM +0200, Miroslav Suchý wrote:
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
FYI I plan to continue in AWS cleanup on Friday.
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deleted all AMIs that does not have tag FedoraGroup and that were older than 2019-01-01.
For the record, the list of deleted AMIs is in attachement. And the script that I used is https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered 36996 AMIs. The associated snapshots still exists.
Hurray!
Thanks again for doing this.
You are welcome. But I have to say I am scared. I just ask myself: and centos AMIs are stored under which account?
Our account, is the answer!
Yep. ;(
It is scary, but it should be done...
So, I have just tagged all AMIs from
https://www.centos.org/download/aws-images/
with FedoraGroup=ga-archives
ok.
I suspect there's a lot fewer of them than the fedora ones?
Any idea if I missed something else before I start deleting the more recent ones?
I don't think so...
kevin
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deregister all AMIs without FedoraGroup tag that are older than 2020-01-01. This was in all regions. Snapshots are still there.
I used script:
https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered more than 8k AMIs (now tell me what I broke)
The full log is here (well almost full as I forgot to log it at the beggining so few hundreds of lines are lost)
On Thu, Jun 20, 2024 at 01:55:29PM GMT, Miroslav Suchý wrote:
Dne 14. 03. 24 v 9:58 dop. Miroslav Suchý napsal(a):
I waited till Freeze is over - just to be safe. And now I want to delete the old AMIs. Likely in several waves. Going from oldest to ~2021.
I deregister all AMIs without FedoraGroup tag that are older than 2020-01-01. This was in all regions. Snapshots are still there.
I used script:
https://github.com/xsuchy/fedora-infra-scripts/blob/main/delete-old-amis.py
The script deregistered more than 8k AMIs (now tell me what I broke)
The full log is here (well almost full as I forgot to log it at the beggining so few hundreds of lines are lost)
Thanks!
Nothing so far broken I know of.
kevin
Dne 20. 06. 24 v 1:55 odp. Miroslav Suchý napsal(a):
I deregister all AMIs without FedoraGroup tag that are older than 2020-01-01. This was in all regions. Snapshots are still there.
I continued with all older than 2021-01-01.
1240 AMis deregistered.
The log is here: https://k00.fr/n2tx12di
Dne 26. 06. 24 v 11:43 odp. Miroslav Suchý napsal(a):
I deregister all AMIs without FedoraGroup tag that are older than 2020-01-01. This was in all regions. Snapshots are still there.
I continued with all older than 2021-01-01.
I continued with all older than 2022-01-01.
797 AMIs deregistered.
The log is here: https://k00.fr/a5oqhiho
FYI - My next intent. Do one more run for AMIs older than 2023 in few days. Then I will pause (because PTOs. In August start deleting snapshots that were left behind AMIs. And in September continue with deleting most recent AMIs.
On Sun, Jun 30, 2024 at 06:52:53PM GMT, Miroslav Suchý wrote:
Dne 26. 06. 24 v 11:43 odp. Miroslav Suchý napsal(a):
I deregister all AMIs without FedoraGroup tag that are older than 2020-01-01. This was in all regions. Snapshots are still there.
I continued with all older than 2021-01-01.
I continued with all older than 2022-01-01.
797 AMIs deregistered.
The log is here: https://k00.fr/a5oqhiho
FYI - My next intent. Do one more run for AMIs older than 2023 in few days. Then I will pause (because PTOs. In August start deleting snapshots that were left behind AMIs. And in September continue with deleting most recent AMIs.
ok. Sounds good!
kevin
Dne 30. 06. 24 v 6:52 odp. Miroslav Suchý napsal(a):
I continued with all older than 2022-01-01
I continued with all older than 2023-01-01.
1014 AMIs deregistered.
The log is here: https://k00.fr/opdxkbs9
4283 AMI without tag remains. I see on the list AMIs like:
* CPE RHEL 9.1 * CentOS Stream 9x86_64 20240624 * CentOS Stream 8 aarch64 20240429 * Fedora-Cloud-Base-39_Beta-1.1.aarch64-hvm-us-east-2-gp3-0 * Fedora-Cloud-Base-AmazonEC2.x86_64-40-20240622.0-hvm-us-east-2-gp3-0 * fedora-coreos-40.20240301.92.0-x86_64
Full list is here: https://k00.fr/5z8vge8p
If any of these is yours, please tag it with FedoraGroup otherwise it will be deleted at the end of summer.
On 02/07/2024 08:59, Miroslav Suchý wrote:
Dne 30. 06. 24 v 6:52 odp. Miroslav Suchý napsal(a):
I continued with all older than 2022-01-01
I continued with all older than 2023-01-01.
1014 AMIs deregistered.
The log is here: https://k00.fr/opdxkbs9
4283 AMI without tag remains. I see on the list AMIs like:
- CPE RHEL 9.1
I'll take care of these ones
- CentOS Stream 9x86_64 20240624
- CentOS Stream 8 aarch64 20240429
For CentOS Stream, it would have been a good idea to ask them to tag properly , as I don't think they read the Fedora infra list. So I just played MITM and created issue, so that they'll take action : https://issues.redhat.com/browse/CS-2315
Dne 02. 07. 24 v 8:59 dop. Miroslav Suchý napsal(a):
I continued with all older than 2023-01-01.
1014 AMIs deregistered.
I continued with all older than 2023-06-01.
I forgot to keep the full log.
And because no one objected to all these missing AMIs I deleted in past months I also deleted the snapshots. 55 749 snapshots were deleted.
The full log is
infrastructure@lists.fedoraproject.org
-
Fabian Arrotin -
Kevin Fenzi -
Miroslav Suchý