devel December 2021

devel@lists.centos.org

31 participants
22 discussions

forums + portal for {lang}.centos.org sites
by Karanbir Singh 17 Aug '24

17 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

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

CS8 repos / repomd.xml.asc
by Leon Fauster 02 Mar '22

02 Mar '22

Hey. It seems that the mirrors do not have the repomd.xml.asc file. Does the main repo provide it? -- Thanks Leon

5 8

Re: [CentOS-devel] Is advanced-virt (Virtualization SIG) not relevant anymore with latest CentOS Stream 8?
by Igor Raits 01 Feb '22

01 Feb '22

Hi Danilo, Thanks for the very quick response! And thanks Sandro for including relevant people (as it was hard for me to find appropriate emails). Have a great day, On Tue, Nov 16, 2021 at 2:04 PM Danilo de Paula <ddepaula(a)redhat.com> wrote: > Yes, until RHEL 8.5 the latest-and-greatest virt packages used to be > shipped within Advanced Virtualization. But since AV packages are part of > RHEL now, there's no need for updating the SIG anymore because RHEL has the > most updated packages and, by consequence, c8s should have those builds too. > > > > On Tue., Nov. 16, 2021, 7:25 a.m. Sandro Bonazzola, <sbonazzo(a)redhat.com> > wrote: > >> +Eduardo Lima <etrunko(a)redhat.com> +Danilo Cesar Lemes de Paula >> <ddepaula(a)redhat.com> >> >> Il giorno mar 16 nov 2021 alle ore 12:52 Igor Raits <igor.raits(a)gmail.com> >> ha scritto: >> >>> Hello, >>> >>> I've noticed that the latest c8s repos ship libvirt/qemu-kvm (and other >>> related things) newer than the advanced virtualization repository… which >>> brings me to a question if it is still worth using those builds or not? >>> >>> I've been trying to dig into some mailing list conversations (which are >>> pretty much non-existent at this point) and IRC meetings (which I did not >>> see in October, but found one in November[1]). Found only mention that >>> libvirt/qemu will not be available for power arches since c9s and that's >>> what probably virt sig will build (if my understanding of meeting minutes >>> are correct). >>> >>> Any piece of information would be very helpful :) >>> >>> >>> [1] >>> https://www.centos.org/minutes/2021/November/centos-meeting.2021-11-03-17.0… >>> >> >> >> -- >> >> Sandro Bonazzola >> >> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >> >> Red Hat EMEA <https://www.redhat.com/> >> >> sbonazzo(a)redhat.com >> <https://www.redhat.com/> >> >> *Red Hat respects your work life balance. Therefore there is no need to >> answer this email out of your office hours.* >> >> >>

3 4

CentOS Linux 8 and SIGs content removal plan (please read)
by Fabian Arrotin 04 Jan '22

04 Jan '22

As you’re all aware, and per https://www.centos.org/centos-linux-eol/ , CentOS Linux 8 is going EOL end of this month, and content will just remain available on mirror network until January 31st. After that date, CentOS Linux 8 repositories will be removed from mirror network, and mirrorlist will start answering “invalid release”, so no way to easily install any rpm component. But what about SIGs content that was built for/against CentOS Linux 8 ? (basically other repositories that you can see under http://mirror.centos.org/centos/8/ but that aren’t coming from centos linux 8 distro itself ? As soon as CentOS Stream 8 was announced, we offered the possibility to all SIGs to opt-in and build for/against Stream 8, and so have their repositories automatically pushed to http://mirror.centos.org/centos/8-stream , as it was for /8/ . Most of the SIGs opted at that time to build in parallel for 8 and 8-stream, while some decided to just start building against/for 8-stream directly (and of course content built on 8-stream *should* just work fine, and reverse is also true) But some months ago, community members asked (https://pagure.io/centos-infra/issue/400) if that was possible to continue building against/for el8, but so switching buildroot from centos 8 to RHEL 8, which was worked on and is now available. What does that mean for you, SIGs ? If you want (opt-in and so optional) continue to build for el8, just create a ticket on https://pagure.io/centos-infra/issues to ask your tags to build against RHEL 8 instead of CentOS Linux 8. You can do that whenever you want but before (for obvious reasons) end of January 2022 What if you don’t opt-in ? You SIG content will removed from mirror network, at the same time as CentOS Linux 8 content. So to recap : * End of january, *all* repositories listed under http://mirror.centos.org/centos/8/ will be removed (except for SIGs that opted-in for the ‘switch to RHEL 8 buildroot’ plan) * mirrorlist.centos.org will also start answering ‘invalid repo’ for SIG content, as it will be for CentOS Linux 8 itself * All SIGs tags for 8 will be locked down (except for SIGs that opted-in for the ‘switch to RHEL 8 buildroot’ plan) so no way to just tag-build (and so push anything) out -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

2 2

Moving SIG Guide to a new home
by Fabian Arrotin 31 Dec '21

31 Dec '21

