devel January 2022

devel@lists.centos.org

30 participants
26 discussions

CentOS Hyperscale SIG Quarterly Report for 2021Q4
by Davide Cavalca 10 Jan '22

10 Jan '22

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

1 0

[REPORT] Automotive SIG
by Jeffrey Osier-Mixon 10 Jan '22

10 Jan '22

January 2022 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat - acting chair _____________________________________ Membership update (members added, removed. Chair changes.) This SIG does not have a formal membership process. The mailing list currently has 77 subscribers representing at least yy companies. I have been asked to act as chair for the first few months in order to stabilize the SIG. _____________________________________ Releases in the most recent quarter (or most recent release, if none in that quarter) The SIG is not yet creating builds or publishing releases, but we are very close to doing so at this point; see the report below. _____________________________________ Health report and general activity narrative. The SIG has had two public meetings per month, one formal and one informal "office hours", each with 25-40 attendees representing 7-10 separate organizations. We feel this is a good start at corporate community diversity but will continue to work toward a community-driven project. This SIG is intended to be a community effort with contributions and shared benefits from all participants. Several RH employees made the first contribution to the project as well as the infrastructure required to build and test it. We now occupy a gitlab repository building software regularly, with build instructions provided, and we are on track for a downloadable release in Q1 2022. This is a high-level summary of current activity from our technical lead: - The work keeps on going at: https://gitlab.com/redhat/automotive/automotive-sig - We have created manifests in that repository that can be used with OSBuild to create a number of images. - We currently support: - qemu and raspberry pi - x86_64 and aarch64, - ostree-based (default) and non-ostree-based - booting via uefi of by-passing it and booting directly the kernel - We then have 3 images - minimal - osbuilder (containing the tools allowing to build images with osbuild) - neptune (demo image with a graphical interface running the demo app: neptune) - The OSBuild manifests have been streamed-line and simplified a lot. If you have not look at them in a while have a look ! - We have also added a mechanism to easily build images from within a virtual machine, which makes it easier to build images without root privileges. - The VM created for the step just above (^) can also be migrated to a different system, thus allowing to build more easily in a different architecture. - Instructions on how to build images have also been greatly simplified The doc at: https://sigs.centos.org/automotive/building/ is up to date - We have a kernel-auto package based on the CentOS-Stream package and with the Real-Time patches included - We have a few koji tags set-up for the SIG, the kernel-auto is the main beneficiary of them (with a couple of other RT related packages) - We are working on automatically building some of our sample images and making them available. A few of them can be found at: https://pingou.fedorapeople.org/images/ but this is a temporary location and they are now over a month old. - We have been sending weekly updates to the SIG mailing list on a regular cadence and will try to continue doing it. _____________________________________ 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

2 1

Final reminder: CFP for February Dojo
by Rich Bowen 07 Jan '22

07 Jan '22

This is your final reminder: The CFP for the February CentOS Dojo - https://wiki.centos.org/Events/Dojo/FOSDEM2022 - will close on January 9th. Note that, as of right now, we only have enough content for one day, and presumably if this doesn't change between now and then we'll drop Thursday and just have a one-day event on Friday. --Rich

2 1

[Cloud SIG][Meeting] CentOS Cloud SIG meeting minutes (2022-01-06)
by Alfredo Moralejo Alonso 06 Jan '22

