I'm running a simple home mirror, but I managed to get into a situation where I have to use a bunch of custom excludes. I think we should be able to offer what people want nowadays.\

To my knowledge, hotstuff and other pre-configured rsync modules are no longer maintained and advised not to use. This leads people to maintain their own exclusion list for the rsync.

So I'm trying to improve my current experience at home and reduce the effort for others.

Project Description

I'd like to offer people with limited storage a super-easy way how to deploy a home mirror.

Ideally, Leap Micro + preconfigured combustion script. Boot and pull a pre-configured mirror container via cockpit (unless done in the combustion script) (160GB hotstuff, 320GB, etc ...). Done in like 5-8 minutes and already serving.

That's the easier part^

The more tricky part will be that nobody really touched are pre-configured rsync modules hotstuff etc for quite some time.

So refreshment of our pre-configured hotstuff, exposing it on github.com/openSUSEm, updating docs, and advertising is the next goal. Also, make a pre-recorded demo similar to the one I've done for Micro.

Trigger Ish recently configured a mirror for the Mauritius region and he struggled with quota issues. That only confirmed that I'm not alone who sees the issue. I shared with him my exclusion list and crontab line and he was happy. I think we can do a better job and nobody should be using these exclusion lists that require maintenance.

Goal for this Hackweek

Avoid using exclude list while being on a budget. Offer up-to-date pre-configured options. Offer simple solutions via containers for (not-only) people with rasp pi or similar home NAS.

rsync modules for mirrors with quota up2date in git (currently located on pontifex)
auto-deployment of mirror config to pontifex? (bonus, otherwise manual pull via request to admin@opensuse.org)
Set of container images (per offered rsync module)
Update docs (see resources) and publish a demo

Resources

https://en.opensuse.org/openSUSE:Mirror_howto

https://www.youtube.com/watch?v=ft8UVx9elKc

Join this project Leave this project

Looking for hackers with the skills:

hotstuff mirror opensuse rsync leapmicro containers raspberrypi

This project is part of:

Hack Week 21 Hack Week 23

Activity

over 2 years ago: tjyrinki_suse liked this project.

over 2 years ago: avicenzi joined this project.

over 2 years ago: pdostal joined this project.

over 2 years ago: pdostal liked this project.

over 2 years ago: Pharaoh_Atem liked this project.

over 2 years ago: Ishwon joined this project.

over 2 years ago: lkocman started this project.

over 2 years ago: lkocman added keyword "raspberrypi" to this project.

over 2 years ago: lkocman added keyword "hotstuff" to this project.

over 2 years ago: lkocman added keyword "mirror" to this project.

over 2 years ago: lkocman added keyword "opensuse" to this project.

over 2 years ago: lkocman added keyword "rsync" to this project.

over 2 years ago: lkocman added keyword "leapmicro" to this project.

over 2 years ago: lkocman added keyword "containers" to this project.

over 2 years ago: lkocman originated this project.

Comments

over 2 years ago by lrupp | Reply

Really love to see this happening! Just one note: if possible, please provide an RPM package that can easily be installed and updated on the download mirror (pontifex). Single scripts, deployed at some time on a machine and not maintained any longer are a way we really should avoid. I had/have this experience especially with pontifex too often in the past....
- over 2 years ago by lkocman | Reply
  
  Will keep that in mind. Yes I also think we want github and rpm deployment.

over 2 years ago by pjessen | Reply

I can't remember when, but I hardwired the hotstuff modules, after I realised no one had the insight to fix the knapsack stuff. I try to maintain the other rsync modules, but I don't spend much time on it. Wrt this project, I say go for it, as long as it doesn't mean any extra ongoing maintenance.
- over 2 years ago by lkocman | Reply
  
  Absolutely the goal is to simplify work. There will be some effort initially (refresh itself, initial bugfixes and rework deployment). That's what the hackweek is about.

over 2 years ago by lkocman | Reply

Initial drop of the current configuration (previously was under svn) https://github.com/openSUSE/opensuse-hotstuff (openSUSE Heroes can commit)

Very simple rpm utilizing obs_scm and explicit listing of individual files https://build.opensuse.org/request/show/975806 If infra team accepts this I'd like to start deploying via update from the infra repo.

Next step is refresh of the files :-)

over 2 years ago by lkocman | Reply

Perhaps a related project https://github.com/Firstyear/opensuse-proxy-cache

over 2 years ago by simotek | Reply

The cache @firstyear wrote (https://github.com/Firstyear/opensuse-proxy-cache) might be more useful for alot of people rather then syncing as a fully populated mirror it fetches packages etc on demand the first time they are requested and caches them for future use. A number of people in Australia are already using it with decent success, I have it running in a container on one of my machines and the rest point to that as there main repo. It means you don't have to download the whole mirror just the stuff you actually use.

over 2 years ago by avicenzi | Reply

Hi, just fix hotstuff modules, other problems are solved in https://github.com/opensuse-brasil/mirror-images (I think).

I still need to clean up and upload my swarm/compose files and create some k8s files.

I've been running my mirror for probably over a year now on containers, no issues, it works really well.

My mirror current runs on this repo https://github.com/alexandrevicenzi/opensuse-mirror-docker/, it has some flaws.

I would really love if modules just included versions for example:
- Leap 15.4 oss/non-oss and updates
- TW oss/non-oss and updates
In my mirror I have current (15.4), current -1 (15.3) and TW, no ports, no debugs, no sources. Just Leap 15.4 with updates uses about 75 GB, that's really good even if you want to host at home. If you add 15.3, and TW that goes up to 700 GB, and if you add debug, source, ports, that goes over 2 TB. Would be nice if it was easier to filter architectures, I have zero interest in hosting IBM/PPC packages, that's often mainframe, and most people would not use openSUSE TW in a mainframe.

I don't really like the idea that I need to update my include/exclude file every new release, if we can avoid that with hotstuff, that is better. It's easier to maintain modules on our side, than expect many to update their configs every new release.

over 2 years ago by avicenzi | Reply

I just had an idea, maybe a silly one, but what if we had a service where the user chooses what he wants to mirror, and they get a custom url that is plain text, and with this url, they can just wget before they run rsync in cron to get their desired include/exclude list.

I would like sometime like that, and to be honest, not that difficult to be achieved. I would be willing, or I may implement that myself, just for fun.

over 2 years ago by lkocman | Reply

I'm spending initial 2-3 days on the https://hackweek.opensuse.org/21/projects/opensuse-build-supported-by-suse-it

I'll be looking into this on Wednesday.

I did get an access to MySQL database for mirrorcache from Andrii, so scripting this should be possible

about 1 year ago by lkocman | Reply

Oky I've spent some extra time on this yesterday. So I'm making it part of this year's hackweek again :-)

Refreshed https://build.opensuse.org/package/show/home:lkocman:Images/opensuse-mirror I plan to rework it to use exclusively exclude lists and offer user a decent choice.

next task would be to have a convenient hack with openSUSE-repos to use my local mirror on my local network only. I was thinking of repo priority and passing url to service fiel as a zypper variable.