Testers needed: mirrormanager

Matt Domsch Matt_Domsch at dell.com
Tue Mar 13 17:47:48 UTC 2007

For a while now I've been working on a webapp/database called
mirrormanager to track the status of all the various mirror systems
that you graciously administer.  Right now, all the tracking (IP
addresses for the ACLs, yum mirror lists, static web pages listing the
mirrors by country, etc) are all manual - someone (lately, me), has to
edit a bunch of files for each change (add, remove, move a mirror).
So, I got tired and wrote a program to do that for me.

At this point, I'm looking for volunteers to try out the site, enter
their data, and let me know if something causes a python backtrace and
what you did to get there.  My goal is to shake enough bugs out that
it can be used *LIVE* for the Fedora 7 launch.


You need to have a Fedora Account System account.  You don't need to
sign the Contributor License Agreement, but you will have to accept
the Export Compliance statement listed there when you create a new

There will be an app that crawls your web site (either http or ftp),
at least once a day, to discover what content you're actually
carrying.  It uses HTTP HEAD or FTP DIR commands and keep-alives, so
it should be fast and not a huge load.

Source Code to mirrormanager is under the MIT/X11 license, and is
posted here:

The "Grand Idea" doc is here:

Some things you can do:
Create a new Site.  The Site is the administrative unit.  You can add
admins for your Site, which additional Fedora Account System
usernames, then they can do things with your Site's data.

Create Hosts for your Site.  Hosts are the individual systems that you
use to serve data.  If you're doing a round robin DNS, only list one
Host.  But you can have many hosts.

Hosts can have their own lists of IP ACLs, local netblocks (so we can
eventually try to route your local traffic to you automagically), a
list of allowed countries (some places can only serve traffic to a
limited number of countries), and the like.

Create Categories (Fedora Core, Fedora Extras, ...) for your Host.
More categories will exist as the content becomes available in the
masters - e.g. Fedora EPEL and Fedora Releases (for F7).

Create URLs (http, ftp, rsync) for your Categories.  You can list URLs
which are "Private", meaning they're for use by other mirrors only.
In this way we can start to create a tiering system, but with
non-publicly-published URLs.

Create SiteToSites.  This lets other Sites' admins see the Private

See the public mirror list.

See the rsync ACL list.  The goal is to replace most of ftp at redhat.com
with a script that reads this list once a day. :-)

Wanna help?  ==> fedora-infrastructure-list at redhat.com.

With your help, this should smooth out the mirror load, and make
release day go very easily.

Fedora Mirror Wrangler

Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

More information about the infrastructure mailing list