Hi all, For some time we thought about moving the existing SIGGuide from the wiki (https://wiki.centos.org/SIGGuide) to a new place and have more collaboration from SIG[s] members to enhance/update/clarify the SIG guide. That's the reason why we had an infra ticket to track this (https://pagure.io/centos-infra/issue/543) Content was added to the specific git repo (https://git.centos.org/centos/sig-guide) and it's automatically rendered and available under https://sigs.centos.org/guide/ We'd like to get some feedback and we'll then just modify the wiki page to point to the new page. We'll also review and merge/accept PR against that doc, so it's also *yours* and shared between all SIGs :-) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

3 2

CPE to staff EPEL work
by Rich Bowen 18 Dec '21

18 Dec '21

We are pleased to announce that Red Hat is establishing a small team directly responsible for participating in EPEL activities. Their job isn't to displace the EPEL community, but rather to support it full-time. We expect many beneficial effects, among those better EPEL readiness for a RHEL major release. The EPEL team will be part of the wider Community Platform Engineering group, or CPE for short. As a reminder, CPE is the Red Hat team combining IT and release engineering from Fedora and CentOS. Right now we are staffing up the team and expect to see us begin this work from October 2021. Keep an eye on the EPEL mailing list[1] and the associated tracker as we begin this exciting journey with the EPEL community. [1] https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraprojec… [2] https://pagure.io/epel/issues

9 11

Outdated ca-certificates in CentOS 7 Vagrant box
by Alex Pircher 16 Dec '21

16 Dec '21

Hello all, the CentOS 7 Vagrant box (https://app.vagrantup.com/centos/boxes/7) uses outdated ca-certificates, which leads to errors. Can you please update ca-certificates. Thanks, Alex # wget https://www.centos.org/ --2021-10-15 15:46:38-- https://www.centos.org/ Resolving www.centos.org (www.centos.org) 81.171.33.201, 81.171.33.202, 35.178.203.231 Connecting to www.centos.org (www.centos.org)|81.171.33.201|:443... connected. ERROR: cannot verify www.centos.org's certificate, issued by ‘/C=US/O=Let's Encrypt/CN=R3’: Issued certificate has expired. To connect to www.centos.org insecurely, use `--no-check-certificate'. # yum update -y ca-certificates # wget https://www.centos.org/ --2021-10-15 15:51:09-- https://www.centos.org/ Resolving www.centos.org (www.centos.org) 81.171.33.201, 81.171.33.202, 35.178.203.231 Connecting to www.centos.org (www.centos.org)|81.171.33.201|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 24837 (24K) [text/html] Saving to: ‘index.html’ 100%[==================================================================================================>] 24,837 --.-K/s in 0.02s 2021-10-15 15:51:09 (1.16 MB/s) - ‘index.html’ saved [24837/24837]

2 2

CentOS Stream 8 : samba-4.15.2-2.el8
by Johnny Hughes 16 Dec '21

16 Dec '21

There is an issue with CentOS Stream 8 and the currently published samba-4.15.2-2.el8. I am working on a compose that removes that build from the repo. In the interim, if you need to perform an update before i get the new compose released .. place this: exclude=*4.15.2-2.el8* in your CentOS-Stream-AppStream.repo and CentOS-Stream-BaseOS.repo. I should have this fixed within in the next couple of hours. Thanks, Johnny Hughes

4 6

CPE Weekly Update – Week of December 13th – 17th
by Vipul Siddharth 16 Dec '21

16 Dec '21

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 form of a discourse post (or on our commblog), check the post on discussion.fp.o: https://discussion.fedoraproject.org/t/cpe-weekly-update-week-of-december-1… # 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. Update ------ ### Fedora Infra * Log4j CVE affects our Openshift 3, mitigated via [fix](https://access.redhat.com/solutions/6578441) * Deployed an Openshift Dedicated cluster on AWS still deciding * Lots of spam cleared off mailing lists ### CentOS Infra including CentOS CI * Various activities/preparation for CentOS Linux 8 EOL process * Proposal for SIGs to [switch to RHEL8](https://lists.centos.org/pipermail/centos-devel/2021-December/098779… * Preparing needed steps to clear content and remove it from mirrorlist * WIP for Meta group for SIGs, allowing to build+push their -release pkgs (not having to depend on CentOS Stream team for this) * Investigating [openshift template issue](https://pagure.io/centos-infra/issue/555) for newer deployed projects and jenkins * Log4j CVE impact analysis (impacting OCP 4 if Elasticsearch is used, which we are not using) * Stream MVBE infra : renewal process for internal TLS cert ## 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 ------- * Dealing with a slowdown in rpm signing * Continuing the development Content Resolver enhancements * Various cleanup and docs work at various places ## 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 ------- * Foundation for background tasks in place * Started work on authentication and the session workflow * CLI polish ## OSCI – Distrobaker monitoring Goal of this Initiative ----------------------- This initiative is to improve the Distrobaker monitoring to monitor side-tags and module builds. Distrobaker is a service which rebuilds the CentOS 9 Stream Koji builds for RHEL 9 in Brew. Updates ------- * added a barebones implementation of gathering side tag metrics ## 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 ------- * No updates - team on time offs Kindest regards, CPE Team -- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel December 2021