Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • infrastructure infrastructure
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 110
    • Issues 110
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch LinuxArch Linux
  • infrastructureinfrastructure
  • Merge requests
  • !522

Add GeoIP domain for our sponsored mirros

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Kristian Klausen requested to merge klausenbusk/infrastructure:geomirror into master Jan 15, 2022
  • Overview 15
  • Commits 1
  • Pipelines 22
  • Changes 20

We had a GeoIP mirror in the past based on nginx and its GeoIP module, but it didn't perform very well, due to the high latency (asking a central server for the package and then redirected to the closest mirror).

One of the reasons for offering this service, is so we can relieve mirror.pkgbuild.com which is burning a ton of traffic (50TB/month), likely due to it being the default mirror in our Docker image. Another reason is so we can offer a link to our arch-boxes images in libosinfo (used by gnome-boxes, virt-install and virt-manager), with good enough performance for most users.

This time we take a different approach and use a DNS based solution, which means the latency penalty is only paid once (the first DNS request). The downside is that the mirrors must have a valid certificate for the same domain name, which makes using third-party mirrors a challenge. So for now, we are just using the sponsored mirorrs controlled by the DevOps team.

Fix #101 (closed)

Edited Apr 12, 2022 by Kristian Klausen
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: geomirror