The monthly CentOS newsletter is available. This month: making Stream 8
more like Stream 9, retiring EPEL 8 Modules, web and docs work, and an
x86 SIG proposal. Plus, updates from Alt Images and Virtualization
SIGs.
https://blog.centos.org/2023/03/centos-newsletter-march-2023/
We've published the video of Wednesday's board meeting.
Recording:
https://youtu.be/VQ1Zc8D-xh4
Minutes:
https://hackmd.io/JU0brnwQQcy0lfmoviA1FA
Recap:
https://blog.centos.org/2023/03/centos-board-meeting-recap-march-2023/
We'll have a followup board office hours next Thursday, March 16, at
14:00 UTC. (Note that this might be a different local time for you than
last time. We have followed US DST.)
https://us06web.zoom.us/j/85797326320?pwd=ang0SjlxRlRYTlRGRlFSUXJzZGNUZz09
Highlights of the recap:
* Christian Glombek presented about CentOS Stream CoreOS & OKD Streams.
This is a condensed version of the talk he gave at CentOS Connect. We
unfortunately don't have a recording of that talk because of technical
issues, so this is your chance to see it.
* We discussed the x86 SIG proposal. This conversation is ongoing.
* Issue 92: We discussed signing testing repositories
* We gave a recap of the work to migrate content off the wiki. See the
post on centos-promo.
* Issue 93: We talked about the announcement around the EOL/EOB for
CentOS Stream 8 and CentOS Linux 7 in 2024. Pat has written a post, and
Shaun is working on how to display notices.
* We talked about events. We would like to find a home event for a
North America West CentOS Connect to join our European event at FOSDEM
and our US East event at DevConf.US. We also talked about how to do
virtual events, and giving them their own identity distinct from the
in-person CentOS Connect.
* We talked about doing a survey around CentOS awareness and sentiment.
======================================================
#centos-meeting: CentOS Cloud SIG meeting (2023-03-09)
======================================================
Meeting started by jcapitao[m] at 15:00:54 UTC. The full logs are
available athttps://www.centos.org/minutes/2023/March/centos-meeting.2023-03-09-15.00…
.
Meeting summary
---------------
* roll call (jcapitao[m], 15:01:22)
* OKD/SCOS Update (jcapitao[m], 15:11:40)
* the preparation of the RPM builds for the OpenShift container stack
is on-going (jcapitao[m], 15:12:31)
* OKD/SCOS is working on standing up a cluster on massopen.cloud
(jcapitao[m], 15:13:16)
* New release of OpenStack: RDO Antelope schedule plans (jcapitao[m],
15:14:21)
* RDO Antelope should be GA by end of March (jcapitao[m], 15:16:40)
* TripleO packages won't be provided in CloudSIG repo for this release
(jcapitao[m], 15:21:25)
* LINK:
https://lists.rdoproject.org/archives/list/dev@lists.rdoproject.org/thread/…
(jcapitao[m], 15:21:33)
* LINK:
https://lists.centos.org/pipermail/centos-devel/2023-March/142809.html
(amoralej, 15:32:23)
* LINK:
https://lists.centos.org/pipermail/centos-devel/2023-March/142814.html
(jcapitao[m], 15:44:21)
Meeting ended at 15:46:32 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jcapitao[m] (40)
* amoralej (18)
* spotz (10)
* centguard (4)
* davdunc[m (2)
* karolinku12 (1)
* lorbus (1)
* karolinku (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Hi everyone,
it came to Infra & Releng Team (sub-team in CPE that is taking care of
Fedora Infra, Fedora Release Engineering and CentOS Infra) attention
that there is a confusion about the labels we are using for issues in
our trackers. Namely fedora-infrastructure, releng and centos-infra.
There was even a request to change them to something less confusing.
So we want to decide if this is really need to change, so we ask you to
take this quick survey [0] (this is an anonymous survey, nothing is
collected by us) to see if the change is really needed or people are
happy with current labels.
The survey will be closed on 7th March 2023.
On behalf of I&R Team,
Michal
[0] - https://forms.gle/J2HWDkw1UNuj8HYD8
Hi Everyone,
Our next board meeting will take place at 21:00 UTC next week:
`date -d "2023-03-08 21: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/BJ_FDo93s
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.
thanks,
--
Thomas 'alphacc' Oulevey
CentOS Board of Directors Secretary
alphacc(a)centosproject.org
Let's start discussing the future of wiki.centos.org !
There was a CentOS Docs SIG day happening on monday after Fosdem and
during that day, we started to discuss the future of wiki.centos.org.
As a reminder : https://wiki.centos.org is actually powered by moin
(http://moinmo.in/) which is :
- python 2.x based
- unmaintained
It's also running on CentOS Linux 7 (for these requirements), itself
going EOL next year. Also worth adding that it's under constant spammer
load, with plenty of bots trying to write content, be denied, and trying
in a different way, so it's really a "whack a mole" game.
For all these reasons, it has to be replaced by something else, (still a
wiki) or even better, be decommissioned entirely and eventually moved to
a git workflow.
FWIW, it's what is used for all websites from various SIGs under
https://sigs.centos.org (including the SIG guide itself,
https://sigs.centos.org/guide)
As a follow-up on the CentOS SIG day, an investigation (see
https://pagure.io/centos-infra/issue/1061) was started as a PoC to just
extract wiki content in a readable (static) format, so that we can still
host a "read-only" version (archived) of wiki content, while a new
service (wiki or else) would replace it.
All comments/remarks are welcome, and let's have a plan about what to do
(the sooner, the better)
Kind Regards,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
Hi all,
For the first time in CentOS history, we'll have two version going EOL
the same year, at just some week intervals, so we should already be
prepared about this, and the sooner, the better.
Per https://www.centos.org/centos-linux/ and
https://www.centos.org/centos-stream/#centos-stream-8 :
- June 30th 2024 for CentOS Linux 7
- May 31st 2024 for CentOS Stream 8
At the infra side, there are services that we still need to see working,
so we already started to add el9 support to our ansible roles and some
services are already (or will be soon) migrated to el9.
I intend to send multiple mails in the next hours/days about identified
applications for which we're still unsure if we should migrate these ,
or just let them behind (decommission), so if you see a topic/subject
for an application you're interested in, feel free to participate in
that specific thread (easier to read/follow than just everything in one
email thread). These emails should start with something like "RFC
(Request for comments) : future of <app>"
Let me just announce here in advance the (public) infra services running
on CentOS 7 that will just disappear when CentOS 7 itself will be EOL
(and so not receiving any update anymore) :
- mirror.centos.org : all Stream 9 (and above) mirror content is now on
its own dedicated mirror.stream.centos.org CDN setup, so there is no
need to keep an empty mirror.centos.org vhost with no content, as all
content will be moved (as usual) to vault.centos.org. So
mirror.centos.org A/AAAA records will be removed completely. (or we can
just have a simple vhost with a redirect to mirror.stream.centos.org)
- mirrorlist.centos.org : from Stream 9 (and above), it's using Fedora
infra mirrormanager instance for metalink= instead of mirrorlist= in
.repo files. We'll just decommission our mirror crawler (also running
with a mix of perl/python2 code), so not validating any mirror for
legacy/EOL releases. mirrorlist.centos.org A/AAAA records will be
removed in the following weeks after c7 will be EOL'ed.
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
* Image build systems: kiwi / livecd
* Tags and targets are now in CBS. We are now able to build images
* Thanks to all those that did that work
* We are not able to publish to the mirrors yet
* https://pagure.io/centos-infra/issue/1039
* !! Help is needed creating rpm-ostree stuff in kiwi !!
* https://github.com/OSInside/kiwi/issues/38
* kiwi can currently create the following images:
live media, OEM disk images, VM disk images, cloud images, container
images, WSL images, fstrees, squashfs images, filesystem tarballs,
liveinstall ISOs, PXE images, UEFI netboot images
* Image build systems: containers
* The SIG would like to build containers in kiwi, so that it is build on
CBS instead of elsewhere.
People Present (lines said)
---------------------------
* tdawson (47)
* Eighth_Doctor (34)
* salimma (15)
* davide (6)
* centguard (5)
Minutes:
https://www.centos.org/minutes/2023/February/centos-meeting.2023-02-23-19.0…
Log:
https://www.centos.org/minutes/2023/February/centos-meeting.2023-02-23-19.0…
Hi Folks,
As many of you know, CentOS Stream 8 is currently produced using an "inside
out" workflow, meaning RHEL builds happen first and then are reflected in
CentOS Stream afterward. This is not the case with CentOS Stream 9 where
builds are performed directly by maintainers at Red Hat from merge requests
in gitlab.com.
The CentOS Stream team is busy working on a project to migrate CentOS
Stream 8 to the gitlab.com/Stream-first workflow. This is an exciting step
to reflect CentOS Stream's true purpose in both currently active releases.
One effect of this transition, though, is that we need to migrate from the
old mbox buildsystem to the new Stream koji (
https://kojihub.stream.centos.org) To do this the team needs to pause
regular compose and push-to-mirror jobs to avoid a split-brain situation
with 2 separate systems. You may notice a lack of updates to the repos on
the mirrors for a few more weeks while this transition is completed. The
team's first priority is making sure that Red Hat maintainers take control
over the c8s branches in https://gitlab.com/redhat/centos-stream/rpms (and
builds in koji) and then the team will return to working on regular
composes and push-to-mirror operations.
If you have any questions in the interim, please reach out to me.
Cheers!
--
Brian Stinson