06 Jan '22

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2022-01-06) ====================================================== Meeting started by amoralej at 15:03:31 UTC. The full logs are available athttps://www.centos.org/minutes/2022/January/centos-meeting.2022-01-06-15.… . Meeting summary --------------- * Status of Cloud SIG and CentOS Linux 8 EOL (amoralej, 15:06:26) * CL8 is EOL and will be reomved with SIGs content from CentOS Mirrors on Jan 31st (amoralej, 15:07:05) * Cloud SIG has repos for CentOS Stream 8 for Ussuri, Victoria, Wallaby and Xena (amoralej, 15:08:39) * ACTION: anyone using CloudSIG repos and CentOS Linux 8 should move to CentOS Stream 8 (amoralej, 15:10:06) * ACTION: CloudSIG will update release rpms to remove logic to detect CL8 or CS8 and point always to CS8 (amoralej, 15:15:11) * plans for next release CloudSIG RDO Yoga (amoralej, 15:18:46) * OpenStack project agreed to support both CentOS Stream 8 and CentOS Stream 9 in coordinated Yoga release (amoralej, 15:20:03) * RDO plan to release packages for OpenStack coordinated Yoga release both for CentOS Stream 8 and 9 as soon as possible after upstream GA (early april) (amoralej, 15:20:58) * support for TripleO in CS8 in Yoga is still being discussed (amoralej, 15:21:15) * chair election (amoralej, 15:26:14) * AGREED: to maintain current chair in Cloud SIG until next election which will happen in march/april (amoralej, 15:42:36) Meeting ended at 15:45:05 UTC. Action Items ------------ * anyone using CloudSIG repos and CentOS Linux 8 should move to CentOS Stream 8 * CloudSIG will update release rpms to remove logic to detect CL8 or CS8 and point always to CS8 Action Items, by person ----------------------- * **UNASSIGNED** * anyone using CloudSIG repos and CentOS Linux 8 should move to CentOS Stream 8 * CloudSIG will update release rpms to remove logic to detect CL8 or CS8 and point always to CS8 People Present (lines said) --------------------------- * amoralej (69) * spotz_ (18) * jcapitao (8) * arrfab (8) * centbot (3) * themayor (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

minimal CentOS 8 or 9 stream container images
by Ken Dreyer 05 Jan '22

05 Jan '22

Is there a 8stream-minimal or 9stream-minimal image that uses microdnf? We're searching for a smaller base image for the Ceph project, and we'd like to use an image similar to https://catalog.redhat.com/software/containers/ubi8/ubi-minimal/5c359a62bed… , but the ubi8 repos don't have all the packages we need. Maybe we could use the Stream 8 .repo files with ubi8-minimal as a workaround? But what should we do for el9? - Ken

2 1

CentOS Linux 8 and SIGs content removal plan (please read)
by Fabian Arrotin 04 Jan '22

04 Jan '22

As you’re all aware, and per https://www.centos.org/centos-linux-eol/ , CentOS Linux 8 is going EOL end of this month, and content will just remain available on mirror network until January 31st. After that date, CentOS Linux 8 repositories will be removed from mirror network, and mirrorlist will start answering “invalid release”, so no way to easily install any rpm component. But what about SIGs content that was built for/against CentOS Linux 8 ? (basically other repositories that you can see under http://mirror.centos.org/centos/8/ but that aren’t coming from centos linux 8 distro itself ? As soon as CentOS Stream 8 was announced, we offered the possibility to all SIGs to opt-in and build for/against Stream 8, and so have their repositories automatically pushed to http://mirror.centos.org/centos/8-stream , as it was for /8/ . Most of the SIGs opted at that time to build in parallel for 8 and 8-stream, while some decided to just start building against/for 8-stream directly (and of course content built on 8-stream *should* just work fine, and reverse is also true) But some months ago, community members asked (https://pagure.io/centos-infra/issue/400) if that was possible to continue building against/for el8, but so switching buildroot from centos 8 to RHEL 8, which was worked on and is now available. What does that mean for you, SIGs ? If you want (opt-in and so optional) continue to build for el8, just create a ticket on https://pagure.io/centos-infra/issues to ask your tags to build against RHEL 8 instead of CentOS Linux 8. You can do that whenever you want but before (for obvious reasons) end of January 2022 What if you don’t opt-in ? You SIG content will removed from mirror network, at the same time as CentOS Linux 8 content. So to recap : * End of january, *all* repositories listed under http://mirror.centos.org/centos/8/ will be removed (except for SIGs that opted-in for the ‘switch to RHEL 8 buildroot’ plan) * mirrorlist.centos.org will also start answering ‘invalid repo’ for SIG content, as it will be for CentOS Linux 8 itself * All SIGs tags for 8 will be locked down (except for SIGs that opted-in for the ‘switch to RHEL 8 buildroot’ plan) so no way to just tag-build (and so push anything) out -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2022