infrastructure November 2024

infrastructure@lists.fedoraproject.org

5 participants
5 discussions

VDO
by Miroslav Suchý 04 Jul '26

04 Jul '26

After I seen the talk about VDO: https://www.youtube.com/watch?v=7CGr5LEAfRY I went ahead and tried it. I tried it on small (12GB) sample of Copr data and I saved 20-30% data. I then deployed it on production server retrace.fedoraproject.org and saved there 15% out of 2TB. Several notes: The RPM packages are only available for RHEL. Recently the public github has been updated with version of VDO, which should work on Fedora. No RPM available for Fedora yet though. Here are my notes: # vdo create --name=vdo1 --device=/dev/vdb --vdoLogicalSize=1T # mkfs.ext4 /dev/mapper/vdo1 Some slides suggest to use -E discard. This is not needed for new volumes. See vdo-devel mailing list for reasoning. # mount -o discard /dev/mapper/vdo1 /mnt/a Probably best scenario is to create vdo on whole disk and then make PV from whole VDO disk and put LVM on top of that. When you already have data, you cannot convert your disk to VDO. You need create new VDO disk, format it, mount it and copy the data. In my case, due limited space for migration I created a small LVM volume "vdosrv": # lvcreate -L 80G -n vdosrv vol0 I converted it to VDO which claims to have 2TB of vitual total size # vdo create --name=srv18 --device=/dev/vol0/vdosrv --vdoLogicalSize=2T # mkfs.ext4 /dev/mapper/srv18 See how many space is *actually* free. # vdostats # mkdir /mnt/srv18 # mount -o discard /dev/mapper/srv18 /mnt/srv18 Now I moved some data from old volume to /mnt/srv18. I shrank the FS of old volume, I shrank the old LV. And then I enlarged the new LV. # lvresize -L +400G /dev/vol0/vdosrv and let know vdo that it can use the new space: # vdo growPhysical -n srv18 I repeated this several times. I have to say that my experience is so far good. I hope that my notes help someone. Miroslav

10 14

Deleting old AMIs in AWS
by Miroslav Suchý 09 Jan '25

09 Jan '25

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. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

5 33

Planned Outage - Server update/reboots - 2024-11-20 21:00 UTC
by Kevin Fenzi 18 Nov '24

18 Nov '24

Planned Outage - Server update/reboots - 2024-11-20 21:00 UTC There will be an outage starting at 2024-11-20 21:00 UTC, which will last approximately 5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2024-11-20 21:00 UTC' Reason for outage: We will be updating and rebooting servers to pick up the recent RHEL 9.5 release as well as to move a number of instances to Fedora 41 (including hopefully builders/koji hubs) Affected Services: Most maintainer / contributor services will be affected for some short windows during the outage. Package maintainers are advised to wait for the outage to be over to launch any builds. Ticket Link: https://pagure.io/fedora-infrastructure/issue/12293 Please join #admin:fedoraproject.org / #noc:fedoraproject.org on matrix. Please add comments to the ticket for this outage above. Updated status for this outage may be available at https://www.fedorastatus.org/

1 0

Meeting Agenda Item: Introduction Khalid Aljahil
by Khalid Aljahil 14 Nov '24

14 Nov '24

Hello everyone. I’ve been lurking for a bit and it’s time to introduce myself to you all. My name is Khalid Aljahil. I’m a sysadmin with 10 years of experience. My day to day tasks usually involve: - Managing Linux servers - Creating and managing Ansible playbooks - Managing Kubernetes clusters. - Maintaining our Gitlab instance. - Other tasks including backups / health monitoring / scripting … etc I’m a CKA, RHCSA, and god willing, will soon be RHCE. What I’d like to work on are mostly things I already have experience with, so Ansible, K8s, and server management and configuration. Matrix handle: @khalid:fedora.im

3 2

Planned Outage: Pagure & Dist-Git - 2024-11-13 08:00 UTC
by Aurelien Bompard 05 Nov '24

05 Nov '24

There will be an outage starting at 2024-11-13 08:00 UTC, which will last approximately 1 hour. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2024-11-13 08:00 UTC' Reason for outage: switch authentication from OpenID to OIDC Affected Services: - Dist-Git - Pagure Ticket Link: https://pagure.io/fedora-infrastructure/issue/12272 Contact Information: - The Fedora Infrastructure channel on Matrix: https://matrix.to/#/#admin:fedoraproject.org - Add comment to the ticket for this outage above.

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure November 2024