devel September 2023

devel@lists.centos.org

17 participants
10 discussions

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

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

September board meeting and office hours
by Shaun McCance 20 Sep '23

20 Sep '23

The board had its monthly meeting last week. The recording, minutes, and recap are all available. Recording: https://youtu.be/QsSWOiM8wSE Minutes: https://hackmd.io/@centosboard/H1XiSh7ah Recap: https://blog.centos.org/2023/09/centos-board-meeting-recap-september-2023/ We'll have the followup office hours this Thursday, September 21, at 14:00 UTC. Everybody is welcome to join and talk to the board. https://meet.google.com/nam-dhqm-rae Highlights of the recap: * After much discussion, the wiki has been archived. There was considerable discussion about improvements to be made to the web site and the docs. * The CentOS mailing lists need to be migrated to new infrastructure. * The board discussed sharing infrastructure with Fedora. * Aleksandra Fedorova proposed an Integration SIG to verify that products and services built on CentOS Stream will continue to work on future releases. The board approved. * We discussed the process for sunsetting a few old SIGs that are no longer active. * The community architect proposed an event strategy that involves focusing on CentOS Connect at FOSDEM as the primary contributor event, and hosting smaller classroom-style sessions at other host events. * We discussed the switch to Jira for bug reporting, and the need for better documentation and training around it use.

1 0

[centos-artwork] Restructuring the website homepage layout
by Alain Reguera Delgado 20 Sep '23

20 Sep '23

Hey folks, Could we have a talk about the website homepage layout? Here is a tentative sketch I am working on for the a new website theme: https://centos.gitlab.io/artwork/centos-web/jekyll-theme-centos-base/docume… In this layout: Are "News and Events" and "Blog Posts" redundant sections? Does it make sense to present only extracts from blog posts if we cover "news and events" as blog posts? What is your opinion about restructuring the site content under the following 4 top sections: 1. Project: describes the project itself. For example, the project mission, the project organizational structure, the project trademarks, the project governance, legal stuff, gpg signing keys. 2. Bits: describes content that final users can download, install, study, propose/make changes to, and use in their computers or devices. In this section you would have CentOS Stream and all its derived distributions. This section would cover related information like, screenshots, links to download mirrors, end of life, documentation links for using this distributions, post-installation commands you might want to run. This section would be implemented using "jekyll- theme-centos-download" component. https://centos.gitlab.io/artwork/centos-web/jekyll-theme-centos-download/do… 3. Community: describes the community resources and activities. For example, here you find the entry points for the latest blog posts, news and events as well as shortcuts to resources like mailing lists, wiki, forums, blog, irc, calendars, cbs, and sigs. 4. Sponsors: promotes sponsors with linked images and thanksgiving message for their active support. This section would be implemented using "jekyll-theme-centos-sponsors" component: https://centos.gitlab.io/artwork/centos-web/jekyll-theme-centos-sponsors/do… What would be your perfect layout and content structure for the website? Thanks! -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

2 1

CentOS Cloud SIG meeting minutes (2023-09-14) centos
by Joel Capitao 14 Sep '23

14 Sep '23

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2023-09-14) ====================================================== Meeting started by jcapitao[m] at 15:00:10 UTC. Meeting summary --------------- * roll call (jcapitao[m], 15:00:28) * RDO/OpenStack Update (jcapitao[m], 15:09:26) * New release of OpenStack: Bobcat/2023.2 is ongoing * OKD/SCOS (jcapitao[m], 15:24:46) * no new OKD/SCOS releases since last time * there will be one last stable/4.13 release before we move stable to 4.14 * the next stream will move to 4.15 builds soon too * work on splitting SCOS into a base and an OKD layer is underway at: https://github.com/okd-project/okd-coreos-pipeline/pull/46

1 0

Archiving wiki.centos.org (next week)
by Fabian Arrotin 14 Sep '23

14 Sep '23

