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 -cpe channel on

We (CPE team) will be joining Fedora Social Hour on Jan 27th.
Looking forward to seeing a lot of you!

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.


Fedora Infra

  • Mostly quiet holidays with only minor reboots, etc
  • More koji upgrades: all aarch64/armv7 done, s390x kvm and hubs left to do
  • Container builds broken, needs more eyes
  • Centos cert fetching broken, needs more eyes

CentOS Infra including CentOS CI

  • CentOS Linux 8 EOL plan
  • Hardware issues (storage box, 64 compute nodes for CI infra)
  • Kmods SIG DuD discussion (koji plugin vs external script)
  • CI storage for ocp/openshift migration planning

Release Engineering

  • Rawhide compose issues, but we got a good compose yesterday after a bunch of work
  • Mass rebuild of F36 next week

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.


  • Finished our January planning, working on:
    • Preparing new version of Content Resolver for production, finishing up stuff around the buildroot integration
    • Exploring things around increasing compose quality
    • Business as usual

Datanommer/Datagrepper V.2

Goal of this initiative

The datanommer and datagrepper stacks are currently relying on fedmsg which
we want to deprecate.
These two applications need to be ported off fedmsg to fedora-messaging.
As these applications are ‘old-timers’ in the fedora infrastructure, we would
also like to look at optimizing the database or potentially redesigning it to
better suit the current infrastructure needs.
For a phase two, we would like to focus on a DB overhaul.


  • Data is migrated, we need to deploy the new code to production now.

CentOS Duffy CI

Goal of this initiative

Duffy is a system within CentOS CI Infra which allows tenants to provision and
access bare metal resources of multiple architectures for the purposes of
CI testing.
We need to add the ability to checkout VMs in CentOS CI in Duffy. We have
OpenNebula hypervisor available, and have started developing playbooks which
can be used to create VMs using the OpenNebula API, but due to the current state
of how Duffy is deployed, we are blocked with new dev work to add the
VM checkout functionality.


  • Work on backend -> modules to provision vms
  • Legacy API integration

Image builder for Fedora IoT

Goal of this initiative

Integration of Image builder as a service with Fedora infra to allow Fedora IoT migrate their pipeline to Fedora infra.


  • Team forming this week. Currently waiting on work from the Image Builder team to wrap to unblock us from moving forward


Goal of this initiative

This initiative is to separate Bodhi into multiple sub packages,
fix integration and unit tests in CI, fix dependency management,
and automate part of the release process.
Read ARC team findings in detail.


  • Team is forming this week and will officially be launching work next Monday


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.


  • epel9 is growing rapidly:
    • 2589 packages available (355 more in testing)
    • 1158 source rpms (225 more in testing)
  • Positive community response
  • Ongoing documentation improvements

Kindest regards,
CPE Team