On Tue, Jun 1, 2021 at 12:58 PM Carl George carl@redhat.com wrote:
There isn't a policy per say, we just rsync the ISOs that pungi generates, with the delete flag. It may be tempting to suggest "just don't use the delete flag", but that is unreasonable from a disk space perspective. I just checked the latest compose and the isos directory totals 27GB. We are doing new composes roughly weekly. Generating an extra 27GB worth of files every week, for ourselves and all mirrors, doesn't sound appealing.
As a project who mirrors your content, I agree, this would not work in the long run :-)
Would a "latest" symlink be useful, even if there is only one set of ISOs available? Are you actually interested in getting the previous ISOs, or do you just want a download URL that doesn't change?
Yes, I think that would be the best option. It would work for a variety of automation tools as well. Please do the same with the checksum file.
Thanks!
On Fri, May 28, 2021 at 11:56 AM Lance Albertson lance@osuosl.org wrote:
What is the current policy for Stream ISO's? It seems that it's
currently only one week which is problematic when trying to maintain your own packer templates and having to constantly update the filename and checksums. It seems as though long term, this method doesn't bode well for maintainability.
Would it be possible to do one of the following?
- Offer a filename symlink to the "current" build?
- Offer an ISO that exists longer than a week?
- Host archived ISOs on vault (or somewhere else) with some saner
retention
Thanks-
-- Lance Albertson Director Oregon State University | Open Source Lab _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-- Carl George
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel