<div dir="ltr"><div><p>Hi everyone,</p><p>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 (<a href="https://libera.chat/" target="_blank">https://libera.chat/</a>).</p>
<p>Week: 20th - 24th June 2022</p><p><span style="color:rgb(32,33,36);font-family:Roboto,arial,sans-serif;font-size:13px;white-space:pre-wrap">If you wish to read this in form of a blog post, check the post on the Fedora community blog: </span><a href="https://communityblog.fedoraproject.org/cpe-weekly-update-week-25-2022/" target="_blank">https://communityblog.fedoraproject.org/cpe-weekly-update-week-25-2022/</a></p>
<h1>Highlights of the week</h1>
<h2>Infrastructure & Release Engineering</h2>
<h2>Goal of this Initiative</h2>
<p>The purpose of this team is to take care of day-to-day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.<br>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.).<br>The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on.<br>Link to planning board: <a href="https://zlopez.fedorapeople.org/I&R-2022-06-22.pdf" target="_blank">https://zlopez.fedorapeople.org/I&R-2022-06-22.pdf</a><br>Link to docs: <a href="https://docs.fedoraproject.org/en-US/infra/" target="_blank">https://docs.fedoraproject.org/en-US/infra/</a></p>
<h2>Update</h2>
<h3>Fedora Infra</h3>
<ul><li>Most apps have moved over to the OpenShift4 cluster. Hopefully, the transition should be finishing up this week.</li><li>Wiki: All upgraded in production and working (thanks Ryan!)</li><li>Resultsdb: All moved over to OpenShift 4 in prod and working (thanks Leo!)</li><li>Business proceeding as usual</li></ul>
<h3>CentOS Infra including CentOS CI</h3>
<ul><li>Kerberos settings switch for <a href="http://git.centos.org" target="_blank">git.centos.org</a> (kcm on el8 vs keyring on el7) for <a href="https://pagure.io/centos-infra/issue/811" target="_blank">lookaside upload CGI</a>[1]</li><li>Issue on iad2 hosted<a href="https://pagure.io/centos-infra/issue/812" target="_blank"> reference mirror</a>[2] (epel.next and mirrormanager), all fixed now</li><li>Duffy CI ongoing tasks and deployments (all announced)</li><li>Equinix <a href="https://pagure.io/centos-infra/issue/816" target="_blank">nodes migration</a>[3] (on their request)</li><li>Business proceeding as usual</li></ul>
<h3>Release Engineering</h3>
<ul><li>Compose-tracker updated to f36 in staging, production happening tomorrow</li><li>Python 3.11 merged to rawhide</li><li>MBS randomly fails to process builds</li><li>Rawhide compose failures recently (syslinux retirement, then python 3.11 merge) all fixed now</li><li>Business proceeding as usual</li></ul>
<h2>CentOS Stream</h2>
<h2>Goal of this Initiative</h2>
<p>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.</p>
<h2>Updates</h2>
<ul><li>CentOS Stream 8: Manually keeping regular RPMs and module RPMs updated on the koji.stream server as current updates are composed and released.</li></ul>
<h2>CentOS Duffy CI</h2>
<h2>Goal of this Initiative</h2>
<p>Duffy is a system within CentOS CI infrastructure allowing tenants to provision and access machines (physical and/or virtual, of different architectures and configurations) for the purposes of CI testing. Development of Duffy is largely finished, we're currently planning and testing deployment scenarios.</p>
<h2>Updates</h2>
<ul><li>Release version 3.2.1</li><li>Docs, docs, docs and a Dojo</li></ul>
<h2>Package Automation (Packit Service)</h2>
<h2>Goal of this initiative</h2>
<p>Automate RPM packaging of infra apps/packages</p>
<h2>Updates</h2>
<ul><li>Mostly business as usual</li><li>Thanks again to all who are reviewing our PRs</li><li>Most of our GitHub critical apps are enabled now or close to being enabled</li></ul>
<h2>Flask-oidc: oauth2client replacement</h2>
<h2>Goal of this initiative</h2>
<p>Flask-oidc is a library used across the Fedora infrastructure and is the client for ipsilon for its authentication. flask-oidc uses oauth2client. This library is now deprecated and no longer maintained. This will need to be replaced with authlib.</p>
<h2>Updates:</h2>
<ul><li>POC working using authlib, tidying up code to prepare to submit a PR back to upstream</li></ul>
<h2>EPEL</h2>
<h2>Goal of this initiative</h2>
<p>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).</p>
<p>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 a build system, Bugzilla instance, updates manager, mirror manager and more.</p>
<h2>Updates</h2>
<ul><li>This week we have 6442 (+127) packages, from 2882 (+76) source packages</li><li>Containerd and puppet retired from EPEL7 because of upstream EOL and multiple CVEs.</li><li>Caddy was updated, fixing 4 CVEs in EPEL9</li></ul></div><div><b><font size="4">Index</font></b></div><div>[1] <a href="https://pagure.io/centos-infra/issue/811" target="_blank">https://pagure.io/centos-infra/issue/811</a> </div><div>[2] <a href="https://pagure.io/centos-infra/issue/812" target="_blank">https://pagure.io/centos-infra/issue/812</a></div><div>[3] <a href="https://pagure.io/centos-infra/issue/816" target="_blank">https://pagure.io/centos-infra/issue/816</a></div><br clear="all"><div><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr"><div>Thanks and Regards,</div>Akashdeep Dhar (he/him),<div><p dir="ltr" style="line-height:1.38;text-align:justify;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:"Red Hat Text",sans-serif;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Objective Representative, Fedora Council</span></p><p dir="ltr" style="line-height:1.38;text-align:justify;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:"Red Hat Text",sans-serif;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Red Hat Community Platform Engineering</span></p><p dir="ltr" style="line-height:1.38;text-align:justify;margin-top:0pt;margin-bottom:0pt"><a href="mailto:t0xic0der@fedoraproject.org" target="_blank" style="text-decoration-line:none"><span style="font-size:10pt;font-family:"Red Hat Text",sans-serif;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;text-decoration-line:underline;vertical-align:baseline;white-space:pre-wrap">t0xic0der@fedoraproject.org</span></a></p><p dir="ltr" style="line-height:1.38;text-align:justify;margin-top:0pt;margin-bottom:0pt"><a href="mailto:akashdeep@redhat.com" target="_blank" style="text-decoration-line:none"><span style="font-size:10pt;font-family:"Red Hat Text",sans-serif;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;text-decoration-line:underline;vertical-align:baseline;white-space:pre-wrap">akashdeep@redhat.com</span></a></p></div></div></div></div></div>