DeveloperWiki:新しいミラー

新しいミラーの追加

このテキストは Arch のパッケージのための新しいミラーを追加する方法の概要を説明しています。

個人的なミラーに関するノート

• ミラーのための帯域は無料ではありません。彼らはあなたに提供する全てのデータについて支払う必要があります
  • これはあなたが ISP に支払っていても適用されます
  • 完全なミラーは 50GB 以上のサイズがあります
• あなたがほとんど使ったことがないとしても、誰かにダウンロードされるパッケージはたくさんあります
• ミラー管理者は、あなたが必要とするパッケージのみをダウンロードすることを強く推奨しています
• 個人的なミラーをセットアップする前に、ここ に書かれている代わりの方法を確認するようにしてください

2つのティアを使用したミラーリング方式

高い負荷と帯域の制限が原因で、Arch Linux は2つのティアを使用したミラーリング方式を使用しています。

archlinux.org と1時間ごとに直接同期するティア1ミラーがいくつかあります。

他の全てのミラーはティア1ミラーの中の1つと同期する必要があります。archlinux.org と同期することは許可されていません。

ミラー管理者向け

ティア2必要要件

• Disk-space >= 60 GB
• Sync off a tier 1 mirror (see https://archlinux.org/mirrors/tier/1/)
• Sync all contents of the upstream mirror (i.e. do not sync only some repositories)
• Do not sync more often than every hour, but you should sync at least once a day
• Sync on a random minute so it is more likely the requests will be spaced out with other mirrors
• Use the following rsync options: -rtlvH --delete-after --delay-updates --safe-links
• If you ever wish to send downtime notifications to our users, please use the arch-mirrors-announce list. You do not need to subscribe to be able to post.
• http support

ティア1必要要件

• Tier 2 requirements
• Bandwidth >= 100Mbit/s
• rsync support
• Proven reliability (be a tier 2 mirror for a while and have reasonable uptime, response to out-of-sync notifications etc.)

You can use rsync directly or this script as a starting point. Please note that the script tries to minimize load and bandwidth used (about 3MiB of metadata for each rsync run as of 2018-03-01) in case there are no changes. Feel free to remove this check if you don't sync very often or your upstream mirror does not provide the lastupdate file.

機能リクエストを作成する

ノート: We are not accepting new ftp mirrors.

Go to https://bugs.archlinux.org and create a feature-request (category: mirrors) containing the following information:

• Mirror domain name
• Geographical location of the mirror (country)
• URLs for supported access methods (http(s), rsync) (no ftp)
• Your mirror's available bandwidth
• An administrative contact email (optional, see below)
• An alternative administrative contact email (optional)
• (tier 1 mirrors) Rsync IPs so your server(s) can be allowed to sync off tier 0 (rsync.archlinux.org)
• (tier 2 mirrors) The name of tier 1 mirror you are syncing from. You can find available tier 1 mirrors here

The contact email(s) will be used by Arch Linux staff to contact the mirror administrator if they have questions regarding the mirror or if there are problems with the mirror. If a contact email is not provided, the mirror listing may be removed at any time, especially if problems occur, without prior contact to the admin.

連絡先とメーリングリスト

Feel free to join the arch-mirrors mailing list which can be used for general discussion about our mirrors. If you want to inform our users about downtime of your mirror please use the arch-mirrors-announce mailing list. You do not need to subscribe to be able to post to arch-mirrors-announce.

If you want to reach the Arch Linux staff for questions, you can either use the arch-mirrors list, you can open a bug report on our tracker or you can send a mail to mirrors@archlinux.org.

Arch Linux 側

• Add the mirror info to the Django admin site
• Regenerate the rsync whitelist with the gen_rsyncd.conf.pl script - only for tier 1 mirrors, or when disabling access to a previously untiered mirror (also done by an hourly cronjob)
• Regenerate the pacman-mirrorlist package

ミラーサイズ

To give you an impression how much space will be needed for a mirror here are some numbers (as of 2018-03-01):

Mandatory:

• pool (all packages) - 42GB
• repositories (core, community, extra, testing, gnome-unstable, kde-unstable, multilib) - total ~100MB

Optional:

• iso - 7GB (encouraged)
• archive - 15GB (permanently frozen)
• other - 17GB
• sources - 50GB

Most mirrors do not sync archive, other and sources directories, but sync everything else (including temporary repositories), so usually you will need about 50GB reserved for Arch Linux mirror.

However, note that the required space may temporarily increase when a big rebuild happens and thus many packages exist twice in different versions. Please plan in a buffer of 30GB to 50GB on top of the above mentioned values.