======================================================
#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
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
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