devel

devel@lists.centos.org

4 participants
4640 discussions

CentOS Hyperscale SIG Quarterly Report for 2022Q3
by Davide Cavalca 03 Oct '22

03 Oct '22

Hello, I've published our quarterly update for the Hyperscale SIG activities on the CentOS Blog: https://blog.centos.org/2022/10/centos-hyperscale-sig-quarterly-report-for-… Cheers Davide

1 0

[REPORT] Quarterly Report - CentOS Automotive SIG
by Jeffrey Osier-Mixon 30 Sep '22

30 Sep '22

October 2022 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat - acting chair _____________________________________ Membership update This SIG does not have a formal membership process. The mailing list currently has 99 subscribers representing at least 31 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 SIG provides a new distribution: Automotive Stream Distribution (AutoSD), a CentOS Stream derivative designed specifically around the needs of an automotive OS, and 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. _____________________________________ Health report and general activity narrative The CentOS Automotive SIG celebrated its first year anniversary in August. The SIG has typically had 1-2 public meetings per month, one formal and one informal "office hours", each with 25-40 attendees, with visible participation from 7-10 separate organizations. The office hours portion has been on hiatus since July as summer vacations brought attendance to a crawl, but we intend to start them back up in October. 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. This is a high-level summary of activity over our first year as outlined on the CentOS blog <https://blog.centos.org/2022/08/centos-automotive-sig-first-year-in-review/> : We worked to define what the Automotive SIG is producing and we landed on three artifacts: - AutoSD, a CentOS-Stream based linux distribution which is the public, in-development version of the Red Hat In-Vehicle Operating System (similar to CentOS Stream for RHEL). - 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. All of this resides in a repository on gitlab, in the CentOS namespace with the infrastructure to enable CI/CD for a basic distribution. We are building a set of nightly images for different use-cases, and have a robust set of documentation at the above link. Not a lot of high-level features have been introduced over the past few months due to vacation schedules, but the distro is doing very well and now supports a SOAFEE implementation along with container support based on podman and systemd. In addition, we are pleased to have had the first contribution from outside Red Hat (thanks Volvo!). _____________________________________ 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 0

CPE Weekly Update for Week 39 of 2022
by Akashdeep Dhar 30 Sep '22

30 Sep '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update-week-39-2022/. If you want to receive weekly reports by email in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Regards, CPE Team

1 0

CentOS Hyperscale SIG conference recap
by Davide Cavalca 29 Sep '22

29 Sep '22

Hello, I've posted a recap of the CentOS Hyperscale SIG conference activities from the past few months on the CentOS Blog: https://blog.centos.org/2022/09/centos-hyperscale-sig-conference-recap/ Cheers Davide

1 0

Gitlab Expiration Notice
by Leigh Griffin 29 Sep '22

29 Sep '22

Hey folks, You may have seen a notification on a banner within Gitlab that talks about an upcoming expiration date and a potential loss of features. This is unfortunately an automated message, our renewal as part of their OSS Program is in motion and no service interrupts are expected. Leigh -- Leigh Griffin Senior Manager, Emerging OS Platforms Red Hat Waterford <https://www.redhat.com/> Communications House Cork Road, Waterford City lgriffin(a)redhat.com M: +353877545162 IM: lgriffin @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://red.ht/sig>

1 0

Keylime configuration changes
by Anderson Sasaki 27 Sep '22

27 Sep '22

Hello, We would like to announce that the new versions of the keylime and keylime-agent-rust packages will include major changes in their configuration files. These changes were introduced in the upstream Keylime 6.5.0 release [1] and rust-keylime 0.1.0 release [2], and implement the specification from the enhancement proposal [3]. The goal of the changes is to make the configuration process easier, with more intuitive and consistent options. The first and more notable change is the split of the previous single file configuration into multiple per-component configuration files. The old “/etc/keylime.conf” file is replaced with six separate configuration files: - /etc/keylime/agent.conf: the Keylime agent configuration file - /etc/keylime/verifier.conf: the Keylime verifier configuration file - /etc/keylime/registrar.conf: the Keylime registrar configuration file - /etc/keylime/tenant.conf: the Keylime tenant configuration file - /etc/keylime/ca.conf: the shared CA configuration file - /etc/keylime/logging.conf: the shared logging configuration file The “ca.conf” and “logging.conf” are shared configuration files that need to be present regardless of the Keylime component installed. In CentOS Stream they are included in the keylime-base subpackage which is required by the other components. The other configuration files are delivered as part of the respective component subpackage. For example, the keylime-verifier subpackage includes the “verifier.conf” file. Another feature introduced is the ability to override the default configuration options through configuration snippets. For each component configuration file, there is a respective /etc/keylime/*.conf.d directory where the user can place files containing snippets to override previously set options. This is the recommended way of overriding configuration options instead of modifying the default configuration file directly. Keep in mind that the configuration processing applies the snippets files in lexicographic order. The last value set to an option is kept. Finally, various options names were modified, especially those related with the TLS configuration. The goal was to make them consistent and intuitive, using the same option name for similar configurations in all components. For example, the “server_key” option sets the private key file used by the server for each of the components that run a server. For more information, please refer to the enhancement proposal [3] or contact us on upstream Slack channel [4] (#keylime on CNCF Slack instance). Thank you, Keylime development team [1] https://github.com/keylime/keylime/releases/tag/v6.5.0 [2] https://github.com/keylime/rust-keylime/releases/tag/v0.1.0 [3] https://github.com/keylime/enhancements/blob/master/72_config_and_simplify_… [4] https://cloud-native.slack.com/messages/C01ARE2QUTZ

1 0

Fwd: Planned Outage - networking work - 2022-09-26 21:00 UTC and 2022-09-27 21:00 UTC
by Fabian Arrotin 26 Sep '22

26 Sep '22

FYI, as that means also some CentOS Services hosted there too (including - but not limited to - SSO) -------- Forwarded Message -------- Subject: Planned Outage - networking work - 2022-09-26 21:00 UTC and 2022-09-27 21:00 UTC Date: Fri, 23 Sep 2022 14:50:01 -0700 From: Kevin Fenzi <kevin(a)scrye.com> Reply-To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org> To: announce(a)lists.fedoraproject.org, infrastructure(a)lists.fedoraproject.org, devel-announce(a)lists.fedoraproject.org

1 0

CS9: current firefox not in compose
by Leon Fauster 23 Sep '22

23 Sep '22

I wonder about the current firefox build 91.13.0-1.el9? Its not on the mirrors (comp 20220829) nor in the last prod compose (20220909) / both lists firefox-91.11.0-2.el9 ... Thanks. -- Leon

6 15

CPE Weekly Update - Week 38 2022
by Michal Konecny 23 Sep '22

23 Sep '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update---week-38-2022/. If you want to receive weekly reports by emails in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Regards, CPE Team

1 0

[Messaging] RabbitMQ for EPEL 9
by Robby Callicotte 21 Sep '22

21 Sep '22

Hello all, I recently stumbled onto this bugzilla issue[1]. It has gone a couple of months without a response from the assignee. I know that the stalled package request procedures can be started now, but I also see that RabbitMQ was built by the Messaging SIG in the past. So... Where should this get routed? Is the messaging SIG still active? I see some info[2] saying that it is, but the lack of response leads me to think that it may not be. Thanks! [1] https://bugzilla.redhat.com/show_bug.cgi?id=2105791 [2] https://wiki.centos.org/SpecialInterestGroup/Messaging -- Robby Callicotte He/Him/His Timezone: America/Chicago IRC: c4t3l | Twitter: @robbycl2v

3 3

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