Dne 01. 04. 23 v 20:27 Kevin Fenzi napsal(a):
Should we stop uploading 'standard' and 'gp2'? I mean, is there any
reason anyone would want to use one of those? I find it just confusing
that there's multiple types for each image. If we can, I'd say we should
just do gp3?
standard is magnetic
Dne 04. 04. 23 v 23:50 Kevin Fenzi napsal(a):
I'm still unsure if that means we only do gp3 or what is the list of
ones we do after this change?
Depends on your use case. For Copr we use gp3 for all volumes but - copr-dist-git (5TB) and copr-be data volume where we
store dnf repositories
Dne 05. 04. 23 v 19:24 Kevin Fenzi napsal(a):
Currenly we upload 'standard' and 'gp2'.
I failed to find what "standard" means. Likely one of the magnetic ones, but
don't know which one.
Should we do 'standard' and 'gp3'? or 'sc1' and 'gp3'?
Yes.
I guess thats really for the cloud sig to
I was going through our spending in AWS and I found that we spent a lot in Sydney region (?). In details most of the
bill there is because of stored snapshots. There is 7508 of them dated to back to 2013. For volumes that does not exists
any more.
The only instances (and volumes) we have in
Dne 13. 07. 23 v 0:26 Dusty Mabe napsal(a):
If you say it's an issue then hopefully we can give this some priority and get
to it soon.
Removing the "old ones" isn't that easy to do. Our production AMIs and
development AMIs are all mixed together so it would be hard to come up with a criteria
Dne 11. 07. 23 v 15:53 Dusty Mabe napsal(a):
Apologies for not responding sooner. Actually for some reason this is the first
email I've seen
in the thread so maybe I need to check my spam filters. Either way, apologies.
The reason you are seeing snapshots but no volumes is because these
Dne 05. 07. 23 v 21:17 Kevin Fenzi napsal(a):
On Mon, Jul 03, 2023 at 04:02:02PM +0200, Fabian Arrotin wrote:
On 03/07/2023 06:39, Miroslav Suchý wrote:
I was going through our spending in AWS and I found that we spent a lot
in Sydney region (?). In details most of the bill there is because
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
Dne 08. 02. 24 v 17:09 Miroslav Suchý napsal(a):
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.
For the record, here is complete list containing 150k lines [9MB]
https://k00.fr/s7xl2itj
This is a resource from AWS that does not have propper tag:
Region: eu-west-1
Volumes - [id name (attached to instance, owner)]:
* vol-0e5efafe67ed944ad N/A (apps-containerization, N/A)
Can the owner please tag (or delete) it?
--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno,
Dne 09. 02. 24 v 20:34 Miroslav Suchý 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,
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
I was wondering why I cannot tag some images in AWS and I found that some GA
images in AWS have different owner.
I.e. all our images has
Owner account ID 125523088429
But e.g. ami-0e4e634d022c1a3f8 in ap-southeast-4 region has owner id 569228561889. There are more such cases, but it
seems
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,
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.
--
Miroslav Suchy, RHCA
Red Hat,
Here comes December edition of resources running in AWS. It's a snapshot of
resources running today.
FedoraGroup: infra
Region: ap-south-1
Instance Type: c5d.xlarge - Count: 1
Volume Type: gp3 - Total Size: 8 GiB
Region: eu-central-1
Instance Type: c5d.xlarge - Count: 1
HEADS UP
On Friday I plan to delete all Snapshots that were created before 2019 and do
not have tag FedoraGroup.
On next Friday (2023-12-01) I plan to delete all Snapshots that were created in 2021 and earlier and do not have tag
Fedora Group.
This will be done in all regions.
As mentioned
Dne 28. 11. 23 v 23:28 Sandro napsal(a):
On 28-11-2023 15:54, Miroslav Suchý wrote:
On Friday I plan to delete all Snapshots that were created before 2019 and do
not have tag FedoraGroup.
On next Friday (2023-12-01) I plan to delete all Snapshots that were created in 2021 and earlier and do
Dne 09. 11. 23 v 20:39 Kevin Fenzi napsal(a):
Well, actually, we should probibly check in on the thing thats cleaning
up the amis? and confirm that it is deleting the snapshots?
I think that is this:
roles/fedimg/templates/clean-amis.py
in ansible.
and it does delete the snapshot... so,
Here comes November edition of resources running in AWS. It's a snapshot of
resources running today.
FedoraGroup: respins
Region: us-east-1
Volume Type: gp3 - Total Size: 500 GiB
FedoraGroup: ci
Region: us-east-1
Instance Type: c5.2xlarge - Count: 3
Volume Type: gp3 -
Dne 29. 11. 23 v 8:36 Miroslav Suchý napsal(a):
On Friday (2023-12-01) I plan to delete all Snapshots that were created before
2019 and do not have tag FedoraGroup.
On next Friday (2023-12-08) I plan to delete all Snapshots that were created in 2021 and earlier and do not have tag
Fedora
Dne 29. 11. 23 v 8:36 Miroslav Suchý napsal(a):
On Friday (2023-12-01) I plan to delete all Snapshots that were created before
2019 and do not have tag FedoraGroup.
This phase has finished. Any snapshot older than 2019 that remained is because AWS refused to delete it - likely because
Dne 02. 12. 23 v 22:45 Miroslav Suchý napsal(a):
I wonder - do we have written retention policy for our images? Do we want to keep the old one? Public ones? Private ones?
It seems that Fedora Atomic Host is EOLed since 2019-11-26
https://projectatomic.io/blog/2019/11/fedora-atomic-host
Here comes January edition of resources running in AWS. It's a snapshot of
resources running today.
FedoraGroup: garbage-collector
Region: ap-southeast-1
Volume Type: standard - Total Size: 6 GiB
FedoraGroup: min
Region: eu-central-1
Instance Type: t3.2xlarge - Count: 1
During the autumn cleanup I deleted several abandoned instances and volumes. I made a snapshot of each such volume and
tagged it with FedoraGroup=garbage-collector and then deleted these volumes. So far no one objected that he is missing
something. I plan to delete these snapshots with
Dne 23. 04. 24 v 3:31 odp. Dusty Mabe napsal(a):
If you don't mind give us until next week to finish up loose ends on this. We
are already
adding the FedoraGroup=coreos tag to our snapshots/AMIs as we create them now,
but we are
working on a script to go apply that tag to our existing images.
This is without AMIs and Snapshots that still produce looong list.
If you are an owner add `FedoraGroup` tag to this resource. See
https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/aws-access/#_role_and_user_policies
Region: us-east-1
Instances: (name, id, owner)
* N/A
Here comes April edition of resources running in AWS. It's a snapshot of
resources running today.
FedoraGroup: Not tagged
Region: ap-south-1
Service Name:
# of AMIs: 1302
Region: eu-south-1
Service Name:
# of AMIs: 102
Region: il-central-1
Service Name:
# of
Dne 02. 05. 24 v 7:25 dop. Miroslav Suchý napsal(a):
Here comes April edition of resources running in AWS. It's a snapshot of
resources running today.
I had a bug in script and size of volumes were incorrectly calculated. Here is
fixed version:
FedoraGroup: abrt
Region: us-east-1
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
Here comes January edition of resources running in AWS. It's a snapshot of
resources running today.
Per request of Miro Vadkerti I grouped it by (FedoraGroup, region, ServiceName). I will try to make it more compact next
time, but giving up now as it already cost me half of the night.
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
This is without AMIs and Snapshots that still produce looong list.
Region: us-west-1
Volumes - [id name (attached to instance, owner)]:
* vol-0d7702fbe7ab94c6f N/A (famna.fedorainfracloud.org, N/A)
Region: us-west-2
Instances: (name, id, owner)
* openscanhub-test (i-0c32e3d4eff4bf1a4, N/A)
Dne 04. 04. 24 v 4:06 dop. Dusty Mabe napsal(a):
If you don't mind let me try to get the FedoraGroup tag added to our CoreOS
AMIs first.
I'll try to set up something to get that done this week.
Sure. I pause any deletion till end of the current freeze (scheduled to
2024-04-16).
--
Miroslav
Here comes January edition of resources running in AWS. It's a snapshot of
resources running today.
For the first time, AMIs and Snapshots are included:
FedoraGroup: Not tagged
Region: ap-south-2
# of AMIs: 222
Snapshots: 2220 GB in 222 snapshots
Region: ap-south-1
This is without AMIs and Snapshots that still produce looong list.
Region: ap-southeast-1
Instances: (name, id, owner)
* proxy38 (i-0a1ee820c765d573c, N/A)
Volumes - [id name (attached to instance, owner)]:
* vol-0cbc4cc3e8cab429f N/A (proxy38, N/A)
Region: us-east-1
Instances: (name, id,
Here comes May edition of resources running in AWS. It's a snapshot of
resources running today.
FedoraGroup: centos-stream-build
Region: us-east-2
Service Name:
Instance Type: t2.micro - Count: 1
FedoraGroup: Not tagged
Region: ap-south-1
Service Name:
# of AMIs: 1309
This is without AMIs and Snapshots that still produce looong list.
If you are an owner add `FedoraGroup` tag to this resource. See
https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/aws-access/#_role_and_user_policies
Region: ap-northeast-2
Instances: (name, id, owner)
*
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
201 - 239 of 239 matches
Mail list logo
