devel May 2024

devel@lists.centos.org

5 participants
4 discussions

Zuul/Nodepool upgrade on Thursday 16 of May (9:00 UTC)
by Fabien Boucher 16 May '24

16 May '24

Dear all, We are planning to upgrade Zuul and Nodepool from major version 8 to major version 10 on centos.softwarefactory-project.io [1]. We will start the upgrade on May 16th at 9:00 UTC, and expect a service downtime of about 3 hours. Zuul: https://zuul-ci.org/docs/zuul/latest/releasenotes.html#relnotes-10-0-0 Nodepool: https://zuul-ci.org/docs/nodepool/latest/releasenotes.html#relnotes-10-0-0-… During the upgrade no CI Job will run on Merge Requests for redhat/centos-stream/rpms/*. Without any expressed concerns about the proposed schedule we will process on the due date. [1] https://centos.softwarefactory-project.io/zuul/t/centos/status Fabien Boucher on behalf of the prodchain infra team

1 1

migrating centos-bootc infra into centos
by Colin Walters 15 May '24

15 May '24

Hey, we announced image mode for RHEL: https://www.redhat.com/en/blog/introducing-image-mode-red-hat-enterprise-li… It's tech preview, but I think it'd make sense to move these images into centos proper still. Right now we have upstream code in https://github.com/centos/centos-bootc and we created a temporary quay.io namespace in quay.io/centos-bootc. I'd like to propose a migration like this: - github.com/centos/centos-bootc -> https://gitlab.com/redhat/centos-stream/containers/bootc (Somewhat paralleling https://gitlab.com/fedora/bootc/base-images ) This would also implicitly be creating a new containers/ namespace) - quay.io/centos-bootc/centos-bootc:stream9 -> quay.io/centos/centos-bootc:stream9 - quay.io/centos-bootc/bootc-image-builder:latest -> quay.io/centos/bootc-image-builder:latest The :latest tag is currently a bit out of place for bib, and should probably switch to :stream9 too? That said, the time may also be right at least for these things to convert from a ":stream9" tags in favor of a more...streamlined tag like just plain ":9"? Only tangentially related, but still related is $ skopeo inspect -n docker://quay.io/centos/centos:latest|jq -r .Created 2020-12-08T00:22:53.076477777Z $ Which is obviously pretty broken...we should probably just drop this `:latest` tag as it's just a trap at this point?

3 3

CentOS Stream 8 ending in less than two weeks (May 31, 2024)
by Troy Dawson 13 May '24

13 May '24

CentOS Stream 8 was the first of the CentOS Stream releases. As such, it is the first to end. CentOS Stream 8 End Of Life is Friday, May 31, 2024. We will be following the established CentOS practice of moving all the released content to vault.centos.org. When everything has been moved over, all dnf/yum commands that point to the normal CentOS Stream 8 repositories will break. CentOS Stream 8 users that are not ready to move off, will have to manually update their configurations to point to vault.centos.org. But there will be no more updates of any kind. No security updates. No feature updates. No updates at all For more details of CentOS Stream's retirement, please read this earlier email. https://lists.centos.org/hyperkitty/list/devel@lists.centos.org/thread/BIWC… Troy Dawson

1 0

2024-05-08 - CentOS Public Board Meeting External
by Amy Marrich 07 May '24

07 May '24

Hi Everyone, Our next board meeting will take place at 21:00 UTC on next Wednesday: `date -d "2024-05-08 21:00 UTC"` If you would like to attend please send an email to shaunm(a)redhat.com ( please do not reply to @centos-devel or use another email address) and you will receive a link to a meeting room with a passcode, 1 hour before the meeting takes place. The agenda can be checked at (work in progress) : https://hackmd.io/VKzlKTqiS6eMVsXjjxKwhw As a reminder we will enforce few rules : * 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/redaction, 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. I hope some of you can join. thanks, *Amy Marrich* She/Her/Hers Principal Technical Marketing Manager - Cloud Platforms Red Hat, Inc <https://www.redhat.com/> amy(a)redhat.com Mobile: 954-818-0514 Slack: amarrich IRC: spotz

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel May 2024