devel

devel@lists.centos.org

7 participants
4648 discussions

Status of signing kernels in CBS?
by Pierre-Yves Chibon 19 Oct '23

19 Oct '23

Good Morning Everyone, I remember a while back discussions about allowing SIGs to sign kernel builds built in CBS. I don't remember seeing anything land though. Did I miss something? Or is this still an ongoing discussion? Thanks, Pierre

2 1

CentOS Cloud SIG meeting minutes (2023-10-12) centos
by Joel Capitao 12 Oct '23

12 Oct '23

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2023-10-12) ====================================================== Meeting started by jcapitao at 15:14:15 UTC. The full logs are available athttps://www.centos.org/minutes/2023/October/centos-meeting.2023-10-12-15.… . Meeting summary --------------- * roll call (jcapitao, 15:14:20) * OKD/SCOS builds are back on track, we released another 4.13 into `stable` and another 4.14 into `next` yesterday (Oct 11) (lorbus, 15:19:33) * RDO/Openstack Update (jcapitao, 15:30:55) * OpenStack 2023.2 Bobcat is officially released (jcapitao, 15:32:57) * LINK: https://lists.openstack.org/pipermail/openstack-announce/2023-October/00207… (jcapitao, 15:33:06) * RDO is still working to release Bobcat/2023.2 on top of CentOS Stream 9 (jcapitao, 15:33:44) * LINK: https://issues.redhat.com/browse/RDO-135 (jcapitao, 15:34:01) Meeting ended at 15:43:29 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jcapitao (29) * lorbus (24) * centguard (4) * spotz (2) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Platform Tools moving bugs from bugzilla.redhat.com to issues.redhat.com
by Florian Weimer 12 Oct '23

12 Oct '23

The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”. We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.) Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know. The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions. Thanks, Florian

12 26

working with gitlab / rpm locally
by Leon Fauster 10 Oct '23

10 Oct '23

Hi all, sorry if I'm late to the party. I need to touch a package again for a local customization and with the transition to gitlab I wonder how the new process looks like. In the past I used the tools from git.centos.org/centos-git-common.git like get_sources.sh and into_srpm.sh to work locally on packages from git.centos.org/rpms/. The lookaside stuff were here git.centos.org/sources/. So, how does one build a srpm nowadays? Where is the lookaside stuff? A look into https://docs.centos.org/en-US/stream-contrib/ didn't help. BTW, I'm not an fedora dev. So, if the process looks like the fedora one then I have no idea. Any help would be greatly appreciated! -- Thanks in advance, Leon

2 2

2023-10-11 - CentOS Public Board Meeting
by Thomas Oulevey 07 Oct '23

07 Oct '23

