CPE Weekly Update – Week 35 2022

Originally published at: CPE Weekly Update – Week 35 2022 – Fedora Community Blog

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/).

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: 29th of August – 2nd of September 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

  • Nspawn off in rawhide to sort out kernel building issue (was filed back in 2017!)
  • Had issues with the openh264 repo late last week. Everything should be fixed now.
  • Got critical path packages update all reworked (thanks adamw!)
  • Business as usual

CentOS Infra including CentOS CI

  • Rootless builds with podman available in openshift
  • iso images DriverDisks are now live for Kmods SIG
  • Stream infra handover process/jira EPIC
  • Investigating network issue in Community cage impacting all centos infra (including Stream 8/9 builds and SIGs)
  • Business as usual (mirrors, cbs tags)

Release Engineering

  • Fedora Media Writer 5.0.3 released
  • Business as usual

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

  • Did a scratch module build on the new c8s infrastructure.
    • Wrote some code to migrate lookaside source from old infra. to the new. Should run it this week.

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 7654 (+227) packages from 3377 (+55) source packages
  • Today is the last day to take the EPEL survey
  • sqlcipher EPEL 9 request lead to updating the package in rawhide with a coordinated rebuild of 5 other packages
  • Formalizing an End of Life policy in our docs per CentOS board request
  • Removed nginx module streams from EPEL 8 Modular that were conflicting with RHEL 8 module streams

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

  • Frontend mockups
  • CI improvements and cleanups
  • More work on renovate-driven automated dependency updates
  • Progress on message consumer
  • Establish user identities from OIDC token in API backend
  • Started work on notification senders