devel

devel@lists.centos.org

16 participants
4590 discussions

October board meeting recording and office hours
by Shaun McCance 17 Oct '22

17 Oct '22

Hi all, I've uploaded the recordings of last week's board meeting: https://youtu.be/FA0ddn-IWes If you'd like to discuss any issues with the board, we'll have an open board office hours this Thursday, October 20, at 14:00 UTC: https://us06web.zoom.us/j/87623425120 Thanks, Shaun

1 0

EPEL 8 Modules get the axe on Halloween 2022
by Troy Dawson 14 Oct '22

14 Oct '22

When EPEL-8 was launched, it came with some support for modules with the hope that a module ecosystem could be built from Fedora packages using RHEL modules as an underlying tool. This has never happened and we have ended up with a muddle of modular packages which will 'build' but may not install or even run on an EL-8 system. Attempts to fix this and work within how EPEL is normally built have been tried for several years by different people but have not worked. At this point we are saying that this experiment with modules in EPEL has not worked and we will focus our resources on what does work. Schedule of EPEL 8 Module Retirement: Next Week: - epel-release will be updated. -- epel-modular will set enabled = 0 -- epel-modular full name will have "Deprecated" in it October 31 2022: - The EPEL 8 modules will be archived and removed. -- The mirror manager will be pointed to the archive. - Packagers will no longer be able to build EPEL 8 modules. After October 31st (Actual date to be determined): - epel-release will be updated again. -- epel-modular repo configs will be removed. Questions and Answers: Question: Will I still be able to access the modules after October 31st? Answer: It is not recommended, because the modules will not get any security or bug fixes, but yes. They will be in the Fedora archives, and the mirror managers will point at them. Question: What will you be dressed as on Halloween? Answer (Troy): A Penguin EPEL Steering Committee [1] - https://pagure.io/epel/issue/198

2 3

CentOS Cloud SIG meeting minutes (2022-10-13)
by Joel Capitao 13 Oct '22

13 Oct '22

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2022-10-13) ====================================================== Meeting started by jcapitao at 15:01:41 UTC. The full logs are available athttps://www.centos.org/minutes/2022/October/centos-meeting.2022-10-13-15.… . Meeting summary --------------- * roll call (jcapitao, 15:01:54) * Documentation update (jcapitao, 15:05:27) * LINK: https://lists.centos.org/pipermail/centos-devel/2022-August/120541.html (jcapitao, 15:07:59) * LINK: https://wiki.centos.org/SpecialInterestGroup/Cloud (lorbus, 15:08:26) * ACTION: Cloud SIG to migrate its documentation on https://sigs.centos.org/ (jcapitao, 15:12:29) * Meetup heads up (jcapitao, 15:13:22) * OKD/SCOS (CentOS Stream CoreOS 9) update (jcapitao, 15:22:47) * LINK: https://github.com/openshift/installer/pull/6443 has to merge (it's already been approved and passed e2e testing) (lorbus, 15:24:16) * The OKD/SCOS MVP release is imminent, and announcement will go out in the next days (lorbus, 15:35:23) * LINK: https://issues.redhat.com/secure/RapidBoard.jspa?rapidView=15137 (lorbus, 15:41:17) Meeting ended at 15:59:22 UTC. Action Items ------------ * Cloud SIG to migrate its documentation on https://sigs.centos.org/ Action Items, by person ----------------------- * **UNASSIGNED** * Cloud SIG to migrate its documentation on https://sigs.centos.org/ People Present (lines said) --------------------------- * jcapitao (38) * lorbus (34) * amoralej (28) * spotz (15) * centguard (5) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

I wish to be an developer and help to grow up for CentOS community
by Ramone Ferreira 11 Oct '22

11 Oct '22

Gratitude for this e-mail, i'm a software developer, with works C, C++,Lua, Python and i hope so much to contribute community i'm Ramon, and i looking for some experience with linux and software development cordially thanks

1 0

Re: [CentOS-devel] CentOS Stream 8
by Rich Bowen 11 Oct '22

11 Oct '22

