The FTP mirrors are fairly complex, especially when it comes to the way data is
kept in sync and monitored. There are many scripts that are scattered about that
makes the magic happen. Hopefully this documentation reveals the truth behind
the magic.

The nature of our system allows some flexibility to the services that we can
offer. We can serve as the master mirror for small projects, but also as a part
of a large project’s mirror infrastructure. Each set of data is referred to as a
‘tree’; each project may have one or more trees.

Note

This project has been tightly integrated into the OSL mirror infrastructure
and has a lot of hard coded references to hosts, paths and other bits.

As it stands now, the system is currently deployed using the OSL internal
CFEngine configuration management system. Documentation will be updated to
reflect how it should be installed externally.

Most of the files reside in /data/mirror on the nodes while some scripts are
located in /usr/local/sbin. In addition there are other services such as
xinetd, bwbar, etc that need to be configured outside these directories or the
current repository.