devel November 2021

devel@lists.centos.org

41 participants
29 discussions

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

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

17 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

De-branding in CentOS Stream 9
by Alex Iribarren 06 Dec '21

06 Dec '21

Hi all, While trying to run the CentOS functional tests on CS9[*], I noticed that several fail because of branding issues. For example, p_httpd/httpd_centos_brand_server_tokens.sh expects the server string to match `Apache.*\ (CentOS)`, when in fact the server line is: Server: Apache/2.4.51 (Red Hat Enterprise Linux 9) OpenSSL/3.0.0 This got me thinking about how de-branding is supposed to work in CS9. I would guess the usual process would have to be reversed now, where Red Hat would remove the CentOS brand from CS9 packages and add the Red Hat brand for the RHEL 9.0 builds, but clearly this isn't happening yet. I guess this is an oversight? Cheers, Alex [*] I know, I know, but I have to run *something* before you guys release your own functional test suite for CS9!

8 18

CentOS Stream 9 content available for cbs.centos.org : start your builds !
by Fabian Arrotin 30 Nov '21

30 Nov '21

Hi, Long awaited feature request is now implemented on https://cbs.centos.org : you can now start requesting 9s tags to build against/for CentOS Stream 9 ! I already created some tags/targets for SIGs that already requested it some time ago through our dedicated infra tracker (reminder: https://pagure.io/centos-infra/issues) Worth knowing that the following repositories are enabled by default for all newly created 9s tags: - BaseOS - AppStream - CRB What's possible to add ? I know that for 8/8s some SIGs (like Cloud SIG for openstack) rely on other repositories, like HighAvailability , or others. Feel free to ask such repositories to be added to your build tags. It's also possible to build against CentOS Stream 9 buildroots if the pushed repositories don't include all -devel / runtime packages that you need at buildtime. For that, consider also asking for it if/when needed. Important ! Due to the way Stream 9 will be delivered (more news on that later, probably through Brian and/or Carl), I have locked all -release tags for 9s. What does that mean ? That you can build pkgs, and also tag to -testing (that will go out as usual to buildlogs.centos.org) but not to -release (even if tag is created already). Once we'll have figured out how to properly sign+push SIG content out, we'll announce the plan and also unlock the -release SIG tags Stay tuned for more information about that soon. Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

6 11

Board Nominations Requested
by Rich Bowen 29 Nov '21

29 Nov '21

** Please do read the message before responding with your nominations. We have a process, and if you don’t follow the process, it makes everything harder for everyone. Nominations go to a Google Form, and NOT to this list. Read on for more details. ** As per our governance docs - https://www.centos.org/about/governance/board/ and https://git.centos.org/centos/board/blob/master/f/directors/cohorts specifically - this is notification that we’re looking for nominations for directors to replace those departing at the end of this term. Every six months, half our our directors are asked if they wish to continue in their seats. That question has been asked, and we are awaiting the responses. Meanwhile, as you no doubt know, long-time director KB Singh has indicated that he will not be remaining for another term. To this end, we come to you, the CentOS Community, for nominations for who should fill those seats. Please submit your nominations to this form: https://forms.gle/G7mytxgHRpcYEC4ZA Please DO NOT send them to this list. There’s a few reasons for this: * Our governance indicates that the Board selects the next Board. We do not have any defined notion of project “membership” or a voting class of any kind, other than the Board itself. We do not wish to give any false impression that a public vote will be held on this list. * We do not wish for this to devolve into a bikeshed over proposed names. * We do not wish for individuals named to assume that they have any particular advantage over other nominees, nor do we wish for anyone to be shamed, embarrassed, or disappointed, if they are named and then not seated on the Board. The Board will collect those nominations, consider them at an upcoming meeting, and select the next Board at that time. We ask, if you wish to nominate someone, to consider the list of director requirements/recommendations listed at https://www.centos.org/about/governance/director-requirements/ It may also be wise to ask the individual if they are willing/able to serve. Thank you for your participation in this important moment in our project’s history. Rich, for the CentOS Board of Directors

1 2

RHEL docs in CentOS Stream
by Shaun McCance 27 Nov '21

27 Nov '21

The Content Services team inside Red Hat is working on upstreaming its RHEL documentation to CentOS Stream. This is going to take quite a lot of work, so it will be a gradual process. The team could use help in prioritizing which docs to do first. There are over 60 titles, and I won't bore you with the list, but they cover installation, upgrades, administration, containers, security, networking, identity management, storage, and virtualization, among other things. Some of them involve integrations with other Red Hat products, but those products are all built from community projects. I think I'd like to ask a single open-ended question, and then we'll figure out how that maps to existing docs. So: What features or procedures do you wish were better documented in CentOS? Thanks, Shaun McCance Community Architect Red Hat Open Source Program Office

2 1

Building oVirt Node and oVirt Engine Appliance on CentOS Infrastructure
by Sandro Bonazzola 25 Nov '21

25 Nov '21

Hi, we are now trying to build oVirt stable release content on https://cbs.centos.org/ and ship it to users via CentOS Virtualization SIG repos. Most of the packages are building fine (except ovirt-engine which still need some work, currently tracked on https://pagure.io/centos-infra/issue/527 ) The two most challenging builds are the oVirt Node and oVirt Engine Appliance which on oVirt jenkins are requiring lorax and imagefactory, running virt-install in nested virtualization. This seems to not be working in copr build flow and I expect it to not work on cbs. How can we build an OVA and an ISO within centos infrastructure for shipping it as part of the Virtualization SIG? I know there's https://ci.centos.org/ which may probably be able to do the same task we are running on jenkins.ovirt.org but I guess there's a more "standard" way to do it in CentOS infra. Thanks, -- 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.*

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel November 2021