Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#63843 - {mirror} Update mirror configuration
Attached to Project:
Arch Linux
Opened by Rackspace (rackspace) - Thursday, 19 September 2019, 15:49 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 21 April 2022, 17:39 GMT
Opened by Rackspace (rackspace) - Thursday, 19 September 2019, 15:49 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 21 April 2022, 17:39 GMT
|
DetailsHello, we've been going through cleaning up some of our mirror profiles on projects we are actively mirroring. For our listing I noticed we were only set to "Worldwide" and HTTP, RSYNC with no listing for HTTPS. Our primary domain is globally load balanced via DNS so we'd prefer to keep the existing Worldwide entry, but based on troubleshooting it looks like that entry is only pulled if all other mirrors for a region fail. Thus we'd also like to have our region-specific locations added as well.
Mirror domain name mirror.rackspace.com dfw.mirror.rackspace.com ord.mirror.rackspace.com iad.mirror.rackspace.com lon.mirror.rackspace.com hkg.mirror.rackspace.com syd.mirror.rackspace.com Geographical location of the mirror (country) Worldwide US US US GB HK AU URLs for supported access methods (http(s), rsync) (no ftp) http://mirror.rackspace.com https://mirror.rackspace.com rsync://mirror.rackspace.com http://dfw.mirror.rackspace.com https://dfw.mirror.rackspace.com rsync://dfw.mirror.rackspace.com http://ord.mirror.rackspace.com https://ord.mirror.rackspace.com rsync://ord.mirror.rackspace.com http://iad.mirror.rackspace.com https://iad.mirror.rackspace.com rsync://iad.mirror.rackspace.com http://lon.mirror.rackspace.com https://lon.mirror.rackspace.com rsync://lon.mirror.rackspace.com http://hkg.mirror.rackspace.com https://hkg.mirror.rackspace.com rsync://hkg.mirror.rackspace.com http://syd.mirror.rackspace.com https://syd.mirror.rackspace.com rsync://syd.mirror.rackspace.com Your mirror's available bandwidth 1 Gbps per region An administrative contact email (optional, see below) Already subscribed to mirror mailing list (tier 1 mirrors) Rsync IPs so your server(s) can be allowed to sync off tier 0 (rsync.archlinux.org) Will provide if needed (tier 2 mirrors) The name of tier 1 mirror you are syncing from. kernel.org We're happy to apply to be listed as a Tier1 mirror for whichever regions would be a good fit, and/or if there is a desire to have another Worldwide(Various) tier1 mirror. |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Thursday, 21 April 2022, 17:39 GMT
Reason for closing: Implemented
Thursday, 21 April 2022, 17:39 GMT
Reason for closing: Implemented
As for tier 1 status: Would you sync from each region or would you sync once and then distribute the data internally? If you could quickly distribute the data internally that would essentially give us a few tier 1 mirrors in multiple regions for the price of one.
We'd be syncing once, currently from Dullas(IAD), but at some unknown point in the future this will change to Chicago(ORD). The content is then immediately distributed to our other 5 DCs. Currently this is done with child jenkins jobs on success of the master sync.
Thanks,
Judd
Please switch to one of the *_tier1 modules on "rsync://rsync.archlinux.org". You'll probably want "rsync://rsync.archlinux.org/kitchensink_tier1". Reply here once you've switched so I can close this request.
If you want to sync more often than once an hour, please consider using a script like this[1] to reduce the amount of rsync traffic when there are no changes.
[1] https://git.archlinux.org/infrastructure.git/tree/roles/syncrepo/files/syncrepo-template.sh
EDIT: I've whitelisted both IPs.
I see I've got access to the rsync server, but not yet to the kitchensync_tier1 module:
[judd.obannon@jenkins ~]$ rsync rsync://rsync.archlinux.org/
temp-archive temporary endpoint for the archive
ftp ftp area (most mirrors should use this)
ftp_tier1 ftp area (most mirrors should use this)
ftp_auth ftp area, passworded (same as 'ftp')
ftpfull ftp area (everything, including very old versions, except sources)
ftpfull_tier1 ftp area (everything, including very old versions, except sources)
ftpfull_auth ftp area (everything, including very old versions, except sources)
kitchensink ftp area (everything, including very old versions)
kitchensink_tier1 ftp area (everything, including very old versions)
kitchensink_auth ftp area (everything, including very old versions)
core core repository
extra extra repository
community community repository
testing testing repository
community-testing community-testing repository
[judd.obannon@jenkins ~]$ rsync rsync://rsync.archlinux.org/kitchensink_tier1/
@ERROR: access denied to kitchensink_tier1 from UNKNOWN (72.4.120.222)
rsync error: error starting client-server protocol (code 5) at main.c(1503) [receiver=3.0.6]
Do I need to auth to the kitchensync_auth module first?
Confirmed syncing normally from kitchensync_tier1. I'm pulling down everything now. going by historical size of the project I'm assuming the archive stuff won't be a space burden. If, however, it does how much of the archive content do you expect/require to be retained for a tier1 mirror? I didn't see this specifically called out in the mirror documentation.
Thank you again for your patience!
I was also looking at the DNS mapping for mirror.rackspace.com. [2] Most of Europe gets matched to a US mirror (iad). Is this something that can be tweaked?
Thanks for providing all these mirrors. :)
Edit: Used [3] to check ping times from different countries; they all seem to resolve mirror.rackspace.com to 72.4.120.219 (iad). (Can also test with geo.mirror.pkgbuild.com which our own GeoIP based mirror; seems to fare better, IP matching is mostly on-point and ping times are great.)
[1] https://archlinux.org/mirrors/rackspace.com/
[2] https://dnschecker.org/#A/mirror.rackspace.com
[3] https://tools.keycdn.com/ping