Based on https://git.centos.org/centos/board/issue/82
Would it be possible to leave the SIG build roots available for RHEL releases for 30 days after the release EOL so folks can finalize their SIG packages (if they want)?
Hi,
Can you elaborate ? The way we understand this request is : you'd like to ensure that you can still build against RHEL 8 30 days after it will be EOL, right ? From an infra PoV in koji (cbs.centos.org) we can do that (as long as it's also on RH CDN, from which we pull from)
but I'd like to remind that mirror.centos.org and mirrorlist.centos.org will all be decommissioned when centos linux 7 itself will be EOL, so while you'll be able to build content, there will be no default place to push packages to . Have you considered that point in your request ? So if you can elaborate about your needs, that would be good (and ideally why not starting the discussion on the centos-devel : better than through a ticket on a tracker ?)
Metadata Update from @arrfab: - Issue tagged with: cbs-rhel8-buildroot, feature-request, need-more-info
Metadata Update from @zlopez: - Issue untagged with: cbs-rhel8-buildroot, feature-request, need-more-info - Issue priority set to: Waiting on Reporter (was: Needs Review)
Metadata Update from @zlopez: - Issue tagged with: cbs-rhel8-buildroot, feature-request, need-more-info
Adding some details from my side as I initially asked for clarification by the CentOS Board. This has been done after discussions in #643 and #786. The point about where to push packages to has been part of the request. The CentOS Board noted that these are technical details which are not decided by them, but should be discussed with the Infra SIG or others responsible. Same concerning how/where to provide centos-release-* packages. The main intent was to have an official statement about how long SIGs can expect that they'll be able to build content for RHEL and thus communicate expected availability and support of their content to users.
The CentOS Board only discussed that it is desirable to have build roots for RHEL releases available in CBS (for SIGs to consume) for 30 days after the release went EOL (end of maintenance support). During these 30 days after EOL no further syncs of the repositories are expected, i.e. no access to content provided as part of ELS is requested. EPEL seems to have a very similar policy. According to my understanding the request by @jcpunk is now to verify that there are no issues raised by infra concerning this request based on which the CentOS Board can then make a decision.
In case there is a positive decision by the CentOS Board the next step would then be to discuss where to push content to and open questions concerning centos-release-* packages.
hmm, I'd suggest either discuss that during the infra meeting, or rather on the centos-devel list, so that everybody can follow the discussion (better than in a tracker that only subscribed people and requester will see/consider) ...
You mean also for the discussion concerning the availability of RHEL buildroots? The discussion where to push content to and questions about centos-release-* imho should be done on centos-devel (was my plan to do it that way).
yes, the discussion about where to push : building against rhel is the easy part, but the whole cdn and mirrorlist support will disappear with centos linux 7 (stream 8 itself will be eol before centos linux 7) .. Tempted to then close this ticket and rather have a discussion/agreement/thread on centos-devel.
@jcpunk , @pjgeorg : what do you think ?
That works for me. Mostly this ticket was "is it possible for this to happen on the infra". The answer seems to be "yes it is possible." Now we can move onto having a broader chat.
I didn't want to have a chat going on, reach consensus, and then find out "yeah we can't do that"
Ok, closing for now and discussion can start on centos-devel then :)
PS: let's not forget the part of the infra that will disappear in june 2024 in the discussion though
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@pjgeorg did you want to start the thread?
@jcpunk I can start the thread. Will do so tomorrow. Need to collect all required information so that we have a good starting point.
Log in to comment on this ticket.