Project:Infrastructure/Mirrors/Wrangling

This guide Article description::lists the steps needed to properly wrangle (manage) new Gentoo mirrors.

Preparing and testing mirrors
1. New mirrors should file a bug under the "Mirrors" product, "New Server" component. If a request comes in via email, ask them to file the request on Bugzilla.

2. Ask for the following information on the bug, if not provided already:


 * Official mirror name (preferably not your hostname, but the name of your organization)
 * Mirror type: distfiles/releases, gentoo-portage. NOTE: gentoo-portage is always rsync only . Some mirrors may have rsync for distfiles as well. Do not be confused by the difference!
 * URLs: full protocol and path for release/distfile mirrors, hostname or IP for gentoo-portage mirrors
 * Hardware specifications
 * Bandwidth specifications (transfer speed, eg 100Mbit, and any limits you may have)
 * Location
 * Intended concurrent users (for each protocol, mirror type)
 * Admin contact name and email address (This address should be registered in Bugzilla so we can CC you to any bug reports)

3. Modify the summary to have the type of mirror and the city as well as country if possible.

4. Inform the mirror of testing policies, tell them the due date (when testing will be completed) and give them the following links to make sure their mirror(s) have been setup correctly:


 * Distfiles: https://www.gentoo.org/doc/en/source_mirrors.xml
 * gentoo-portage: https://www.gentoo.org/doc/en/rsync.xml

Our policy right now for testing duration is as follows:


 * New distfiles/gentoo-portage mirrors: 2 weeks from date of infra accepting the bug
 * Returning distfiles/gentoo-portage mirrors: Same hardware/IP - 1 week. Different hardware/IP - 2 weeks
 * Problematic mirrors: 1 week to fix the issue, else they're removed from rotation unless we're provided with valid reasons by the admins.
 * Rsync mirrors in any continental rotation on DNS with issues should be removed immediately from those until the issue is resolved. For example,,  . You can leave the mirror in its country's rotation.

Now the mirror is ready to be added officially.

For distfiles mirrors

 * 1) Add the mirror to git:  (check the format of the doc, follow the same).
 * 2) Send email to admin (and CC mirror-admin@gentoo.org!)
 * 3) Add the mirror/admin-email to the infra wiki.
 * 4) Put in the following comment and close the bug:

For gentoo-portage mirrors

 * 1) Add new host to the ACLs. Follow the format, re-use existing numbers for a country before adding new ones. To add an IP to the ACL:
 * 2) To add a new country, just make sure it isn't already there, then create one.
 * 3) Add the IP into the country (and if needed, continent) DNS rotation(s) in git-based DNS. For example, a new mirror in the US would be, so you will add the new IP:
 * 4) Add the mirror to git  (check the format of the doc, follow the same).
 * 5) Add the mirror/admin-email to the infra wiki.
 * 6) Put in the following comment (modify as needed) and close the bug:

For distfiles mirrors
1. Remove the mirror from git: (check the format of the doc, follow the same).

2. Remove the mirror/admin-email from the infra wiki.

3. Put in the following comment and close the bug:

''Removed $server_name from mirrors listings. Thanks for the hardware and bandwidth donation, your services helped many Gentoo Users. (You have no more obligation to monitor the gentoo-mirrors mailing list.)''

For gentoo-portage mirrors
1. Remove the IP from, at. Leave the existing rsyncX.$CC comment so that it is known that it should be reused.

2. Remove the IP from the country DNS rotation(s) in git-based DNS

3. Remove the mirror from CVS (check the format of the doc, follow the same).

4. Put in the following comment (modify as needed) and close the bug:

''Removed $server_name from ACLs, removed from DNS. Thanks for the hardware and bandwidth donation, your services helped many Gentoo users. (You have no more obligation to monitor the gentoo-mirrors mailing list.)''