Heads up - AWS Snapshots cleanup
by Miroslav Suchý
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
5 months, 2 weeks
AWS Snapshots without FedoraGroup tag
by Miroslav Suchý
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 months, 2 weeks
Introduction - Chris(devic3)
by Krzysztof Kuberski
Hello,
I wish to help in contributing at Fedora, below some informations about me
IRC - DeviC3
Skills/job:
Actually, I'm working as sysadmin in the RHEL environment and a secondary
job as LSE in the same company.
Skills which can be useful:
scirpts - Bash;Python,
with background in networking and low level OS debugging,
automation,
monitoring,
storage
Wish to learn?
If still used, C programming and working with kernel
Best regards, Christopher !
5 months, 3 weeks
AWS cleanup
by Miroslav Suchý
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 FedoraGroup=garbage-collector at the end of month.
--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
5 months, 4 weeks
intent to retire: fedmsg-irc, old fmn, osbs
by Kevin Fenzi
Greetings everyone.
Now that fedora 39 is out the door, I'd like to schedule some
retirements of a few old services:
fedmsg-irc: This is a old fedmsg process that send fedmsg's to IRC.
Currently we have one running in production and one in staging, both on
rhel7 vm's that we would like to retire. They currently gateway the
entire message bus to #fedora-fedmsg (prod) and #fedora-fedmsg-stg
(staging), but due to the volume and IRC throttling they are way behind.
It's often behind by 12-48 hours. Additionally, it sends some matching
messages to the #fedora-releng channel (composes, etc). We plan to
replace that with a matrix bot webhook at some point.
old fmn (old fedora notifications service).
https://apps.fedoraproject.org/notifications-old/
This was replaced with https://notifications.fedoraproject.org/
and we said we would sunset the old one after f39 was out.
If you're missing features with the new one, please make sure they are
tracked at https://github.com/fedora-infra/fmn/issues
osbs (openshift build service). This is 4 openshift 3.11 clusters. (one
each for x86_64 and aarch64 x production and staging). This service
built containers for us, but all the containers we now build are done
via ImageFactory (base, minimal, toolbox) or elsewhere (quay.io, etc).
I'd like to turn these services off next wed (2023-11-15) if there's no
reasons I missed to do so before then. We will keep the data from them
around in case we need to bring them back or get data from them.
Please let us know if there's any uses for these services we aren't
aware of before next wed.
https://pagure.io/fedora-infrastructure/issue/11504 is a tracking ticket
for the osbs cluster retirement.
Thanks!
kevin
6 months, 1 week
Fedora 39 Final freeze now in effect!
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 39
Final release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release Fedora 39 when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone
https://infrastructure.fedoraproject.org/infra/ansible.git
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2023-10-18 (or later if
release slips). Frozen hosts should have no changes made to them without
a sign-off on the change from at least 2 sysadmin-main or rel-eng
members, along with (in most cases) a patch of the exact change to be
made to this list and/or a pull-request to the infra/ansible repo.
Thanks,
kevin
6 months, 1 week
