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 rendered markdown, check the post on Fedora community blog (waiting for approval, will work later): https://communityblog.fedoraproject.org/cpe-weekly-update---week-of-november-1st---5th/ # 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 (Advance Reconaissance Crew), which is a subset of the team, investigates possible initiatives that CPE might take on. Update ------ * Mini-initiative for docs ( https://pagure.io/fedora-infrastructure/issue/9892) migration going well * ARC is now focused on Bodhi improvements! ### Fedora Infra * F35 is out smoothly! * openqa power9 box is back up and working along with it’s mgmt interface * 67 issues, should go down a bit next week * 17 open ansible PR’s, should be 0 next week ### CentOS Infra including CentOS CI * Business as usual ### Release Engineering * Issue cleanup in the releng tracker * 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 ------- * Stream 9 mirror links on the website ( https://www.centos.org/centos-stream/#tab-3)! * Stream 9 CI for SIGs has aarch64 boxes * Brainstorming around c8s and c9s processes getting closer together * Working on cleaning up old qcow2 images and old RPMs * Finishing up DistroBuildSync for ELN * Finishing up Content Resolver buildroot integration * Business as usual ## Datanommer/Datagrepper V.2 Goal of this Initiative ----------------------- The datanommer and datagrepper stacks are currently relying on fedmsg which we want to deprecate. These two applications need to be ported off fedmsg to fedora-messaging. As these applications are 'old-timers' in the fedora infrastructure, we would also like to look at optimizing the database or potentially redesigning it to better suit the current infrastructure needs. For a phase two, we would like to focus on a DB overhaul. Updates ------- * Import still running! (20%) ## 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 ------- * CI: Dependabot, enable workflow dispatch to re-run tests * Work in progress: - Database models: a diagram and code - Logging (expletive deleted) - Configuration framework ## 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 ------- * Pull request (https://pagure.io/fedora-infra/ansible/pull-request/839#), which creates project, group, rolebindings to permit the FCOS team access to the OCP4 staging cluster in order to deploy the pipeline, merged ## 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-next configured in koji * Multiple tools configured/updated to support epel9/epel9-next (fedpkg, fedscm-admin, robosignatory, distribution-gpg-keys, mock-core-configs, etc.) * Blocked waiting for migration of Fedora s390x builders to z15 (scheduled for 2021-11-09) * Meetings with multiple stakeholders and potential contributors to plan future work * EPEL docs migrated from Fedora wiki to docs.fp.o ( https://docs.fedoraproject.org/en-US/epel/) Kindest regards, CPE Team
_______________________________________________ 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
