Hi Neal,

Correct me if I am wrong - MirrorManager expects all mirrors have the same content, while MirrorBrain and MirrorCache tolerate divergents and are able to use from them whatever is available.

Actually MirrorCache does support metalinks, just the core problem is that it doesn't have access to exact file sizes yet. You can try e.g. :

curl -H 'Accept: */*, application/metalink+xml' -s https://mirrorcache-eu.opensuse.org/download/tumbleweed/repo/oss/x86_64/2048-cli-0.9.1+git.20181118-1.9.x86_64.rpm

Regards,

Andrii Nikitin

From: Neal Gompa <ngompa13@gmail.com>

This looks very cool, but I'm confused why we would do this instead of
using MirrorManager2[1] and collaborating on that project? The
documentation showing the differences between MirrorCache and
MirrorBrain seem to mirror the differences between MirrorManager2 and
MirrorBrain based on my memory of discussing this at oSC two years
ago. Moreover, MirrorManager2 already has self-service management of
mirrors. The main difference between MirrorManager2 and MirrorCache
seems to be that MirrorCache lacks metalink support, which I think we
would actually *want* to have.

Are there any other specific features that MirrorCache has that I'm missing?

[1]: https://github.com/fedora-infra/mirrormanager2/

--
真実はいつも一つ！/ Always, there's only one truth!