devel July 2022

devel@lists.centos.org

29 participants
28 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

Alternate Images - Proposed SIG
by Troy Dawson 04 Aug '22

04 Aug '22

Following the CentOS "Setting up a new SIG"[1] instructions I am opening a new topic about creating a new CentOS SIG. I have initially filled out several sections that are in other SIG pages. These are all open for discussion. Goals: The Alternate Images SIG's goal will be to build and provide alternate iso images for CentOS Stream. What is in Scope: - Live Images (Previously known as LiveDVD, LiveCD) -- Examples: --- Live Desktops (KDE / GNOME / XFCE / Mate ) --- Live Rescue - Alternate Install Images -- Examples: --- Minimum install iso (doesn't need the network, but almost as small as the boot.iso) --- KDE install iso (has epel enabled, and packages to install a working kde desktop) - Repo's that are compatible with CentOS Stream, and follow the Fedora licensing policy. What is not in Scope: - Containers - Raw / QCow / AWS - Iso images that are bigger than 4 Gig. (This number can be adjusted after the SIG is formed) - Repo's that are not compatible with CentOS Stream, or do not follow the Fedora licensing policy. Collaboration: We plan on working with various Desktop SIG's, the Fedora minimization team, and any other group that wants custom iso's. Deliverables: - Documentation along with configuration (kickstarts and scripts) that will allow members to create their alternate images. - Alternate images in a publically downloadable area -- Images will be rebuilt, or retired, a minimum of every three months. Leadership: I (Troy Dawson) will be the initial Lead of the SIG. After (or while) the SIG is formed we will decide if we want a co-chair leadership and/or how often the leadership is elected. Troy Dawson [1] - https://wiki.centos.org/SpecialInterestGroup#Setting_up_a_new_SIG

8 15

CPE Weekly Update - Week 30 2022
by Michal Konecny 29 Jul '22

29 Jul '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: 25th July - 29th July 2022 If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-30-2022/ # 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. Link to planning board: https://zlopez.fedorapeople.org/I&R-2022-07-27.pdf Link to docs: https://docs.fedoraproject.org/en-US/infra/ Update ------ ### Fedora Infra * New Fedora Media Writer release (mostly translation fixes) 5.0.2 * Rabbitmq cluster instability last week due to both ocp3 and ocp4 clusters running monitor-gating and them obsoleting each other over and over. ;( * Worked around redhat.com SPF issue by accepting email from redhat.com, expanding fedoraproject.org alias and sending it right back out through redhat.com mx to deliver. ### CentOS Infra including CentOS CI * Preparing duffy.ci migration ([now announced for next week](https://lists.centos.org/pipermail/ci-users/2022-July/004582.html)) ### Release Engineering * F37 Mass rebuild finished ## 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 ------- * Imported c8s modules into the new mbs. * CentOS Linux 7.9 ISOs are respun ## 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 is up to 6986 (+378) packages from 3137 (+54) source packages * Backported fix for CVE-2021-21419 to EPEL8's [python-eventlet](https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-0… * Retired several rawhide branches of EPEL-only packages * Updated KDE (5.24.6) is available in epel9-next and epel8-next testing. * Will not go out to regular epel until RHEL 8.7 and 9.1 * Working on an EPEL survey that will go out in August ## FMN replacement Goal of this initiative ----------------------- FMN (Fedora-Messaging-Notification) is a web application allowing users to create filters on messages sent to (currently) fedmsg and forward these as notifications on to email or IRC. The goal of the initiative is mainly to add fedora-messaging schemas, create a new UI for a better user experience and create a new service to triage incoming messages to reduce the current message delivery lag problem. Community will profit from speedier notifications based on own preferences (IRC, Matrix, Email), unified fedora project to one message service and human-readable results in Datagrepper. Also, CPE tech debt will be significantly reduced by dropping the maintenance of fedmsg altogether. Updates ------- * Basic repo structure in place (Python + JS side), more boilerplate work ongoing * Fedora-messaging schemas checkup commenced Kindest regards, CPE Team

1 0

Planned outage : Duffy CI infra migration phase 1 on August 1st
by Fabian Arrotin 27 Jul '22

27 Jul '22

As previously announced in June (see https://lists.centos.org/pipermail/ci-users/2022-June/004547.html and also https://www.youtube.com/watch?v=aqgs-3NnRmA), we'll migrate existing Duffy API service to the new Duffy v3, starting with Phase 1 . Migration is scheduled for """"Monday August 1st 7:00 am UTC time"""". You can convert to local time with $(date -d '2022-08-01 07:00 UTC') The expected API downtime will be under the 60 seconds (DNS TTL). Worth knowing: - new duffy api (in legacy mode) has currently less available nodes, but that will be resolved during the day (see below) - we'll have to wait ~6h (default maximum "lease" time for a test node) to be able to let new duffy api reinstall older seamicro nodes and so be available in the new duffy v3 pool (transitioning from old to new duffy pool) - currently running jobs will continue so to work, but when you'll hit new duffy api endpoint (DNS switch) to "return nodes" it will just answer that session doesn't exist (new one) but it's safe to ignore As soon as new duffy API is available you'll already be able to switch your workflow to new the Duffy API and so use the new features. Tenants/users documentation about how to interact with Duffy is available on https://sigs.centos.org/guide/ci/ (see the Duffy part of that documentation) That means that switching to EC2 nodes will be directly possible. During the day we'll tune the duffy nodepool configuration based on usage metrics. IMPORTANT remark : *only* projects/tenants that opted-in in the last 45 days are currently migrated (api and ssh keys), so if you haven't (yet), you can still opt-in, otherwise all your requests for duffy ephemeral nodes will be declined by new duffy api service next monday. In case of troubles, both Pedro (nick phsmoura) and myself (nick arrfab) will be also present in the #centos-ci irc channel on irc.libera.chat the whole day. Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

Re: [CentOS-devel] CentOS-devel Digest, Vol 209, Issue 19
by jlmartinez＠netwizzy.es 26 Jul '22

26 Jul '22

Hola, Estaré fuera de la oficina así que para cualquier cuestión por favor, dirígete a María José de Vicente mjdevicente(a)netwizzy.es. Muchas gracias y un saludo. Hello, I will be out of the office. Meanwhile, please contact María José de Vicente mjdevicente(a)netwizzy.es. Best regards.

1 0

Question on absence of SHA1 in OpenSSL 3.0/Centos 9 stream.
by Nickolay Olshevsky 25 Jul '22

25 Jul '22

Hi, Having SHA1 support removed from the OpenSSL in Centos 9 stream, it is still displayed in the list of supported digest, via CLI `openssl dgst -list` and via library API calls like `EVP_get_digestbyname()` and `EVP_MD_do_all_sorted()`. However, in some cases it would be desirable to know whether particular OpenSSL installation supports SHA1. So, the question - is it done this way by intention and I should look for some workaround, or it is something to get fixed in further package updates? Thanks! -- Best regards, Nickolay Olshevsky o.nickolay(a)gmail.com

2 1

Re: [CentOS-devel] CentOS-devel Digest, Vol 209, Issue 18
by jlmartinez＠netwizzy.es 25 Jul '22

25 Jul '22

1 0

Re: [CentOS-devel] CentOS-devel Digest, Vol 209, Issue 17
by jlmartinez＠netwizzy.es 24 Jul '22

24 Jul '22

1 0

Re: [CentOS-devel] CentOS-devel Digest, Vol 209, Issue 16
by jlmartinez＠netwizzy.es 23 Jul '22

23 Jul '22

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel July 2022