devel June 2022

devel@lists.centos.org

28 participants
22 discussions

Few questions on cloud images
by Pino Toscano 06 Jun '23

06 Jun '23

Hello, I have few questions related to the cloud images provides for c8s and c9s, i.e.: - https://cloud.centos.org/centos/8-stream/x86_64/images/ - https://cloud.centos.org/centos/9-stream/x86_64/images/ 1) I see the c9s images are regularly updated, while the c8s images not; is this wanted, or simply a mistake/miss somewhere? If so, will they be kept up-to-date just like the c9s images? 2) are the Vagrant images there officially supported? Let's say you use one, and find a bug; then check on a "classic" installation (baremetal/VM), and the bug isn't there; can users report problems in those cases? 3) would it be possible to have either unversioned or "-latest" symlinks for the latest versions of all the files (i.e. images, checksums, etc)? This way, it will be much easier for users to fetch the latest versions with no need to change URLs frequently. Of course, the assumption is that users of this are always willing to use the latest version. Thanks! -- Pino Toscano

7 14

Proposal: CentOS Public Board Meetings
by Rich Bowen 07 Jan '23

07 Jan '23

In January of 2021, the CentOS Board of Directors opened our monthly meetings to all SIG chairs, in a first step towards more transparent governance. We wanted to see how the larger audience changed the meeting dynamics, if at all, as well as welcoming a broader pool of voices. We are now ready for the second part of this process. Starting in the August meeting, we will be inviting the entire CentOS community to attend these meetings. Due to the nature of the Internet, we won’t be simply publishing the meeting URL, as this often leads to disruptive behavior in meetings, as I am sure many of you have experienced. Rather, in the week before the meeting, we’ll send, to this list, a way to request an invitation to the meeting. In this way, we hope to limit the incidence of such disruptions, while also making the meeting available to anyone who wishes to attend. We will be working on the rules of engagement for these meetings, but they will be, at minimum: * Wait to be recognized by the Chair before speaking * Respect the Chair when told your time to speak is over - this will allow us to remain on agenda, and complete the meetings in the allotted time * In the event that there are Board-confidential topics, these will be put at the end of the meeting, in Executive Session, and guests will be asked to leave. We hope to minimize these items, but they do sometimes happen. The most common scenarios in which this may happen are personnel issues, or information that Red Hat wishes to share with the Board, but is not yet public. * Muting of participants, or, in extreme situations, ejection from the meeting, is at the sole discretion of the Chair. * Meetings will be recorded, and published to YouTube (possibly with edits/redactions, as approved by the Directors). Thus, by joining the meeting you consent to have your presence at the meeting, and anything you say during the meeting, made public. Because there will seldom be time for Q&A during the meeting itself, we plan to add a post-meeting IRC office hours session for followup questions. This will probably be scheduled for a week after the board meeting, to allow time to publish meeting minutes We welcome your comments about the above proposal, and thank you all for your patience as we implement these changes to our governance process.

8 27

Board Nominations Requested
by Shaun McCance 11 Jul '22

11 Jul '22

** Please read this entire email before responding with nominations. ** We have a process, and the process is important. As per our governance docs: https://www.centos.org/about/governance/board/ Every six months, half of our directors are asked if they wish to continue in their seats or step down. This time, we will have one seat to fill. Tru Huynh has indicated to the board his intent to step down. Tru has been a part of this community for a long time, and we all deeply appreciate the work he's done both on the board and across the entire project. We are asking you, the CentOS community, for nominations for who should fill Tru's seat. Note that the vote on who will fill his seat is held by the board itself, but nominations are open to the entire community. If you would like to nominate someone (or self-nominate), please use this Google form: https://forms.gle/WsknUVnPL5zbWcSK6 Please DO NOT send nominations to this list. As this is not a public vote, we don't to give the impression of a popularity contest with public nominations. We also want to avoid any shaming if someone is nominated and is not seated, or chooses not to accept. I will ensure that each nominee is willing and able to serve, and the board will consider them and select the next director from the list. If you wish to nominate someone, you should consider the list of director requirements and recommendations listed at: https://www.centos.org/about/governance/director-requirements/ Thank you for your thoughtful consideration and participation in this process. -- Shaun, for the CentOS Board of Directors

