On Mon, Dec 22, 2014 at 12:43:15PM -0600, MUUG Mirror Manager wrote:
In any case, we're currently going to mirror ::fedora, ::fedora-secondary and ::fedora-epel.
In your MirrorManager entry I see "Fedora Linux" and "Fedora EPEL". I do not see "Fedora Secondary Arches" but instead "Fedora Archive" (with the wrong content). So something in this area does not seem 100% correct.
I'm not sure what problem you're seeing...
In the MirrorManager online web app, I don't have any categories added at all yet... correction, that's now fixed and I've added Fedora Linux, Fedora EPEL and Fedora Secondary with matching URLs.
I was confused by the different muug entries. I was looking at the old entry. If you add rsync URLs the crawler can scan the state of your mirror much faster.
The mirrormanager-client config file appears to be correct.
The content appears to be correct, or at least, the top few levels match what's on dl.fedoraproject.org. (I'm pulling from mirrors.us.kernel.org, since my IPv6 connection is way faster than IPv4 right now.)
Also, re Peer ASNs, is there any way to let me manage my own list? As a board member of MBIX, and a colleague of Les (at Les.net, the future hoster) I'm aware of what ASNs connect here via private peering and via the local IX. Right now, I count 12 ASNs being learned from the IX's route servers.
I think it should be possible for me to add those ASNs to your entry. I think this might be the first time Peer ASNs are used.
If there's some reasonable way to automate the creation of site-local netblocks, I could do it that way, too... there's 94 netblocks (excluding Hurricane Electric, who peers here too) involved.
Not really, I added 43 manually for my mirrors.
Adrian