This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on

We provide you both infographics and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.

Week: 05 December – 09 December 2022

CPE Infographic

Highlights of the week

Infrastructure & Release Engineering

Goal of this Initiative

Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on.
Planning board


Fedora Infra

  • Both prod/stg openshift clusters upgraded to latest.
  • Finished update/reboot cycle and fallout from it.
  • All builders upgraded to f37
  • Drive/memory replaced in bvmhost-x86-03 by dell
  • Docs-old finally dropped
  • Bodhi upgraded in stg, but some db issues to look into

CentOS Infra including CentOS CI

  • Refactored Ansible roles for MBS and ODCS for CentOS Stream

Release Engineering

CentOS Stream

Goal of this Initiative

This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream.


  • All Stream 8 content synced to the new place, keeping it in sync.
  • Investigated new directory structure for Stream composes
    • stream-{8,9,10}/{test,development,production}
    • The current {test,development,production} will point at the newest Stream directory
    • This is not implemented yet.  
  • Found and fixed an issue that was holding back module pushes due to NFS


Goal of this initiative

Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).

EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more.


  • EPEL 9 is up to 11,740 (+134) packages from 4,479 (+47) source packages
  • Severity column added to willit CVE status pages to help triage work (epel7, epel8, epel9)
  • libwmf, libnxz retired from EPEL 9 due to being added to RHEL 9.1
  • Carl presented “The Road to EPEL 9” at OLF conference

FMN replacement

Goal of this initiative

FMN (Fedora-Messaging-Notification) is a web application allowing users to create filters on messages sent to (currently) fedmsg and forward these as notifications on to email or IRC.
The goal of the initiative is mainly to add fedora-messaging schemas, create a new UI for a better user experience and create a new service to triage incoming messages to reduce the current message delivery lag problem. Community will profit from speedier notifications based on own preferences (IRC, Matrix, Email), unified fedora project to one message service and human-readable results in Datagrepper.
Also, CPE tech debt will be significantly reduced by dropping the maintenance of fedmsg altogether.


  • Planning for December (into early January) done today
  • End-to-end testing while deployed to staging
  • Caching is the next big ticket item to work on in December/January