infrastructure December 2023

infrastructure@lists.fedoraproject.org

10 participants
10 discussions

HEADS UP - deletion of Fedora Atomic Hosts AMIs
by Miroslav Suchý 09 Feb '24

09 Feb '24

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, Manager, Packit and CPT, #brno, #fedora-buildsys

2 2

[salimma@fedoraproject.org: [EPEL-devel] Mailman3 web components for EPEL 9 now in Bodhi!]
by Michel Lind 19 Jan '24

19 Jan '24

Meant to send this to infrastructure@ as well and I hit Send too soon. Best, Michel ----- Forwarded message from Michel Lind <salimma(a)fedoraproject.org> ----- Date: Thu, 21 Dec 2023 14:13:26 -0600 From: Michel Lind <salimma(a)fedoraproject.org> To: EPEL Development List <epel-devel(a)lists.fedoraproject.org> Subject: [EPEL-devel] Mailman3 web components for EPEL 9 now in Bodhi! Dear all, I'm happy to be able to provide this holiday present to the infra team (and other interested parties) - after chasing through tens of dependencies, going through multiple stalled EPEL requests, and evolving ebranch to automate some of these pain points, the `mailman3` web components are now built for EPEL 9 and available to test! https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-4c6b819c9c This is a follow-up to `mailman3` itself that entered EPEL 9 two months ago: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f022c8f3ad There are probably some missing plugins etc. that have not been branched and built for EPEL 9 yet, let me know if you have a list and I'm happy to get to them next. Happy holidays, -- Michel Lind (né Salim) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 -- _______________________________________________ epel-devel mailing list -- epel-devel(a)lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave(a)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/epel-devel@lists.fedoraprojec… Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ----- End forwarded message ----- -- Michel Lind (né Salim) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2

4 3

Bugzilla and Groups
by Tim Flink 23 Dec '23

23 Dec '23

What are the general rules around default bugzilla assignee for packages? I'm trying to set the default assignee for rocm-cmake to rocm-packagers-sig but keep getting an error: Unable to update the bugzilla assignee(s): Invalid user or group name as fedora_assignee As far as I know, rocm-packagers-sig is a pkgdb group. Do I need to request a change to the group for it to be the default bugzilla assignee? Is setting a group as the default assignee against some policy that I don't know about? My search-fu has been failing me on this so I figured I would ask to see if someone here has an answer. Thanks, Tim

2 2

Last Day to Vote in F39 Elections is Today!
by Aoife Moloney 21 Dec '23

21 Dec '23

Hi all, Today is the last day to vote in the F39 elections. Please make sure you do so, in particular for FESCo where the number of candidates exceed the open seats. To vote please visit the Elections App https://elections.fedoraproject.org/ Kind regards, Aoife Aoife Moloney Fedora Operations Architect

1 0

F40 Change Proposals Requiring Infra Changes - Deadline Today
by Aoife Moloney 20 Dec '23

20 Dec '23

Hi all, Today is the final day to submit Change Proposals <https://docs.fedoraproject.org/en-US/program_management/changes_guide/> that require *infrastructure changes* for Fedora Linux 40. Changes do not have to be accepted by this deadline, but they must be submitted. Thanks, Aoife -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney

1 0

Holiday reminder 2023
by Kevin Fenzi 08 Dec '23

08 Dec '23

Just a gentle reminder that the holiday season is coming up. Many contributors have more time to work on things, others are spending time away with friends and family. When you push changes during the holidays be extra aware of anything that might cause outages or breakage that might pull someone who was enjoying time away back to fix things. Happy holidays everyone. kevin

1 0

congrats to another new sysadmin-mainer
by Kevin Fenzi 05 Dec '23

05 Dec '23

I'm happy to announce that We have approved a new member in our sysadmin-main group: praiskup This is the core group of trusted folks that high level access to most everything in fedora infrastructure. As many of you know, he's wrangled copr for quite some time, as well as taking on other critical projects like maintaining mock and it's various configs. Adding him to sysadmin-main will help the copr team to more quickly change items that need that level of access, as well as hopefully allowing him to help out in other places around infrastructure as his time permits. Congrats! Use your powers for good! :) kevin

5 4

Heads up - AWS Snapshots cleanup
by Miroslav Suchý 05 Dec '23

05 Dec '23

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 in different thread in this ML we have ten thousands of snapshots and it is impossible to evaluate each of them separately. If you are aware of something that should be preserved, let me know. Or better, tag it. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

3 6

AWS usage per group (November)
by Miroslav Suchý 03 Dec '23

