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 libera.chat (https://libera.chat/).

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.

Update

Fedora Infra

  • All fedora ansible hosts (except aws) now using linux-system-roles/network for network config!
  • Several upstream koji issues. One tagging issue fixed, one new one still being worked on. ;(
  • Got networking setup so CentOS iad2 master mirror could read Fedora netapp. (to prep for adding space there for them)
  • Invalid users disabled (ones with _ – . and one char)

CentOS Infra including CentOS CI

  • Centos 8 has been retired and removed from mirrors
  • Big storage reorganization (multiple HDD issues, or pending – pfa mode-) , going from out of warranty to still out of warranty node (risk mitigation)
  • Business as usual

Release Engineering

  • Rawhide composes failing, been a long string of bugs

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.

Updates

  • New version of Content Resolver with an integrated buildroot resolver is live! There are testing views (ELN and Stream) using the new resolver, the proper ones will be switched to that soon after some extra validation. All following updates will be again showing up as they come, this bigger one just had to come at once.
  • Started the work on bringing CS8 and CS9 workflows together.
  • Otherwise business as usual.

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.

Updates

  • Still ongoing 🙂
  • Legacy API
  • Backend tasks 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.

Updates

  • End to end running(ish) locally
  • Configuring of the plugins this week
  • Image builder team still blocking but not for long as they are landing PRs now
  • Spent some time as a team understanding the full e2e flow of osbuild and how it will fit in the Fedora IoT architecture

Bodhi

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 at: https://fedora-arc.readthedocs.io/en/latest/bodhi/index.html

Updates

  • Bodhi has been split into multiple packages
  • bodhi-ci has been cleaned up (split into multiple source files)
  • Vagrant box now works out of the box (previously some systemd services were failing after provisioning)
  • CI tests now run using GitHub Actions

EPEL

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.

Updates

  • EPEL9 up to 1648 source packages (increase of 109 from last week)
  • Three EPEL talks happening at CentOS Dojo, starting tomorrow

Kindest regards,
CPE Team