October 2024 - openSUSE Mirrors - openSUSE Mailing Lists

Hello all !
by ridyxx 18 Nov '24

18 Nov '24

Hello all hellas !

2 1

Travel Chernobyl
by ridyxx 18 Nov '24

18 Nov '24

I love traveling and interesting places to learn information and know more about it, and this is exactly what I learned about Chernobyl from this site - https://chernobylstory.com/ The latest news about the ghost town is very interesting and I personally read it in one breath, as you do, I think it will be very useful for those who are interested!

2 1

Travel
by ridyxx 29 Oct '24

29 Oct '24

I love traveling and interesting places to learn information and know more about it, and this is exactly what I learned about Chernobyl from this site - [сhernobylstory.com](https://chernobylstory.com/) The latest news about the ghost town is very interesting and I personally read it in one breath, as you do, I think it will be very useful for those who are interested!

1 0

opensuse-rsync project feedback
by Andrii Nikitin 22 Oct '24

22 Oct '24

Hej, On various occasions, I heard multiple requests about having a simple way to set up and maintain an openSUSE mirror. Since then I had some ideas about "projects" as they are defined at mirrors.opensuse.org, and the fact that each project may need a dedicated rsync process with customized individual check intervals and maybe some kind of notification from the server when new content is arrived, etc. E.g. Leap iso and repo files rarely change, so they might need to be checked less frequently than Leap updates, etc. But when a big sync starts for Leap quarterly updates (.iso files) - it shouldn't delay the sync of updates for long. With these ideas I implemented opensuse-rsync packages. Ideally users follow the following steps: * Choose a size of the mirror according to the list: https://github.com/andrii-suse/opensuse-rsync/blob/master/README.md#approxi… * Install the corresponding package, e.g. opensuse-rsync-typical (which will require approximately 1.2TB of disk space). * Enable the timers using the provided command. * Optionally add custom filters to a config. * Monitor and manage systemd services for each project. So, the idea is that such steps might be the default set of actions to set up a mirror (but not required). Further, it will be easier to gather feedback and implement improvements or add functionality. I would appreciate it if somebody had a chance to review this proposal and share ideas if it looks legit or why it is a bad idea. I will be glad to answer questions about the implementation or design decisions, etc. If no feedback is provided, I probably will add it as an experimental section to the wiki and wait for somebody to try it. Github: https://github.com/andrii-suse/opensuse-rsync OBS: https://build.opensuse.org/project/show/home:andriinikitin:opensuse-rsync Regards, Andrii Nikitin

3 6

rsync.opensuse.org - Large file count in repodata
by Ryan Nicholson 17 Oct '24

17 Oct '24

Context: <mirror>/update/leap/15.6/sle/repodata/ Recently, when mirroring, our local copy of "/update/leap/15.6/sle/repodata/" is pulling between 9 to 100GB of extra repodata files. For me, it appears to only affect updates/.../sle, with the largest being 15.6. However, repomd.xml as synced, is correct and links to 5 good files within repodata. Question: *Is it normal for a repodata pull to have this large amount of files appear during a sync?* We, of course, have rsync configured to "--delete" whatever it needs to during each synchronization. At this time, I believe we observe that only updates to the "sle" folder have this behavior. Cheers, T. Ryan Nicholson

2 1

Large file count of repodata
by Ryan Nicholson 16 Oct '24

16 Oct '24

Context: <mirror>/update/leap/15.6/sle/repodata/ Recently, when mirroring, our local copy of "/update/leap/15.6/sle/repodata/" is pulling between 9 to 100GB of extra repodata files. For me, it appears to only affect updates/.../sle, with the largest being 15.6. However, repomd.xml as synced, is correct and links to 5 good files within repodata. Question: *Is it normal for a repodata pull to have this large amount of files appear during a sync?* We, of course, have rsync configured to "--delete" whatever it needs to during each synchronization. At this time, I believe it's only updates to the "sle" folder that have this behavior. For now, I'll have my validation logic purge anything that's not referenced by the repomd.* files. Let me know if this philosophy is in error. Cheers, T. Ryan Nicholson

1 0