As discussed multiple times either on centos-devel list (for example https://lists.centos.org/pipermail/centos-devel/2023-February/142773.html), or during last docs hackaton in Brussels (day after Fosdem), it was decided to just archive the wiki as static html files (exported from moin) and just have these available through git repository The ticket to track this is https://pagure.io/centos-infra/issue/1245 As we need to also migrate/move that VM elsewhere, and itself disappearing when CentOS Linux 7 will be EOL, and because the PoC was enough, I intend to do the following next monday (September 11th): - snapshot wiki.centos.org content (frozen) - export to html static page - import that back in dedicated git repository (https://gitlab.com/CentOS/docs/wiki_archives- - have a new vhost that would just pull from that git repository (if anything was modified/updated) and still content served from https://wiki.centos.org (so that existing links would still work) From that point, it's up to CentOS Docs SIG to decide how/where to put content, but most of the SIGs already moved content elsewhere (usually under https://sigs.centos.org) but in the meantime, it will still be possible to just use git workflow on html files to modify/update/remove content as needed (interim solution) Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

3 3

2023-09-13 - CentOS Public Board Meeting
by Thomas Oulevey 09 Sep '23

09 Sep '23

Hi Everyone, Our next board meeting will take place at 20:00 UTC on next Wednesday: `date -d "2023-09-13 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/H1XiSh7ah 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. Sorry for the late announcement. thanks, -- Thomas 'alphacc' Oulevey CentOS Board of Directors Secretary alphacc(a)centosproject.org

1 0

An update on RHEL moving to issues.redhat.com
by Brendan Conoboy 09 Sep '23

09 Sep '23

Hi folks, In March of this year, Josh Boyer sent out a message to Fedora's devel list letting everybody know RHEL was going to move from bugzilla.redhat.com to issues.redhat.com (Jira) in the future [1]. The work on this activity has proceeded with relative quiet since, although a couple weeks ago Florian mentioned on centos-devel that Platform Tools had begun to move [2]. I'm now providing a more official followup: All new issues found or desired in RHEL (Or CentOS Stream) need to be filed on issues.redhat.com. It's no longer possible to create new BZs for current RHEL (7 through 9) releases. Over the next few weeks, most RHEL BZs will be migrated to tickets in the RHEL project on issues.redhat.com. The BZs that are migrated will be closed with resolution MIGRATED and a pointer to the Jira issue included in the external links section of each respective BZ. Issues that don't get migrated may still be worked on in Bugzilla- only new BZ creation is disabled, and only disabled in RHEL products. Like before, most new RHEL issues are publicly visible by default, without any login required to view. As CentOS Stream development *is* direct RHEL development, this is a definite change, but hopefully only skin-deep. As an example, previously you might have created a RHEL 9 BZ with the Version field set to "CentOS Stream". On issues.redhat.com you would do the same thing by creating an issue in the RHEL project with the "Affects Version" set to "CentOS Stream 9". People are welcome to create an account on issues.redhat.com, just like was done on bugzilla.redhat.com previously, see what we're up to, file issues, and contribute there as well. We've created a hopefully-helpful article with account basics to get your account setup [3]. I've sent a corresponding message to fedora-devel, so apologies if you're reading this a second time. References: 1. Initial Announcement - https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… 2. Migration Starting - https://lists.centos.org/pipermail/centos-devel/2023-August/143056.html 3. Issues.redhat.com account basics - https://access.redhat.com/articles/7032570 -- Brendan Conoboy / CASE & CPE / Red Hat, Inc.

1 0

Proposal for documentation layout on docs.centos.org
by Aleksandra Fedorova 06 Sep '23

06 Sep '23

Hi, folks, I was playing with the ways to organize the CentOS Documentation site and came up with the following proposal: https://hackmd.io/@bookwar/centos-docs-layout The link has more details but in short we need three categories of content: * User Documentation: everything about installing and administering the CentOS system. Large guides go here, as well as small Knowledge Base articles. * Project Documentation: All about processes and policies of the CentOS Project. * SIGs documentation: Documentation subtrees maintained by each Special Interest group on their own. Note that by SIG docs here I mean documentation written and owned by individual special interest groups. The current SIG Guide (https://sigs.centos.org/guide/) belongs to the "Project Documentation" section in this hierarchy. Each top-level item is then expanded to more sub-levels. For many of the items mentioned in the proposal we do not have the content written yet. But if we agree on the layout, we can start by rearranging existing documents to fit the hierarchy. Then we will be able to use the proposed map for any new content, which we add in the future. -- Aleksandra Fedorova Matrix: @bookwar:fedora.im Fediverse: @bookwar@fosstodon.org

4 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel September 2023