infrastructure April 2026

infrastructure@lists.fedoraproject.org

7 participants
29 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

Fedora 44 Final Infra freeze now in effect!
by Kevin Fenzi 29 Apr '26

29 Apr '26

Greetings. we are now in the infrastructure freeze leading up to the Fedora 44 Final release. This is a final release freeze. We do this to ensure that our infrastructure is stable and ready to release Fedora 44 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 2026-04-14 (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

1 1

[Fedocal] Reminder meeting : F44 Final Go/No-Go Meeting
by jspaleta＠redhat.com 21 Apr '26

21 Apr '26

Dear all, You are kindly invited to the meeting: F44 Final Go/No-Go Meeting on 2026-04-23 from 18:00:00 to 20:00:00 UTC The meeting will be about: Please join us for the Fedora Linux 44 Final Go/No-Go meeting in #fedora-meeting on matrix @ 1800 UTC. In this meeting, we will determine the status of the release candidate for F44. For more information on this meeting, please visit https://fedoraproject.org/wiki/Go_No_Go_Meeting Source: https://calendar.fedoraproject.org//meeting/11147/

1 0

Fedora Communishift Notification for project: communishift-draft-share
by admin＠fedoraproject.org 15 Apr '26

15 Apr '26

Dear Fedora Communishift Project Administrators (BCC'd), This is a reminder that the Communishift project communishift-draft-share will be disasbled and then later deleted during the Fedora post release process at the same time the oldest fedora is retired (1 month after a new fedora release). Please ensure you have a backup of any important configuration or data from your project. Consult Openshift docs. If you need to request an exemption, please file a ticket here: https://forge.fedoraproject.org/infra/tickets Make sure to reference the project name and please provide a reason for the extention, also please include how long you wish the extention to be in place for.

1 0

Fedora Communishift Notification for project: communishift-happinesspackets
by admin＠fedoraproject.org 15 Apr '26

15 Apr '26

Dear Fedora Communishift Project Administrators (BCC'd), This is a reminder that the Communishift project communishift-happinesspackets will be disasbled and then later deleted during the Fedora post release process at the same time the oldest fedora is retired (1 month after a new fedora release). Please ensure you have a backup of any important configuration or data from your project. Consult Openshift docs. If you need to request an exemption, please file a ticket here: https://forge.fedoraproject.org/infra/tickets Make sure to reference the project name and please provide a reason for the extention, also please include how long you wish the extention to be in place for.

1 0

Fedora Communishift Notification for project: communishift-standupbot
by admin＠fedoraproject.org 15 Apr '26

15 Apr '26

Dear Fedora Communishift Project Administrators (BCC'd), This is a reminder that the Communishift project communishift-standupbot will be disasbled and then later deleted during the Fedora post release process at the same time the oldest fedora is retired (1 month after a new fedora release). Please ensure you have a backup of any important configuration or data from your project. Consult Openshift docs. If you need to request an exemption, please file a ticket here: https://forge.fedoraproject.org/infra/tickets Make sure to reference the project name and please provide a reason for the extention, also please include how long you wish the extention to be in place for.

1 0

Fedora Communishift Notification for project: communishift-openscanhub
by admin＠fedoraproject.org 15 Apr '26

15 Apr '26

Dear Fedora Communishift Project Administrators (BCC'd), This is a reminder that the Communishift project communishift-openscanhub will be disasbled and then later deleted during the Fedora post release process at the same time the oldest fedora is retired (1 month after a new fedora release). Please ensure you have a backup of any important configuration or data from your project. Consult Openshift docs. If you need to request an exemption, please file a ticket here: https://forge.fedoraproject.org/infra/tickets Make sure to reference the project name and please provide a reason for the extention, also please include how long you wish the extention to be in place for.

1 0

Fedora Communishift Notification for project: communishift-planet
by admin＠fedoraproject.org 15 Apr '26

15 Apr '26

Dear Fedora Communishift Project Administrators (BCC'd), This is a reminder that the Communishift project communishift-planet will be disasbled and then later deleted during the Fedora post release process at the same time the oldest fedora is retired (1 month after a new fedora release). Please ensure you have a backup of any important configuration or data from your project. Consult Openshift docs. If you need to request an exemption, please file a ticket here: https://forge.fedoraproject.org/infra/tickets Make sure to reference the project name and please provide a reason for the extention, also please include how long you wish the extention to be in place for.

1 0

Fedora Communishift Notification for project: communishift-ocm
by admin＠fedoraproject.org 15 Apr '26

15 Apr '26

Dear Fedora Communishift Project Administrators (BCC'd), This is a reminder that the Communishift project communishift-ocm will be disasbled and then later deleted during the Fedora post release process at the same time the oldest fedora is retired (1 month after a new fedora release). Please ensure you have a backup of any important configuration or data from your project. Consult Openshift docs. If you need to request an exemption, please file a ticket here: https://forge.fedoraproject.org/infra/tickets Make sure to reference the project name and please provide a reason for the extention, also please include how long you wish the extention to be in place for.

1 0

Fedora Communishift Notification for project: communishift-metrics
by admin＠fedoraproject.org 15 Apr '26

15 Apr '26

Dear Fedora Communishift Project Administrators (BCC'd), This is a reminder that the Communishift project communishift-metrics will be disasbled and then later deleted during the Fedora post release process at the same time the oldest fedora is retired (1 month after a new fedora release). Please ensure you have a backup of any important configuration or data from your project. Consult Openshift docs. If you need to request an exemption, please file a ticket here: https://forge.fedoraproject.org/infra/tickets Make sure to reference the project name and please provide a reason for the extention, also please include how long you wish the extention to be in place for.

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure April 2026