Hi all,
As you're all aware (we sent multiple mails in the last year about this), CentOS 7 and Stream 8 will go EOL soon : https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-and...
Let's lists some things that will happen on the CentOS Infrastructure as we'll be approching (or passed) these dates :
# CentOS 7/8s content itself Usual process : content will be archived to https://vault.centos.org and removed from mirror.centos.org completely, with just a simple readme file dropped here (for example http://mirror.centos.org/centos/8/readme for already EOL'ed version). Worth knowing that some SIGs are still building for RHEL8, still supported for SIGs through https://cbs.centos.org so such kind of content will continue to be available there as long as SIGs can build against/for it
# CBS/koji (https://cbs.centos.org) No impact on CBS env itself ( not running centos 7 nor 8s for a long time now) but the various build tag reflecting centos 7 and 8s will be locked so that nobody would be able to build content anymore : that would even be impossible as content itself will have been removed from mirror.centos.org (internally used for cbs build tags)
# CentOS Forums (https://forums.centos.org) : still running on centos 7 and even if that's easy to migrate to newer/supported EL version, it was decided to just shutdown the service (based on discussion with the actual moderation team). An option (to be announced on forums.centos.org ?) is to eventually start moving thread/discussions on Fedora discourse (There is already a CentOS category there : https://discussion.fedoraproject.org/c/neighbors/centos/71) So the plan is just to shutdown forums.centos.org and remove A/AAAA records from DNS
# mirrorlist.centos.org service : Starting from Stream 9 (and above), deployed CentOS instance ares 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. That means that people still running CentOS 7 or 8-stream will not have functional yum/dnf stack, except if they point to either vault or have internal mirror but at least people would be aware that distro itself is EOL and that they shouldn't expect to receive any update anymore
# CentOS mailing-lists Currently running on mailman2 stack, on top of CentOS 7 linux : there is WIP to port everything to up2date mailman3 stack, actually packaged for EPEL9. We have successfully imported archives into mailman3 and same for lists config but let's start a different/separate thread to discuss changes (like renaming lists, see next coming thread)
Kind Regards,
On 18/03/2024 08.28, Fabian Arrotin wrote:
Hi all,
As you're all aware (we sent multiple mails in the last year about this), CentOS 7 and Stream 8 will go EOL soon : https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-and...
Let's lists some things that will happen on the CentOS Infrastructure as we'll be approching (or passed) these dates :
# CentOS 7/8s content itself Usual process : content will be archived to https://vault.centos.org and removed from mirror.centos.org completely, with just a simple readme file dropped here (for example http://mirror.centos.org/centos/8/readme for already EOL'ed version). Worth knowing that some SIGs are still building for RHEL8, still supported for SIGs through https://cbs.centos.org so such kind of content will continue to be available there as long as SIGs can build against/for it
# CBS/koji (https://cbs.centos.org) No impact on CBS env itself ( not running centos 7 nor 8s for a long time now) but the various build tag reflecting centos 7 and 8s will be locked so that nobody would be able to build content anymore : that would even be impossible as content itself will have been removed from mirror.centos.org (internally used for cbs build tags)
# CentOS Forums (https://forums.centos.org) : still running on centos 7 and even if that's easy to migrate to newer/supported EL version, it was decided to just shutdown the service (based on discussion with the actual moderation team). An option (to be announced on forums.centos.org ?) is to eventually start moving thread/discussions on Fedora discourse (There is already a CentOS category there : https://discussion.fedoraproject.org/c/neighbors/centos/71) So the plan is just to shutdown forums.centos.org and remove A/AAAA records from DNS
# mirrorlist.centos.org service : Starting from Stream 9 (and above), deployed CentOS instance ares 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. That means that people still running CentOS 7 or 8-stream will not have functional yum/dnf stack, except if they point to either vault or have internal mirror but at least people would be aware that distro itself is EOL and that they shouldn't expect to receive any update anymore
So SIGs building for RHEL8 might have to replace the mirrorlist= line in their .repo files (in case they provide any) by a baseurl=.
Personally I'd prefer having SIG content built for RHEL8 being pushed to mirror.stream.centos.org due to these changes (incl. sources and debuginfo) just like content built for RHEL 9 and Stream 9.
# CentOS mailing-lists Currently running on mailman2 stack, on top of CentOS 7 linux : there is WIP to port everything to up2date mailman3 stack, actually packaged for EPEL9. We have successfully imported archives into mailman3 and same for lists config but let's start a different/separate thread to discuss changes (like renaming lists, see next coming thread)
Kind Regards,
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 18/03/2024 10:48, Peter Georg wrote:
On 18/03/2024 08.28, Fabian Arrotin wrote:
<snip>
# mirrorlist.centos.org service : Starting from Stream 9 (and above), deployed CentOS instance ares 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. That means that people still running CentOS 7 or 8-stream will not have functional yum/dnf stack, except if they point to either vault or have internal mirror but at least people would be aware that distro itself is EOL and that they shouldn't expect to receive any update anymore
So SIGs building for RHEL8 might have to replace the mirrorlist= line in their .repo files (in case they provide any) by a baseurl=.
Personally I'd prefer having SIG content built for RHEL8 being pushed to mirror.stream.centos.org due to these changes (incl. sources and debuginfo) just like content built for RHEL 9 and Stream 9.
That's the second option on the table : push these to mirror.stream.centos.org and so use metalink=, metalinks being served by mirrormanager . I don't mind one or the other but for people used to eventually search for src.rpm/debuginfo on vault.centos.org/debuginfo.centos.org for these packages, suddenly they'd have to search elsewhere .. but one way or another it's a small change anyway so I personally don't mind adapting the releng process to push to mirror.stream.centos.org and so content would land under https://mirror.stream.centos.org/SIGs/8
Let's wait on other SIGs' feedback (for those also building against/for RHEL 8) and we'll have a final decision about the direction to take soon
On 18/03/2024 12:59, Fabian Arrotin wrote:
On 18/03/2024 10:48, Peter Georg wrote:
On 18/03/2024 08.28, Fabian Arrotin wrote:
<snip> >> >> # mirrorlist.centos.org service : >> Starting from Stream 9 (and above), deployed CentOS instance ares >> 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. >> That means that people still running CentOS 7 or 8-stream will not >> have functional yum/dnf stack, except if they point to either vault >> or have internal mirror but at least people would be aware that >> distro itself is EOL and that they shouldn't expect to receive any >> update anymore > > So SIGs building for RHEL8 might have to replace the mirrorlist= line > in their .repo files (in case they provide any) by a baseurl=. > > Personally I'd prefer having SIG content built for RHEL8 being pushed > to mirror.stream.centos.org due to these changes (incl. sources and > debuginfo) just like content built for RHEL 9 and Stream 9. >
That's the second option on the table : push these to mirror.stream.centos.org and so use metalink=, metalinks being served by mirrormanager . I don't mind one or the other but for people used to eventually search for src.rpm/debuginfo on vault.centos.org/debuginfo.centos.org for these packages, suddenly they'd have to search elsewhere .. but one way or another it's a small change anyway so I personally don't mind adapting the releng process to push to mirror.stream.centos.org and so content would land under https://mirror.stream.centos.org/SIGs/8
Let's wait on other SIGs' feedback (for those also building against/for RHEL 8) and we'll have a final decision about the direction to take soon
No other SIG commented on the proposal so I guess Peter that you win !
Going once, going twice ....
On 28/03/2024 18:19, Fabian Arrotin wrote:
On 18/03/2024 12:59, Fabian Arrotin wrote:
On 18/03/2024 10:48, Peter Georg wrote:
On 18/03/2024 08.28, Fabian Arrotin wrote:
<snip> >> >> # mirrorlist.centos.org service : >> Starting from Stream 9 (and above), deployed CentOS instance ares >> 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. >> That means that people still running CentOS 7 or 8-stream will not >> have functional yum/dnf stack, except if they point to either vault >> or have internal mirror but at least people would be aware that >> distro itself is EOL and that they shouldn't expect to receive any >> update anymore > > So SIGs building for RHEL8 might have to replace the mirrorlist= line > in their .repo files (in case they provide any) by a baseurl=. > > Personally I'd prefer having SIG content built for RHEL8 being pushed > to mirror.stream.centos.org due to these changes (incl. sources and > debuginfo) just like content built for RHEL 9 and Stream 9. >
That's the second option on the table : push these to mirror.stream.centos.org and so use metalink=, metalinks being served by mirrormanager . I don't mind one or the other but for people used to eventually search for src.rpm/debuginfo on vault.centos.org/debuginfo.centos.org for these packages, suddenly they'd have to search elsewhere .. but one way or another it's a small change anyway so I personally don't mind adapting the releng process to push to mirror.stream.centos.org and so content would land under https://mirror.stream.centos.org/SIGs/8
Let's wait on other SIGs' feedback (for those also building against/for RHEL 8) and we'll have a final decision about the direction to take soon
No other SIG commented on the proposal so I guess Peter that you win !
Going once, going twice ....
As I started to work on a checklist with Adam Samalik for the CentOS Stream 8 EOL process, I was wondering about *when* we want to start moving the SIG content that is built for/against RHEL8 to mirror.stream.centos.org : either we do it when Stream 8 is EOL (next month ?) or end of June (when CentOS 7 itself goes EOL)
Personally that doesn't change anything for me, apart from a date when the needed releng script process should be pushed, but from a SIG perspective, (and surely for people/users consuming these packages) it should be properly announced/communicated.
So what are SIGs' chairs thinking about that ? (basically SIGs that opted in for rhel8 buildroots back when it was proposed as an option : https://pagure.io/centos-infra/issues?status=all&tags=cbs-rhel8-buildroo...)
On 11/04/2024 14.56, Fabian Arrotin wrote:
On 28/03/2024 18:19, Fabian Arrotin wrote:
On 18/03/2024 12:59, Fabian Arrotin wrote:
On 18/03/2024 10:48, Peter Georg wrote:
On 18/03/2024 08.28, Fabian Arrotin wrote:
<snip> >> >> # mirrorlist.centos.org service : >> Starting from Stream 9 (and above), deployed CentOS instance ares >> 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. >> That means that people still running CentOS 7 or 8-stream will not >> have functional yum/dnf stack, except if they point to either vault >> or have internal mirror but at least people would be aware that >> distro itself is EOL and that they shouldn't expect to receive any >> update anymore > > So SIGs building for RHEL8 might have to replace the mirrorlist= > line in their .repo files (in case they provide any) by a baseurl=. > > Personally I'd prefer having SIG content built for RHEL8 being > pushed to mirror.stream.centos.org due to these changes (incl. > sources and debuginfo) just like content built for RHEL 9 and Stream 9. >
That's the second option on the table : push these to mirror.stream.centos.org and so use metalink=, metalinks being served by mirrormanager . I don't mind one or the other but for people used to eventually search for src.rpm/debuginfo on vault.centos.org/debuginfo.centos.org for these packages, suddenly they'd have to search elsewhere .. but one way or another it's a small change anyway so I personally don't mind adapting the releng process to push to mirror.stream.centos.org and so content would land under https://mirror.stream.centos.org/SIGs/8
Let's wait on other SIGs' feedback (for those also building against/for RHEL 8) and we'll have a final decision about the direction to take soon
No other SIG commented on the proposal so I guess Peter that you win !
Going once, going twice ....
As I started to work on a checklist with Adam Samalik for the CentOS Stream 8 EOL process, I was wondering about *when* we want to start moving the SIG content that is built for/against RHEL8 to mirror.stream.centos.org : either we do it when Stream 8 is EOL (next month ?) or end of June (when CentOS 7 itself goes EOL)
Personally that doesn't change anything for me, apart from a date when the needed releng script process should be pushed, but from a SIG perspective, (and surely for people/users consuming these packages) it should be properly announced/communicated.
So what are SIGs' chairs thinking about that ? (basically SIGs that opted in for rhel8 buildroots back when it was proposed as an option : https://pagure.io/centos-infra/issues?status=all&tags=cbs-rhel8-buildroo...)
For me both dates are fine, with a slight bias towards next month.
Just a thought as we have to keep in mind that there are not really many (or any?) centos-release-* packages for content built for rhel8 targets (there is no extras8-extras-common-el8 build target): How much work would it be to have content pushed to both locations for a period of time, e.g., starting now until Stream 8 is EOL? This would allow users to start updating their configurations now.
On 12/04/2024 12:22, Peter Georg wrote: <snip>
No other SIG commented on the proposal so I guess Peter that you win !
Going once, going twice ....
As I started to work on a checklist with Adam Samalik for the CentOS Stream 8 EOL process, I was wondering about *when* we want to start moving the SIG content that is built for/against RHEL8 to mirror.stream.centos.org : either we do it when Stream 8 is EOL (next month ?) or end of June (when CentOS 7 itself goes EOL)
Personally that doesn't change anything for me, apart from a date when the needed releng script process should be pushed, but from a SIG perspective, (and surely for people/users consuming these packages) it should be properly announced/communicated.
So what are SIGs' chairs thinking about that ? (basically SIGs that opted in for rhel8 buildroots back when it was proposed as an option : https://pagure.io/centos-infra/issues?status=all&tags=cbs-rhel8-buildroo...)
For me both dates are fine, with a slight bias towards next month.
Just a thought as we have to keep in mind that there are not really many (or any?) centos-release-* packages for content built for rhel8 targets (there is no extras8-extras-common-el8 build target): How much work would it be to have content pushed to both locations for a period of time, e.g., starting now until Stream 8 is EOL? This would allow users to start updating their configurations now.
I'll not modify the existing releng/sign/push process to just that "corner case" but instead I'll have a (temporary) cron job on the main reference mirror for mirror.stream.centos.org that will keep both in parallel. So still pushing to location that is authoritative for http://mirror.centos.org/centos/8/ but primary server (authoritative) will keep also in sync content for https://mirror.stream.centos.org/SIGs/8/ It's already implemented so you can start communicating new URLs for your users :-)
PS: wondering about the *debuginfo* and *src.rpm* packages though : actually these are still pushed to debuginfo.centos.org and vault.centos.org. Would be worth consolidating when c8s is EOL to also start composing repositories with all in one repositories (so like for 9s ? )
On 12/04/2024 14.56, Fabian Arrotin wrote:
On 12/04/2024 12:22, Peter Georg wrote:
<snip> >>> >>> No other SIG commented on the proposal so I guess Peter that you win ! >>> >>> Going once, going twice .... >>> >> >> As I started to work on a checklist with Adam Samalik for the CentOS >> Stream 8 EOL process, I was wondering about *when* we want to start >> moving the SIG content that is built for/against RHEL8 to >> mirror.stream.centos.org : either we do it when Stream 8 is EOL (next >> month ?) or end of June (when CentOS 7 itself goes EOL) >> >> Personally that doesn't change anything for me, apart from a date >> when the needed releng script process should be pushed, but from a >> SIG perspective, (and surely for people/users consuming these >> packages) it should be properly announced/communicated. >> >> So what are SIGs' chairs thinking about that ? (basically SIGs that >> opted in for rhel8 buildroots back when it was proposed as an option >> : >> https://pagure.io/centos-infra/issues?status=all&tags=cbs-rhel8-buildroot&close_status=) > > For me both dates are fine, with a slight bias towards next month. > > Just a thought as we have to keep in mind that there are not really > many (or any?) centos-release-* packages for content built for rhel8 > targets (there is no extras8-extras-common-el8 build target): How much > work would it be to have content pushed to both locations for a period > of time, e.g., starting now until Stream 8 is EOL? This would allow > users to start updating their configurations now.
I'll not modify the existing releng/sign/push process to just that "corner case" but instead I'll have a (temporary) cron job on the main reference mirror for mirror.stream.centos.org that will keep both in parallel. So still pushing to location that is authoritative for http://mirror.centos.org/centos/8/ but primary server (authoritative) will keep also in sync content for https://mirror.stream.centos.org/SIGs/8/ It's already implemented so you can start communicating new URLs for your users :-)
Thanks!
PS: wondering about the *debuginfo* and *src.rpm* packages though : actually these are still pushed to debuginfo.centos.org and vault.centos.org. Would be worth consolidating when c8s is EOL to also start composing repositories with all in one repositories (so like for 9s ? )
I agree. I'd prefer these to be consolidated once c8s is EOL.
-
Fabian Arrotin -
Peter Georg