Hi everyone, 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/).
If you wish to read this in the form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-of-november-15th-19th/ # 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. Updates ------- ### Fedora Infra * Mass updates & reboots carried out * Increased volumes on db01 and torrent02 * Moved s390x from z13 to z15 mainframe successfully * F34 & F35 maintainer test instances now available, F32 retired ### CentOS Infra including CentOS CI * CentOS Linux 8.5.2111 released! * Preparing to sunset its infra needs and switch SIG content for RHEL8 buildroot (opt-in) * Handed over the dedicated Duffy Dev LAB infra for duffy initiative ### Release Engineering * 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 ------- * Thanks to a contribution from the folks in the Automotive SIG we are now publishing Vagrant boxes for CentOS Stream 9 to https://cloud.centos.org/centos/9-stream/x86_64/images/ * 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 ------- * All things database because it practically blocked everything (ongoing) -- Enable having various sub-commands in the first place to be able to do other things than just run the app -- Add one that sets up an empty database with tables from the model -- Prepare database schema migrations -- Test synchronous and asynchronous DB operations * Implement not-yet-functional (see above) API endpoints for users, physical nodes and virtual nodes (ongoing) * Write an Ansible role to deploy Duffy, set up database and fetch playbooks from their repos (ongoing) ## FCOS OpenShift migration Goal of this Initiative ----------------------- Move current Fedora CoreOS pipeline from the centos-ci OCP4 cluster to the newly deployed fedora infra OCP4 cluster. Updates ------- * Work complete, handed over to the FCOS team ## 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 ------- * Fedora s390x builder migration was successful, unblocking epel9 * Productive meetings with Terry Bowling and Eric Hendricks refining the EPEL “feature” and planning future collaboration Kindest regards, CPE Team _______________________________________________ infrastructure mailing list -- infrastruct...@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastruct...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