Hi Everyone, Our next board meeting will take place at 20:00 UTC on next Wednesday: `date -d "2023-10-11 20:00 UTC"` If you would like to attend please send me an email to alphacc(a)centosproject.org ( 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/@centosboard/B1RoGTRla 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, -- Thomas 'alphacc' Oulevey CentOS Board of Directors Secretary alphacc(a)centosproject.org

1 0

Chartering the CentOS Technical Steering Committee
by Brian Stinson 04 Oct '23

04 Oct '23

Hi Folks, I've filed the following for discussion with the CentOS Board: https://git.centos.org/centos/board/issue/123 I won't re-paste the text of the ticket here, but the overal vision for this group is to evaluate tools we use to build things in the CentOS project, coordinate technical effort among the SIGs, govern certain secure assets (like SIG Secureboot keys), and make recommendations for future technologies to make available in the project. To answer a couple of questions I've had so far: - This group is complementary to (but not replacing) the CentOS Infra SIG which is focused on execution of our technology strategy - Everything written in the description is open for discussion, and I look forward to hashing out some of the finer governance points as we go -- Brian Stinson brian(a)bstinson.com

1 0

ISA SIG meeting minutes
by Florian Weimer 04 Oct '23

04 Oct '23

This covers the last several meetings, for which I failed to send minutes. Sorries. # zlib-ng We want to replace zlib with zlib-ng (in compat mode) for CentOS 10 Stream. In support of that, it would be interesting to rebuild CentOS 9 Stream with zlib-ng in the buildroot (again, in compat mode). AI: Florian to talk to some folks and see what can be done to support the zlib-ng transition effort. # ISA SIG meeting at FOSDEM I've confirmed internally that there will be some CentOS-related activity in the days before FOSDEM. There could even be a slot in the official schedule for the ISA SIG if we wanted that. # Blog post highlighting Intel work on GCC 13 Previously, in a separate venue, Intel shared their GCC 13 performance work. We wanted to encourage them to write a blog post about it, but it turns out that it already exists: Build Innovation and Performance with GCC* 13 <https://www.intel.com/content/www/us/en/developer/articles/technical/build-…> # Upcoming AArch64 work. There might be some AArch64 work items in the ISA SIG space in the future (validating a GCC bug fix, and experimenting with LSE atomics now that the Raspberry Pi 5 with support for them has been announced). Thanks, Florian

2 1

unplanned outage : community cage network issue
by Fabian Arrotin 02 Oct '23

02 Oct '23

Hi all, this Sunday, our zabbix monitoring platform informed us that there were plenty of nodes unreachable in community cage, and after some investigation it's a whole rack that was cut off access from network switches. That causes issues for multiple workloads, including duffy CI infra env, CentOS Stream env (aka https://testing.stream.centos.org) or storage/mirror servers used for https://cbs.centos.org. As we don't know when the root cause will be investigated by the network team managing the network infra, we have disabled the koji builders, so don't even try to submit builds to cbs.centos.org as they'd just be stuck waiting for builders to be available (themselves disabled until we have access to internal mirror) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 1

OCI Image Compatibility Spec
by Marcin Franczyk 21 Sep '23

21 Sep '23

Hello, I am writing to ask if at Red Hat you would be interested to collaborate on container image standard improvements under Open Container Initiative ( https://opencontainers.org/) At Huawei we identified that container image specification lacks compatibility requirements. For instance if you run a container that requires an NVIDIA GPU then you have to make sure that CUDA library in the container matches the CUDA driver on the host. The required version of the driver could be expressed in the container image. There are plenty of similar use cases when it comes to kernel configuration, boot args, modules or out-of-tree drivers. More details could be found here: https://docs.google.com/document/d/1lzwh8DGMu5vXXHwJmnewYIMffkcOEvH8owX4UYj… I think OpenShift and its Machine Config operator could benefit from this by influencing worker node configuration based on the image specification, which would mean that customers would also benefit. I am forming a working group under OCI and believe this initiative should not come only from one company since that will be a global standard. I prepared a template for a working group that will be voted on by the Technical Oversight Board (https://github.com/opencontainers/tob) https://docs.google.com/document/d/1WZbr7xEpUohvyIiSvJEgCCxhAVMM9DmgXBsk1q1… The voting will take place once I create a PR. I think, after the working group is approved, we would need 2-3 months to come up with the first standard and a client tool to build and validate the specification. If you are interested we can schedule a meeting to discuss this. Regards, Marcin

2 3

Let's setup the CentOS Integration SIG
by Aleksandra Fedorova 20 Sep '23

20 Sep '23

Hi, all, I'd like to propose a new Special Interest Group focused on integration efforts around CentOS Stream. ---- # Introduction Integration is verifying that products and services built on top of RHEL or CentOS Stream will continue to work on CentOS Stream and the next release of RHEL and will not break on package updates. As RHEL content becomes available only after the release, RHEL-based services traditionally use a catching-up integration pattern: people have to adjust their products and services to work on new RHEL *after* the update is shipped. Adjusting the services takes time, eating into the supported RHEL lifecycle period. It also reduces the options for how we can deal with breaking changes. CentOS Stream provides a way to enable forward-looking integration: you can do the integration early during the development before the change is shipped to the CentOS Stream or RHEL repositories. This allows us to prevent or at least prepare better for any breaking changes, which might be shipped via CentOS Stream or RHEL updates. # Purpose of the SIG Provide a shared space to develop and maintain tooling and knowledge base on collaborative gating and testing of CentOS Stream updates before they are published to CentOS mirrors. This includes both - package-level and compose-level integration. # Goals * Document existing integration workflows used by other SIGs. * Identify common issues. * Manage, develop and promote the Third-Party CI for CentOS Stream. - Document events and triggers. - Document standard pipelines. * Develop the Integration toolkit. # Deliverables * CentOS Stream Integration Guide The main focus of the SIG at least at the beginning would be to collect and maintain the knowledge base for integration patterns and tools used by other SIGs and community members. * CentOS Third-Party CI service Eventually SIG may take the ownership of the third-party CI service (for example based on CentOS Stream Zuul CI) - this is to be discussed further. # First work items * Develop and document solution to the following question: “I have a test case/task I want to run on every change in CentOS and get notified about the failure. How do I do it?” * Interview other SIGs for their integration workflows to identify common patterns, solutions and issues. # Logistics (to be adjusted later by the SIG members) * Matrix channel - No IRC * Discourse tag - No mailing list * Docs in some GitLab repo - No wiki * Bi–weekly text-only office hours on Matrix channel * (?) Occasional recorded video meeting # Questions 1) Is the scope limited to integrations done by CentOS SIGs? No. There are many ways one can integrate with the CentOS Stream. CentOS Project provides the option to do it via a CentOS SIG, but it is just one of the many possibilities. One can run integration workflows on their own infrastructure (both in the open or in private). We welcome everyone and would like to share the knowledge and tooling (and work items :) ) as much as possible. 2) Is the scope limited to integration with other FOSS projects? No. While all the contributions (tooling, configurations, docs) of the SIG should be open and licensed under the licenses approved by the CentOS Project, you can participate in the SIG even when your primary project/product or service is not public. For example you can use integration tooling in your private labs and optionally contribute test results without sharing the access to your test systems. ---- -- Aleksandra Fedorova Matrix: @bookwar:fedora.im Fediverse: @bookwar@fosstodon.org

5 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel