devel August 2023

devel@lists.centos.org

15 participants
9 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

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

[centos-website-artwork] Request for feedback about base/default layout
by Alain Reguera Delgado 30 Aug '23

30 Aug '23

Hi, There is some documentation in progress about "base/default" layout, the default layout that jekyll-theme-centos will be using to render content. You can check it on the following URL: https://centos.gitlab.io/artwork/centos-web/jekyll-theme-centos-base/docume… This page is also an example of how the content presentation looks like when you use the "base/default" layout in your site. I would like to request some feedback from you about the "base/default" layout features and visual presentation as well. Appreciate your comments and concerns here. Thanks! -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

2 3

[REPORT] Quarterly Report - CentOS Automotive SIG
by Jeffrey Osier-Mixon 17 Aug '23

17 Aug '23

January 2023 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat - chair _____________________________________ Membership update This SIG does not have a formal membership process. The mailing list currently has 106 subscribers representing at least 32 organizations, though not all subscribers use corporate emails and some are participating as individuals. _____________________________________ Releases in the most recent quarter (or most recent release, if none in that quarter) The Automotive SIG produces three types of artifacts: - AutoSD, a streaming distribution of CentOS designed for in-vehicle automotive use cases. - An Automotive SIG RPM repository that allows the community to expand the content of AutoSD or experiment with some of its parts. - Sample images, built using OSBuild, which provide examples of how to assemble production images based on AutoSD, customized for some hardware, including container images, based on CoreOS/ostree technologies. AutoSD, or Automotive Stream Distribution, is a streaming distribution for automotive in-vehicle software development based on CentOS Stream. It is transparently the upstream project for Red Hat's eventual in-vehicle OS product. AutoSD has been downloaded and used by many organizations who have commented or asked for help, so we know it is getting some traction though of course we don't have exact metrics on usage. In Q4 2022, we released a version of AutoSD compatible with the emerging SOAFEE specification. SOAFEE (https://soafee.io) is an initiative driven by Arm for the purpose of developing a reference specification for Arm-based software-defined vehicles (SDVs) consisting of an operating system, container orchestration strategy, and application layer. In addition, we introduced a very lightweight container runtime based on podman and systemd that does not include Kubernetes, as the latter represented a significant performance hit on all relevant hardware. We presented at the Arm Developer Summit in November on these topics. In the coming quarter, we plan to tighten up documentation, begin a process for accepting and supporting hardware enablement contributions, and continue to develop AutoSD toward the SOAFEE specification while also contributing to that specification within the SOAFEE community. _____________________________________ Health report and general activity narrative The SIG typically has 1 public meeting per month with 25-40 attendees, with visible participation from 7-10 separate organizations. We have largely given up on a separate office hours meeting due to attendance. This SIG is intended to be a community effort with contributions and shared benefits from all participants. All formal meetings are recorded and posted on this page: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings Several Red Hat employees made the initial contributions to the project as well as the infrastructure required to build and test it. We occupy a gitlab repository in the CentOS namespace building software regularly using CI, with build instructions provided on the documentation page at https://sigs.centos.org/automotive/ . Sample images are present and downloadable along with customization and build instructions. _____________________________________ Issues for the board to address, if any None, keep up the excellent work :) Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 1

August board meeting and office hours
by Shaun McCance 16 Aug '23

16 Aug '23

The board had its monthly meeting last week. The recording, minutes, and recap are all available. Recording: https://www.youtube.com/watch?v=2pWqcs4LJq8 Minutes: https://hackmd.io/@centosboard/r14tdu5j2 Recap: https://blog.centos.org/2023/08/centos-board-meeting-recap-august-2023/ We'll have the followup office hours this Thursday, August 24, at 14:00 UTC. Everybody is welcome to join and talk to the baord. https://meet.google.com/nkj-psxs-urg Highlights of the recap: * We got an update on the status of trusting SIGs for secureboot (Issue 67). * We discussed issues that have arisen with bridging Matrix to IRC (Issue 116). * We discussed guidelines for SIGs to publish images on Quay (Issue 90). * The community architect gave a report from CentOS Connect and Flock. * We briefly discussed the contributor docs, SIG health checkins, and Promo SIG activity. * We had some early discussions around planning CentOS Connect at FOSDEM. * We talked about various alternatives to using Zoom for board and SIG meetings.

1 0

[Cloud SIG] Meeting Cancellation Aug 10 2023
by Joel Capitao 08 Aug '23

08 Aug '23

Hi folks, The CloudSIG meeting, planned at 1500 UTC on Thursday 10th August, is cancelled. It will resume as normal on #centos-meeting channel at 1500 UTC on Thursday 14th September. Regards, Joel

1 0

2023-08-09 - CentOS Public Board Meeting
by Thomas Oulevey 04 Aug '23

04 Aug '23

Hi Everyone, Our next board meeting will take place at 20:00 UTC on Wednesday: `date -d "2023-08-09 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 Zoom 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/r14tdu5j2 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

[ISA SIG] Meeting notes 2023-07-21
by Florian Weimer 03 Aug '23

03 Aug '23

I forgot to post the minutes immediately after the meeting. Key points discussed were: So far, there is no round of new rebuilds with GCC 13 scheduled. The recommended way for installation remains starting out with CentOS Stream and using dnf distro-sync. See <https://sigs.centos.org/isa/consuming/centosstream9/>. Starting with RHEL 9.2 results in cross-grade issues. If the update from c9s breaks, we may have to rebuild some more packages. Thanks, Florian

1 0

[Infra] - Planned outage : cbs.centos.org
by Fabian Arrotin 03 Aug '23

03 Aug '23

Due to a hardware replacement and storage reorg, we'll have to move the existing CentOS Community Build System (aka https://cbs.centos.org) to a new node. Migration is scheduled for """"Thursday August 3rd, 6:30 am UTC time"""". You can convert to local time with $(date -d '2023-08-03 06:30 UTC') The expected "downtime" is estimated to ~45 minutes , time needed to : - stop kojid instances - move kojihub instance and restore data - reconfigure kojid builders to point to new storage location Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel August 2023