5 9

Changes on CentOS CI and next steps
by Camila Granella 11 Jul '22

11 Jul '22

*TL;DR: CentOS CI is going hardwareless and if you wish your project remains using it, we need your opt-in by August 2022. There is a Dojo Summer 2022 <https://wiki.centos.org/Events/Dojo/Summer2022> session happening on Thursday, June 17th, that will explain further technical details. * Hello everyone, As many of you know, since the beginning of this year we have been reevaluating the future of CentOS CI, as currently the hardware being used for it is out of warranty. This is due to the fact that CentOS CI came from community donations of hardware which were maintained in a best effort manner by our team. With no warranties, when the physical machine dies we have no means to replace it. Right now though, our hardware, due to a lack of warranty, will not be moved with the upcoming data center changes due to data center requirements to have in warranty hardware for supportability. We decided to take this opportunity to modernize our current infrastructure, pushing it to a hybrid cloud environment. Duffy CI will become the main tool from now on, so that we can support the CI workflow and best practices on cloud and for this reason, the current hardware infra will no longer be available soon. However, as an effort to continuously provide resources and support CI best practices for projects, our team is adapting Duffy CI so that we can maintain most of the characteristics of our current, physical-based offering. At the technical level, what does that mean for you, CI tenants? - A new Duffy API service will replace the existing one: while it will be running in compatibility/legacy mode with the previous version, you will need to adapt your workflow to the new API, but more details below - We will transition to AWS EC2 instances for the aarch64 and x86_64 architectures by default, with a (limited) option to request “metal” instances for projects requiring virtualization for their tests (like KVM/vagrant/etc) - We will keep a (very small) Power9 infra “on-premise” (AWS does not support ppc64le) for the ppc64le tests (available through a dedicated VPN tunnel) - The existing OpenShift cluster will be also decommissioned and a new one (hosted in AWS, so without an option to run kubevirt operator nor VMs) will be then used (you will have to migrate from one to the other) With that being said, tenants can start preparing for the changes to happen with the maximum deadline of the end of December 2022 wherein at this point, Duffy API legacy mode will be removed. You are required to opt-in if you and/or your team want to use Duffy CI. Projects will only be migrated if they reply to this email confirming that they wish to proceed. Worth knowing that not opting in means that your API key will not be migrated and so all your requests to get temporary/ephemeral nodes will be rejected by the new Duffy API. The maximum decommission deadline of the current hardware infrastructure is December 12th, 2022 and the new Duffy CI will go live in August 2022, so please, complete your migration process by the end of CY22. Reminders of deadlines and of the opt-in requirements will be sent monthly, but your confirmation of opt-in is required by August 2022. When approaching December, reminders about deadlines frequency will increase so that we can ensure effective communication throughout the process. Here are the steps in which we will migrate CI Infra: Phase 1 - Deploy Duffy V3 (August 2022) - Deploy in legacy/compatibility mode, so existing tenants (that opted in !) can still request duffy nodes the same way (like with 'python-cicoclient') : no change at tenants side, and exactly same hardware for tests (transparent migration) - New Duffy API endpoint becomes available, and tenants can start adapting their workflows to point to new API (new ‘duffy-cli’ tool coming, with documentation) - Bare metal and VMs options will be available already through the new API (x86_64, aarch64, ppc64le) Phase 2 - Hybrid Cloud (October 2022) - Legacy/compatibility API endpoint will handover EC2 instances instead of local seamicro nodes (VMs vs bare metal) - Bare metal options will be available through the new API only - Legacy seamicro and aarch64/ThunderX hardware are decommissioned - Only remaining "on-premise" option is ppc64le (local cloud) Phase 3 - Decommission (December 2022) - Legacy/compatibility API deprecated and requests (even for EC2 instances) will no longer be accepted - All tenants that opted in will be using only EC2 for aarch64/x86_64 and on-premise cloud for ppc64le OpenShift new deployment planning and timeline To be defined (deadline for planning and timeline: end of June 2022) Do not hesitate to reach out if you have any questions. It is worth knowing that there will be a dedicated session about the Future of CentOS CI infra at the next CentOS Dojo happening on June 17h (check Dojo Summer 2022 <https://wiki.centos.org/Events/Dojo/Summer2022>). That session will be recorded and then available on Youtube but if you have any questions. Feel free to join the CentOS Dojo and reach out to us! Best regards, -- Camila Granella Associate Manager, Software Engineering Red Hat <https://www.redhat.com/> @Red Hat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/>

