devel October 2022

devel@lists.centos.org

21 participants
16 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

Gauging interest in Discourse
by Shaun McCance 02 Nov '22

02 Nov '22

Hi all, You might be aware that there is a CentOS category on the Fedora Discourse instance: https://discussion.fedoraproject.org/c/centos/71 There have been some discussions about having a dedicated Discourse instance for CentOS. Discourse has a lot of advantages, such as better moderation and integration with our accounts system. But I understand that many people are comfortable with their existing workflows. There's no point in running Discourse if it doesn't get enough buy-in. So I'm asking for input on using Discourse for various things: * Project announcements, like events, meetings, and infra changes * Activity reports, such as for SIGs and events * User support, replacing forums.centos.org * Development of Stream itself, basically centos-devel * Development of stuff inside SIGs * Replacement for the comments section of the blog * Alternatively, just replacing the blog entirely * Something else I'm not thinking of Thanks, Shaun McCance CentOS Community Architect Red Hat Open Source Program Office

5 18

CPE Weekly Update – Week 43 2022
by Lenka Segura 28 Oct '22

28 Oct '22

*Hi everyone,This is a weekly report from the CPE (Community Platform Engineering) Team.The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update-week-43-2022 <https://communityblog.fedoraproject.org/cpe-weekly-update-week-43-2022>/.If you want to receive weekly reports by emails in the future, please subscribe to either https://communityblog.fedoraproject.org/ <https://communityblog.fedoraproject.org/> or https://discussion.fedoraproject.org/c/news/commblog/61 <https://discussion.fedoraproject.org/c/news/commblog/61>. We will stop sending them in 2023.Regards,CPE Team*

1 0

Re: [CentOS-devel] kernel-5.14.0-171.el9.x86_64 / Not bootable (EFI) after Firmware update
by Leon Fauster 28 Oct '22

28 Oct '22

Am 08.10.22 um 16:24 schrieb Leon Fauster: > Hey folks, I wonder if anyone also suffers from the following: > > I updated the BIOS/Firmware of a DELL notebook from 1.8 to 1.9. and > after this the latest C9S > > kernel-5.14.0-171.el9.x86_64 > > can't be booted anymore (secure boot on) but the two older ones do boot: > > kernel-5.14.0-165.el9.x86_64 > kernel-5.14.0-168.el9.x86_64 > > The grub error message when trying to boot kernel-5.14.0-171.el9.x86_64 > looks like: > > error: ../../grub-core/kern/efi/sb.c:183:bad shim signature. > error: ../../grub-core/loader/i386/efi/linux.c:259:you need to load the > kernel first. > > I wonder how this happens. The firmware is classified as bug-fix update. > > Not sure if DBX list was update. fwupdmgr shows "Current version: 83" > If so, it does not make sense that older kernels can be used to boot the > system. So, a big question mark how to solve this issue? Any hints ...? > > > # sha256sum /boot/efi/EFI/BOOT/BOOTX64.EFI > 3ae459e79408b5287ce70c5b86ddcc92c243c7442d6769a330390598b7a351b1 > /boot/efi/EFI/BOOT/BOOTX64.EFI > It seems that the kernel-5.14.0 of the release 17X-series do not get signed with the CentOS key anymore! https://bugzilla.redhat.com/show_bug.cgi?id=2138019 TLDR: /boot/vmlinuz-5.14.0-16* versus /boot/vmlinuz-5.14.0-17* shows The signer's common name is CentOS Secure Boot Signing 201 versus The signer's common name is Red Hat Test Certificate Is this issue already receiving the right attention? -- Thanks Leon

1 0

CPE Weekly Update - Week 42 2022
by Michal Konecny 21 Oct '22

21 Oct '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/ cpe-weekly-update---week-42-2022/ <https://communityblog.fedoraproject.org/?p=11495>. If you want to receive weekly reports by emails in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Regards, CPE Team

1 0

Renaming Dojos
by Shaun McCance 19 Oct '22

