Note: This web site is only kept up to date for OSG Software 1.2 (VDT 2.0.0). If you are looking for information for the most recent release, the RPM-based OSG Software 3.0, please see the OSG documentation web site

This document is for internal purposes only

It is outdated and no longer accurate

VDT Mirror Server

VDT mirrors pull from the rsync server at Configuration is in /etc/rsyncd.conf and the root password is the normal condor password. This machine also handles the Condor mirrors, so try not to screw it up.

If someone wants to host a mirror you need to get the root directory of their mirror. For the VDT, our root directory is -- it's the directory that holds all the caches, the software dir and whatnot. Take their mirror root, add it to MIRROR_LIST in /p/vdt/public/html/defs and rebuild all the caches from VDT 1.3.10 on.

Once that's done let them know they can start mirroring. They need to update their mirror at least once a day, and provide a contact who can mirror it on-demand if necessary. We recommend that they use the following rsync command:

rsync -avz --delete rsync:// <local mirror root>
But we don't really care -- all those options will just speed up the transfer. If they don't have room to mirror the complete VDT they could just do the software and cache directories, which will save about 10GB. All we require is that, whatever they mirror, they update it at least once a day.
rsync -avz --delete rsync:// <local mirror root>/software
rsync -avz --delete rsync:// <local mirror root>/vdt_1310_cache
That's really all there is to it. As usual, make-vdt does all the heavy lifting. In this case you'll want to look at build-scripts/atoms/, build-scripts/atoms/ and build-scripts/atoms/