3 3

New SIG idea - Stream Live Images / Alt Installs
by Troy Dawson 01 Jul '22

01 Jul '22

Before I get all worked up about this idea, I want to see if it is feasible, and if there is any interest in it. I'd like to start a SIG where we create images (Live and Install iso's) that are based on both CentOS Stream and EPEL together. For live images we could have a CS9-KDE-Live.iso, CS9-XFCE-Live.iso, CS9-GNOME-Live.iso, or even a large CS9-ALL-DESKTOPS-Live.iso. For install images we could have CS9-minimal.iso, maybe a KDE, or others. I mainly want the minimal iso so I don't have to download the massive 8 Gig DVD if I want just the minimum, but don't want to do a network install. So, my two questions are. Would this be possible on the current CentOS Stream infrastructure? Would anyone else want a SIG like this? Troy

5 5

Stream 9: where is the repo file for SIGs/.../centos-plus?
by Anthony Alba 29 Jun '22

29 Jun '22

I unpackaged all the centos-release*rpm files I could find, but couldn't find one that references SIGs/core/$basearch/centos-plus. Regards Anthony

2 1

Centos Stream 8 vagrant images not regularly updated
by Nikolaos Moumoulidis 24 Jun '22

24 Jun '22

Hi all, There was a thread created by a colleague of mine a few months ago ( https://lists.centos.org/pipermail/centos-devel/2022-January/120156.html) regarding the CS8 vagrant images not being upgraded regularly in either https://cloud.centos.org/centos/8-stream/x86_64/images/ or https://app.vagrantup.com/centos/boxes/stream8 and the reply was a new process will be created for this to happen monthly. This hasn't happened yet (I understand, we're all busy), so I wanted to check on the status of if/when it will. Ideally https://app.vagrantup.com/centos/boxes/stream8 would be the best place since the '-latest' suffix scheme seemed to not be feasible for now, but even updated images in https://cloud.centos.org/centos/8-stream/x86_64/images that we could manually update the url to every now and then would work. Thanks, Nikos

1 0

CPE Weekly Update – Week 25 2022
by Akashdeep Dhar 24 Jun '22

24 Jun '22

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/). Week: 20th - 24th June 2022 If you wish to read this in form of a blog post, check the post on the Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-25-2022/ Highlights of the week Infrastructure & Release Engineering Goal of this Initiative The 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. Link to planning board: https://zlopez.fedorapeople.org/I&R-2022-06-22.pdf Link to docs: https://docs.fedoraproject.org/en-US/infra/ Update Fedora Infra - Most apps have moved over to the OpenShift4 cluster. Hopefully, the transition should be finishing up this week. - Wiki: All upgraded in production and working (thanks Ryan!) - Resultsdb: All moved over to OpenShift 4 in prod and working (thanks Leo!) - Business proceeding as usual CentOS Infra including CentOS CI - Kerberos settings switch for git.centos.org (kcm on el8 vs keyring on el7) for lookaside upload CGI <https://pagure.io/centos-infra/issue/811> [1] - Issue on iad2 hosted reference mirror <https://pagure.io/centos-infra/issue/812>[2] (epel.next and mirrormanager), all fixed now - Duffy CI ongoing tasks and deployments (all announced) - Equinix nodes migration <https://pagure.io/centos-infra/issue/816>[3] (on their request) - Business proceeding as usual Release Engineering - Compose-tracker updated to f36 in staging, production happening tomorrow - Python 3.11 merged to rawhide - MBS randomly fails to process builds - Rawhide compose failures recently (syslinux retirement, then python 3.11 merge) all fixed now - Business proceeding 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 - CentOS Stream 8: Manually keeping regular RPMs and module RPMs updated on the koji.stream server as current updates are composed and released. CentOS Duffy CI Goal of this Initiative 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. Updates - Release version 3.2.1 - Docs, docs, docs and a Dojo Package Automation (Packit Service) Goal of this initiative Automate RPM packaging of infra apps/packages Updates - Mostly business as usual - Thanks again to all who are reviewing our PRs - Most of our GitHub critical apps are enabled now or close to being enabled Flask-oidc: oauth2client replacement Goal of this initiative 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. Updates: - POC working using authlib, tidying up code to prepare to submit a PR back to upstream 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 a build system, Bugzilla instance, updates manager, mirror manager and more. Updates - This week we have 6442 (+127) packages, from 2882 (+76) source packages - Containerd and puppet retired from EPEL7 because of upstream EOL and multiple CVEs. - Caddy was updated, fixing 4 CVEs in EPEL9 *Index* [1] https://pagure.io/centos-infra/issue/811 [2] https://pagure.io/centos-infra/issue/812 [3] https://pagure.io/centos-infra/issue/816 Thanks and Regards, Akashdeep Dhar (he/him), Objective Representative, Fedora Council Red Hat Community Platform Engineering t0xic0der(a)fedoraproject.org akashdeep(a)redhat.com

1 0

[REPORT] Quarterly Report - CentOS Automotive SIG
by Jeffrey Osier-Mixon 24 Jun '22

24 Jun '22

June 2022 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat - acting chair _____________________________________ Membership update This SIG does not have a formal membership process. The mailing list currently has 94 subscribers representing at least 30 organizations, though not all subscribers use corporate emails and some are participating as individuals. _____________________________________ Releases in the most recent quarter (or most recent release, if none in that quarter) The SIG provides a new distribution: Automotive Stream Distribution (AutoSD), a CentOS Stream derivative designed specifically around the needs of an automotive OS, and transparently the upstream project for Red Hat's eventual in-vehicle OS product. AutoSD has been downloaded and used by several organizations who have commented or asked for help, so we know it is getting some traction though of course we don't have exact metrics on usage. _____________________________________ Health report and general activity narrative. The SIG has had two public meetings per month, one formal and one informal "office hours", each with 25-40 attendees, with visible participation from 7-10 separate organizations. This SIG is intended to be a community effort with contributions and shared benefits from all participants. All formal meetings are recorded and posted on this page: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings Several Red Hat employees made the initial contributions to the project as well as the infrastructure required to build and test it. We now occupy a gitlab repository building software regularly using CI, with build instructions provided on the documentation page at https://sigs.centos.org/automotive/ . Sample images are present and downloadable along with customization and build instructions. This is a high-level summary of current activity: - All work has migrating to a CentOS namespace within GitLab in order to cement our intention as a community project: https://gitlab.com/centos/automotive - CI/CD infrastructure is in place - Firmware size has been reduced - Encryption is available via LUKS - a Linux chroot is being worked on for Android devices - manifests now enable EFI runtime services - Lookaside cache structure - Downloadable images are available: https://autosd.sig.centos.org/ - Documentation has been greatly expanded with both community and corporate contributions: https://sigs.centos.org/automotive/ - Documentation now includes detailed contribution guidelines: https://sigs.centos.org/automotive/contributing/contributing-to-auto-sig-re… - Ongoing discussions within the meetings have centered around supported hardware and expectations for documentation - A new meetings page contains recordings of all meetings: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings - Synchronous communications have moved from IRC to Matrix thanks to some help from Fedora: https://app.element.io/#/room/#centos-automotive-sig:fedoraproject.org _____________________________________ Issues for the board to address, if any None, keep up the excellent work :) Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

Dojo at DevConf, August 17
by Shaun McCance 21 Jun '22

21 Jun '22

Thanks to everybody that attended our online Summer Dojo. We are holding an in-person Dojo on August 17 at Boston University. This is the day before the main track of DevConf.US, at the same venue. https://wiki.centos.org/Events/Dojo/DevConfUS2022 The call for presentations is open. We look forward to talks from the entire Enterprise Linux ecosystem, from how it's built to how it's used. We have both 20-minute and 40-minute talk slots. https://forms.gle/QjGki4whyWTvnD4q9 (If you previously tried to submit a presentation and didn't have permission, it's because I forgot to change the settings to allow submissions from outside Red Hat. Sorry. It's fixed now.) Thanks, Shaun McCance CentOS Community Architect Red Hat Open Source Program Office

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2022