03 Dec '23

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 - Total Size: 1540 GiB Region: us-east-2 Instance Type: m5a.4xlarge - Count: 1 Instance Type: r5.large - Count: 4 Instance Type: i3.2xlarge - Count: 6 Instance Type: r5.xlarge - Count: 2 Instance Type: c5.2xlarge - Count: 1 Instance Type: c6a.large - Count: 17 Volume Type: gp3 - Total Size: 11654 GiB FedoraGroup: centos-stream-build Region: us-east-2 Instance Type: t2.micro - Count: 1 FedoraGroup: garbage-collector Region: ap-southeast-1 Volume Type: standard - Total Size: 6 GiB FedoraGroup: centos-stream-osci Region: ca-central-1 Instance Type: m5d.large - Count: 5 Instance Type: t2.micro - Count: 1 Volume Type: gp3 - Total Size: 36 GiB FedoraGroup: abrt Region: us-east-1 Instance Type: t3a.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 10 GiB 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 Instance Type: c5n.2xlarge - Count: 1 Instance Type: m5.xlarge - Count: 1 Instance Type: m6gd.4xlarge - Count: 1 Volume Type: gp3 - Total Size: 16223 GiB Region: us-west-1 Instance Type: t3.medium - Count: 1 Volume Type: gp3 - Total Size: 40 GiB Region: us-west-2 Instance Type: m5.large - Count: 4 Instance Type: m6g.large - Count: 1 Instance Type: t3.large - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Instance Type: c6gd.xlarge - Count: 1 Volume Type: standard - Total Size: 100 GiB Volume Type: gp3 - Total Size: 900 GiB Region: af-south-1 Instance Type: c5d.xlarge - Count: 2 Volume Type: gp3 - Total Size: 25 GiB Region: eu-west-2 Instance Type: c5d.xlarge - Count: 1 Volume Type: gp3 - Total Size: 20 GiB Region: ap-northeast-2 Instance Type: c5n.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 196 GiB Region: sa-east-1 Instance Type: c5.2xlarge - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 200 GiB Region: ap-southeast-1 Instance Type: c5d.xlarge - Count: 1 Instance Type: c5n.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 108 GiB Region: us-east-1 Instance Type: t3.medium - Count: 1 Instance Type: t3.small - Count: 1 Instance Type: c5.xlarge - Count: 2 Instance Type: t2.medium - Count: 2 Instance Type: c5.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 330 GiB Region: us-east-2 Instance Type: c5d.large - Count: 1 Instance Type: t2.micro - Count: 1 Instance Type: t3.medium - Count: 1 Volume Type: gp3 - Total Size: 63 GiB FedoraGroup: min Region: eu-central-1 Instance Type: t3.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 1000 GiB FedoraGroup: copr Region: us-east-1 Instance Type: t3a.xlarge - Count: 6 Instance Type: m5a.4xlarge - Count: 2 Instance Type: c7i.xlarge - Count: 14 Instance Type: c7g.xlarge - Count: 89 Instance Type: t3a.medium - Count: 5 Instance Type: t3a.small - Count: 1 Instance Type: t2.medium - Count: 1 Volume Type: st1 - Total Size: 6000 GiB Volume Type: gp3 - Total Size: 4172 GiB Volume Type: io2 - Total Size: 20 GiB Volume Type: sc1 - Total Size: 81652 GiB FedoraGroup: centos Region: ap-south-1 Instance Type: t3.2xlarge - Count: 3 Instance Type: t3.large - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4570 GiB Region: eu-central-1 Instance Type: t2.small - Count: 1 Instance Type: t2.large - Count: 2 Instance Type: r5b.8xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Instance Type: t3.xlarge - Count: 1 Volume Type: gp3 - Total Size: 13200 GiB Region: us-west-2 Instance Type: m6i.2xlarge - Count: 2 Instance Type: t3.small - Count: 1 Instance Type: t3.xlarge - Count: 1 Volume Type: gp3 - Total Size: 13145 GiB Region: af-south-1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4050 GiB Region: eu-west-3 Instance Type: t2.large - Count: 2 Instance Type: t2.2xlarge - Count: 1 Instance Type: t3a.xlarge - Count: 1 Instance Type: t2.small - Count: 2 Instance Type: t3.xlarge - Count: 1 Instance Type: t3.large - Count: 1 Volume Type: gp3 - Total Size: 2917 GiB Region: eu-west-2 Instance Type: t2.small - Count: 1 Instance Type: t2.large - Count: 1 Instance Type: t3a.large - Count: 2 Instance Type: r5a.8xlarge - Count: 1 Instance Type: t3.large - Count: 2 Instance Type: t3.xlarge - Count: 1 Instance Type: t2.medium - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 26320 GiB Region: eu-west-1 Instance Type: t2.medium - Count: 4 Instance Type: t2.xlarge - Count: 3 Instance Type: t2.large - Count: 1 Instance Type: t2.small - Count: 2 Instance Type: t3.large - Count: 1 Instance Type: t3.medium - Count: 2 Volume Type: gp3 - Total Size: 584 GiB Region: ap-northeast-1 Instance Type: c6g.2xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 8070 GiB Region: sa-east-1 Instance Type: c6g.4xlarge - Count: 1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4250 GiB Region: ap-southeast-1 Instance Type: m6i.2xlarge - Count: 1 Volume Type: gp3 - Total Size: 4050 GiB Region: ap-southeast-2 Instance Type: m6i.2xlarge - Count: 2 Volume Type: gp3 - Total Size: 8100 GiB Region: us-east-1 Instance Type: t3.xlarge - Count: 2 Volume Type: gp3 - Total Size: 26350 GiB Region: us-east-2 Instance Type: t2.2xlarge - Count: 1 Instance Type: m5a.2xlarge - Count: 1 Instance Type: t3.xlarge - Count: 4 Instance Type: t3a.large - Count: 1 Instance Type: m6i.2xlarge - Count: 2 Instance Type: t2.large - Count: 2 Instance Type: t3.large - Count: 1 Instance Type: m4.2xlarge - Count: 1 Instance Type: t3.small - Count: 1 Instance Type: t3.medium - Count: 1 Volume Type: gp3 - Total Size: 46090 GiB -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

1 0

AWS Snapshots without FedoraGroup tag
by Miroslav Suchý 01 Dec '23

01 Dec '23

We have (almost) all instances and volumes properly tagged. Now let check Snapshots. 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=* -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

5 12

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure December 2023