Hello.
How can i check validation of our mirror ?
http/https://opensuse.astra.in.ua/
Is everything is ok and if our local pcs or our clients pcs making an
update, it should download it from mirror. Right ?
Thx for answer.
Regards.
--
url: https://astra.in.ua/
mobile: +38(063)-321-57-50
email: noc(a)astra.in.ua
Hello openSUSE!
The openSUSE Release team has over time received quite some requests to
provide regular refreshes of install media. Some of these 15.X requests
date back to the 15.2 development cycle. The most recent request* is
from openSUSE Board on behalf of DocB.
The idea is to incorporate released updates into "refreshed" install
images. Having Quarterly Update (QU) setup* done early and doing this
regularly will ensure that we will react timely to various issues
affecting bootable media.
**Identification**
Images will have 15.3-N in the filename to distinguish from the
original GA images. N is the incremental number currently set to 2.
**QU Schedule and Availability**
Leap 15.3 Quarterly Update 1 File (*15.3-2*) are already available at
download-o-o and is ready to be mirrored. See our roadmap* for more
information about the schedule.
get.opensuse.org uses -Current symlinks which already point a the 15.3-
2 content. The idea is that the user would always download the latest
openSUSE Leap 15.X image available to the date.
I'd like to also inform the community that a request to provide a self-
update repository for the installer in 15.4 was declined on a regular
feature review meeting, as we believe that the QU approach provides a
sufficient way to regularly update the installer in openSUSE Leap.
Related article:
https://news.opensuse.org/2021/10/14/respin-of-os-leap-images-are-coming/
[0] https://etherpad.opensuse.org/p/ReleaseEngineering-20210721#L22
[1]
https://build.opensuse.org/project/show/openSUSE:Leap:15.3:Update:Respin
[3] https://download.opensuse.org/distribution/leap/15.3/iso/
[4]
https://en.opensuse.org/openSUSE:Roadmap#Schedule_of_Quarterly_Updates_for_…
[5] https://code.opensuse.org/leap/features/issue/26
Thank you
Lubos Kocman
openSUSE Leap Release Manager
While mirroring /tumbleweed/repo/oss from another mirror via rsync it became clear that these secondary mirrors do not provide atomic updates. The files are updated in random order. Most likely rsync was invoked without --delay-updates. Perhaps also without --partial and proper --partial-dir=DIR, in case this actually combines well with --delay-updates, just to avoid errors like rsync: send_files failed to open "/tumbleweed/repo/oss/x86_64/.lazarus-2.0.12-2.1.x86_64.rpm.C11vZI" (in opensuse): Permission denied (13)
I do not know for how long rsync mirrors are offered. Was there any effort to provide mirror admins with instructions about how to mirror a volatile installation repo properly?
It is required to transfer repodata/repomd.xml at the very end to keep the repo itself consistent.
It is required to transfer /boot/x86_64 with --delay-updates to make sure the installer does not access incompatible files. This part might be tricky.
While I could certainly implement all the required checks myself to have a consistent local mirror, I wonder if this was already solved in a generic way, given the issue exists since a decade. smt-server and rmt-server deal with the repodata part already, but they miss support to mirror the inst-sys. And of course they are unable to fix a bad secondary mirror.
Olaf
