Instructions for setting up a new distfile mirror.
1.
Creating a new distfile mirror
Abstract
Setting up a new distfile mirror nvolves the following steps:
- Acknowledging the bug on bugzilla
- Send the mirror admin instructions on accessing the private master distfile mirror
- Testing the mirror for a period of time to ensure consistency
- Creating an entry on the Main Gentoo Mirrors page
Bugzilla
The first step in creating a new distfile mirror is for the user to file a bug on http://bugs.gentoo.org. From there, the mirror admin should acknowledge the bug and verify that the following information was provided as part of the initial report:
- server name
- IP address of the mirror
- contact information of the server administrator
- maximum number of concurrent connections allowed
- server specs, including CPU, RAM and connection speed to the internet
- any other requirements listed on the Distfile Mirrors Policy document
If part of the information is missing, please request it as a follow-up to the bug. Then, continue to the next step.
Accessing the Private Master Distfile Mirror
Gentoo maintains a private, master distfile mirror which only other distfile mirrors are allowed to use. This ensures that our mirrors are always able to access the latest files when a new version of a popular package, such as KDE or GNOME, is released. As part of the distfile mirror setup process, you should send the mirror admin instructions on accessing this private mirror. If you do not have these instructions, you can obtain them from Kurt Lieber.
Once you have sent the instructions, please make a note in the bug report asking the mirror admin to update their cron scripts to point to the new master mirror.
Probationary Period
New distfile mirror candidates need to go through a probationary period of at least 48 hours and preferably 96 hours where their server is checked periodically for timely updates with gentoo.oregonstate.edu. During this time, monitor the distfile mirror to ensure it is updating at 4 hour intervals. If the mirror shows inconsistencies of any type, report them on the bug entry and work with the server admin to resolve them if possible. The easiest way to do this is to check the timestamp.chk file which can be found in the /distfiles/ directory on the mirror.
Note:
A "TODO" item is to write a script that will automate the monitoring process during the probationary period.
|
Adding Entries to the Main Mirrors page
After the mirror candidate has passed the probationary period, the mirror admin should create an entry for the mirror on our Gentoo Mirrors page.
Note:
Make one entry per protocol that the new mirror is running
|
To create the entries, check out the latest version of the mirrors.xml file from CVS. Make the updates to that file and commit it back to CVS.
|