I'm now at AWS on the open source team. Shaun McCance has taken my centos role Shosholoza, Rich On Thu, Sep 29, 2022, 16:49 John Aron <john(a)aronetics.com> wrote: > Thank you Rich. What are you doing now? > > John > > -----Original Message----- > From: Rich Bowen <rbowen(a)rcbowen.com> > Sent: Thursday, September 29, 2022 4:24 PM > To: John Aron <john(a)aronetics.com>; rbowen(a)centosproject.org > Subject: Re: CentOS Stream 8 > > I am no longer working with the CentOS project. I encourage you email > centos-devel(a)centos.org which is where all of the experts hang out. > > --Rich > > On Thu, 2022-09-29 at 15:16 -0400, John Aron wrote: > > Rich, > > > > I am happy that I have your card and info to email you. The new kernel > > on CentOS Stream 8 is significantly unstable. I have a Dell > > R710 with the PERC H700 raid controller. > > > > Here’s my last dmesg from vmcore-dmesg. > > -- > > [root@stinkfist 127.0.0.1-2022-09-29-14:57:49]# less vmcore- dmesg.txt > > 00 00 48 c7 40 08 00 00 00 00 4b 8d 44 [ 1755.255275] RSP: > > 0018:ffffb04146423cc0 EFLAGS: 00010206 [ 1755.255279] RAX: > > ffff8a76ce9e2800 RBX: ffff8a7608c3c400 RCX: > > 0000000000000000 > > [ 1755.255283] RDX: 0000000000000860 RSI: ffffb0414be4daa0 RDI: > > 0000000000000003 > > [ 1755.255285] RBP: 0000000000000000 R08: ffff8a80fffd5000 R09: > > 0000000000000000 > > [ 1755.255288] R10: ffffb0414be4d8c8 R11: fffffffffffffff0 R12: > > ffffb0414be4d000 > > [ 1755.255291] R13: 0000000000000000 R14: 0000000000000001 R15: > > ffff8a76ce9e2800 > > [ 1755.255294] FS: 00007fc871437700(0000) GS:ffff8a80cfa80000(0000) > > knlGS:0000000000000000 > > [ 1755.255298] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ > > 1755.255301] CR2: 000000000000000b CR3: 0000000e72b00006 CR4: > > 00000000000226e0 > > [ 1755.255305] Call Trace: > > [ 1755.255312] ? kmem_cache_alloc_trace+0x142/0x280 > > [ 1755.255321] kvm_set_memslot+0x248/0x480 [kvm] [ 1755.255371] > > kvm_set_memory_region+0x26/0x40 [kvm] [ 1755.255433] > > kvm_vm_ioctl+0x62c/0xcc0 [kvm] [ 1755.255509] ? > > handle_pte_fault+0x480/0x870 [ 1755.255518] ? > > seccomp_run_filters+0x77/0x120 [ 1755.255525] ? > > __handle_mm_fault+0x44f/0x6c0 [ 1755.255533] do_vfs_ioctl+0xa4/0x680 > > [ 1755.255541] ? handle_mm_fault+0xc1/0x1e0 [ 1755.255548] > > ksys_ioctl+0x60/0x90 [ 1755.255555] __x64_sys_ioctl+0x16/0x20 [ > > 1755.255562] do_syscall_64+0x5b/0x1a0 [ 1755.255572] > > entry_SYSCALL_64_after_hwframe+0x65/0xca > > [ 1755.255581] RIP: 0033:0x7fd0860217cb [ 1755.255587] Code: 73 01 c3 > > 48 8b 0d bd 66 38 00 f7 d8 64 89 01 48 > > 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 00 00 > > 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8d 66 38 00 f7 d8 64 > > 89 01 48 > > [ 1755.255593] RSP: 002b:00007fc871436198 EFLAGS: 00000246 ORIG_RAX: > > 0000000000000010 > > [ 1755.255600] RAX: ffffffffffffffda RBX: 00007fc84abc0298 RCX: > > 00007fd0860217cb > > [ 1755.255604] RDX: 00007fc871436200 RSI: 000000004020ae46 RDI: > > 0000000000000011 > > [ 1755.255608] RBP: 00007fc871e00000 R08: 000055e7e9920a60 R09: > > 0000000000000000 > > [ 1755.255613] R10: 0000000000000000 R11: 0000000000000246 R12: > > 000055e7ea69daf0 > > [ 1755.255617] R13: 00007fc871436200 R14: 00000000000e8000 R15: > > 00007fc84abc0298 > > [ 1755.255624] Modules linked in: tun nft_fib_inet nft_fib_ipv4 > > nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 > > nft_reject nft_ct nf_tables_set nft_chain_nat nf_nat nf_conntrack > > nf_defrag_ipv6 bridge nf_defrag_ipv4 stp llc ip_set nf_tables > > nfnetlink sunrpc intel_powerclamp coretemp kvm_intel kvm irqbypass > > crct10dif_pclmul iTCO_wdt crc32_pclmul iTCO_vendor_support gpio_ich > > ghash_clmulni_intel dcdbas intel_cstate ipmi_ssif joydev intel_uncore > > pcspkr lpc_ich wmi ipmi_si acpi_power_meter i7core_edac xfs > > dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c > > sr_mod cdrom ata_generic sd_mod t10_pi sg mgag200 drm_kms_helper > > syscopyarea sysfillrect sysimgblt fb_sys_fops drm ata_piix libata > > crc32c_intel serio_raw i2c_algo_bit megaraid_sas bnx2 dm_mirror > > dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse [ > > 1755.255765] CR2: 000000000000000b ~ > > -- > > What’s the origin of this crash? I don’t have anyone else to cc’ on > > this matter. I could recompile the kernel cleaning out the unrelated > > functionality present. This could assist? > > > > John > > > > aronetics.com > > We Speak IT® > > > > > >

