Text Blame History Raw

CentOS Mirror managements SOP

Depending on the CentOS version, (8-stream, 7 or 9-stream), yum/dnf repositories on client machines are configured to either use mirrorlist.centos.org or mirrors.centos.org. mirrors.centos.org is an alias to mirrors.fedoraproject.org and so is a MirrorManager instance hosted by Fedora infra team. Let's see which process to follow when we get a ticket (see Howto on the wiki ) to add/remove/modify a mirror entry in corresponding DB.

CentOS Stream 9

When we get a new request for CentOS Stream 9 mirror, the process goes like this :

  • ticket is reviewed by infra-and-releng team and tagged with mirrormanager label
  • assignee should :
    • verify that mirror isn't located at GeoIP level from an embargoed country
    • verify that provided URLs (http/https and - optional - rsync) are working
    • follow the link to that mirror in mirrormanager (needs sysadmin-web FAS group membership)
    • add the CentOS category and then add the URLs
    • update ticket with info and close

CentOS Linux 7 and 8-stream

When we get a new request for CentOS Linux 7 or 8-stream, the process goes like this :

  • ticket is reviewed by infra-and-releng team and tagged with mirror-linux label
  • assignee should :
    • verify that mirror isn't located at GeoIP level from an embargoed country
    • verify that provided URLs (http/https and - optional - rsync) are working
    • update ticket with info and close

Adding new mirror

To help with these steps, there is a simple wrapper/helper script on the machine behind https://mirror-status.centos.org. It will run some pre-flights checks and output the SQL statements to copy/paste into mysql to add the new mirror in mirmon DB.

The process to launch, when one has a shell on the mirmon node, is /var/lib/centos-mirrors/mirror-geo-check.py Follow the steps and then copy/paste mysql statement into mysql (against mirmon database)

Updating existing mirror