CPE Weekly Update - Week 42 2022

Originally published at: https://communityblog.fedoraproject.org/cpe-weekly-update-week-42-2022/

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.

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: 17th – 21st October 2022

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
Docs

Update

Fedora Infra

  • Python3 FMN is now running and processing messages

CentOS Infra including CentOS CI

  • Decommission legacy sponsored infra
  • Collaboration with Artwork SIG for new logo rollout
  • Stream Koji STG environment up and running
  • Internal RHEL mirror for s390x architecture for Stream Infra

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.

Updates

  • One of the aarch64 builders is down, we’re investigating (CS-1267)
  • Moving pungi configs for Stream 8 to Gitlab
  • Fixing ELN builds
  • PowerPC 64 LE working in ELN again

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

  • EPEL 9 is up to 9472 (+81) packages from 3899 (+29) source packages
  • EPEL Steering Committee voted to push EPEL 8 Modular retirement out to February
  • EPEL 8 Modular repo will still be disabled by default in epel-release on Halloween
  • Retired uninstallable epel8 packages: python-sphinx-autodoc-typehints
  • Retired uninstallable epel9 packages: q4wine, resalloc-openstack

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.

Updates

  • API Endpoints all nearly tested
  • Backend coverage back up to 100%
  • Working on querying FASJSON to return list of users, artifacts owned
  • Updating rules pages to be more descriptive