3 3

Try out the new RHEL module streams with the CentOS Stream 8 and 9
by Honza Horak 10 Oct '22

10 Oct '22

(I've sent this before, but it seems to have never reached the mailing list, so re-sending again; although less interesting today, when RHEL 8.7 and 9.1 Beta are already out, yet I believe the thoughts about Stream concept are worth looking at). As you likely know, CentOS Stream is a new concept that allows the community to see what future RHEL brings. Let me touch on a few specific things that you can test in CentOS Stream 8 and 9 for some time already, and couldn't see in a released RHEL until recently. Module streams concept is used in CentOS Stream 8 and 9 (and thus also in the future RHEL-8.x and RHEL-9.x versions) for delivering alternative versions of popular stacks for developers (except other components). You can for example try the latest Node.js version 18, Ruby 3.1, or Maven 3.8. How? Let's see an example with a CentOS Stream 9 container image: First, pull the CentOS Stream 9 image using podman and run it: #> podman pull centos:stream9 #> podman run -ti --rm centos:stream9 Then, use dnf to list available modules [root@ad0a3f9d2aa3 /]# dnf module list Here you see a couple of modular streams that are not enabled by default but are available in the repository in parallel to the default version (which is 3.0 in the case of Ruby and CentOS Stream 9). Now, the most important part, enable the latest available version of Ruby and install some packages: [root@ad0a3f9d2aa3 /]# dnf -y module enable ruby:3.1 [root@ad0a3f9d2aa3 /]# dnf -y install ruby And finally, check what version we actually have: [root@ad0a3f9d2aa3 /]# ruby --version ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux] And you can follow a similar pattern for other module streams, that are on their way to the next RHEL minor release. This way, CentOS Stream and RHEL users can test the new content earlier than before and provide feedback in the BZ [2]. [1] https://www.centos.org/centos-stream/ [2] https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20… Enjoy! Honza

4 3

Is anybody triaging the CentOS Stream distribution bugzillas?
by Miro Hrončok 05 Oct '22

05 Oct '22

Hello, we (the Python maint team) have received several CentOS Stream 9 bugzillas assigned to the distribution component: https://bugzilla.redhat.com/show_bug.cgi?id=2104963 https://bugzilla.redhat.com/show_bug.cgi?id=2127325 We cannot fix them. Is *anybody* triaging such bugzillas? Who do we need to gently ping about them? Thanks, -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

2 2

[messaging] any plans for RabbitMQ 3.10 and Erlang 25?
by Marcin Juszkiewicz 04 Oct '22

04 Oct '22

In OpenStack Kolla project we are building OpenStack components as container images. And some extra images for infrastructure. One of components we use is RabbitMQ. For each of supported distributions (CentOS Stream 9, Debian 11, Ubuntu 22.04) we want to use the same versions: - rabbitmq-server 3.10.* - erlang 25.* We use upstream provided repositories for each distro/arch as there are no up-to-date versions provided in distribution repositories. Are there plans for updating RabbitMQ and Erlang in Messaging SIG repo to 3.10.* and 25.*? This would allow us to support CentOS Stream 9 on AArch64 (where we now have no working builds and consider downgrading to whatever is in CS9 for now).

3 2

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

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