19 Oct '22

Hi all, The CentOS Board is looking at renaming Dojos, our series of free mini- conferences. Please give your input on this Discussion post: https://discussion.fedoraproject.org/t/renaming-centos-dojos/43351 Note that Fedora and CentOS share an accounts system, so if you have a CentOS account, you already have a login for Fedora Discussion. Thanks, Shaun

1 0

October board meeting recording and office hours
by Shaun McCance 17 Oct '22

17 Oct '22

Hi all, I've uploaded the recordings of last week's board meeting: https://youtu.be/FA0ddn-IWes If you'd like to discuss any issues with the board, we'll have an open board office hours this Thursday, October 20, at 14:00 UTC: https://us06web.zoom.us/j/87623425120 Thanks, Shaun

1 0

EPEL 8 Modules get the axe on Halloween 2022
by Troy Dawson 14 Oct '22

14 Oct '22

When EPEL-8 was launched, it came with some support for modules with the hope that a module ecosystem could be built from Fedora packages using RHEL modules as an underlying tool. This has never happened and we have ended up with a muddle of modular packages which will 'build' but may not install or even run on an EL-8 system. Attempts to fix this and work within how EPEL is normally built have been tried for several years by different people but have not worked. At this point we are saying that this experiment with modules in EPEL has not worked and we will focus our resources on what does work. Schedule of EPEL 8 Module Retirement: Next Week: - epel-release will be updated. -- epel-modular will set enabled = 0 -- epel-modular full name will have "Deprecated" in it October 31 2022: - The EPEL 8 modules will be archived and removed. -- The mirror manager will be pointed to the archive. - Packagers will no longer be able to build EPEL 8 modules. After October 31st (Actual date to be determined): - epel-release will be updated again. -- epel-modular repo configs will be removed. Questions and Answers: Question: Will I still be able to access the modules after October 31st? Answer: It is not recommended, because the modules will not get any security or bug fixes, but yes. They will be in the Fedora archives, and the mirror managers will point at them. Question: What will you be dressed as on Halloween? Answer (Troy): A Penguin EPEL Steering Committee [1] - https://pagure.io/epel/issue/198

2 3

CentOS Cloud SIG meeting minutes (2022-10-13)
by Joel Capitao 13 Oct '22

13 Oct '22

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2022-10-13) ====================================================== Meeting started by jcapitao at 15:01:41 UTC. The full logs are available athttps://www.centos.org/minutes/2022/October/centos-meeting.2022-10-13-15.… . Meeting summary --------------- * roll call (jcapitao, 15:01:54) * Documentation update (jcapitao, 15:05:27) * LINK: https://lists.centos.org/pipermail/centos-devel/2022-August/120541.html (jcapitao, 15:07:59) * LINK: https://wiki.centos.org/SpecialInterestGroup/Cloud (lorbus, 15:08:26) * ACTION: Cloud SIG to migrate its documentation on https://sigs.centos.org/ (jcapitao, 15:12:29) * Meetup heads up (jcapitao, 15:13:22) * OKD/SCOS (CentOS Stream CoreOS 9) update (jcapitao, 15:22:47) * LINK: https://github.com/openshift/installer/pull/6443 has to merge (it's already been approved and passed e2e testing) (lorbus, 15:24:16) * The OKD/SCOS MVP release is imminent, and announcement will go out in the next days (lorbus, 15:35:23) * LINK: https://issues.redhat.com/secure/RapidBoard.jspa?rapidView=15137 (lorbus, 15:41:17) Meeting ended at 15:59:22 UTC. Action Items ------------ * Cloud SIG to migrate its documentation on https://sigs.centos.org/ Action Items, by person ----------------------- * **UNASSIGNED** * Cloud SIG to migrate its documentation on https://sigs.centos.org/ People Present (lines said) --------------------------- * jcapitao (38) * lorbus (34) * amoralej (28) * spotz (15) * centguard (5) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel October 2022