Difference between revisions of "Setting up a mirror"
m (add example of information about new openvz mirror) |
|||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | <languages /> | ||
| + | <translate> | ||
| + | <!--T:1--> | ||
If you want to set up a mirror of OpenVZ downloads, here's how. | If you want to set up a mirror of OpenVZ downloads, here's how. | ||
| − | == Requirements == | + | == Requirements == <!--T:2--> |
| + | <!--T:3--> | ||
{{Warning|Please do NOT set up public OpenVZ mirror if: | {{Warning|Please do NOT set up public OpenVZ mirror if: | ||
* you don't have enough resources (disk space, bandwidth, admin staff); | * you don't have enough resources (disk space, bandwidth, admin staff); | ||
| Line 9: | Line 13: | ||
| − | * The mirrored | + | <!--T:4--> |
| + | * The mirrored content should be available through HTTP and FTP; both are optional but of course at least one should be there. In addition, you might provide rsync access — this is highly optional. | ||
| + | <!--T:5--> | ||
* Your http/ftp servers should return correct status for non-existent files (HTTP 404, FTP 550). | * Your http/ftp servers should return correct status for non-existent files (HTTP 404, FTP 550). | ||
| + | <!--T:6--> | ||
* Your mirror should be updated on a regular basis; 1 hour period is recommended. | * Your mirror should be updated on a regular basis; 1 hour period is recommended. | ||
| − | * | + | <!--T:7--> |
| − | + | * You should have some monitoring in place to check that your mirror is up to date and working properly and serving the files using all the protocols it supports | |
| − | |||
| + | |||
| + | <!--T:8--> | ||
If you can not set up a system conforming to the above requirements — please don't attempt it. | If you can not set up a system conforming to the above requirements — please don't attempt it. | ||
| − | == Setting up the mirroring process == | + | == Setting up the mirroring process == <!--T:9--> |
| + | <!--T:10--> | ||
To initially mirror the contents, run: | To initially mirror the contents, run: | ||
| + | <!--T:11--> | ||
* United States: <pre>rsync -av --delete rsync://download.openvz.org/openvz-download /local/path</pre> | * United States: <pre>rsync -av --delete rsync://download.openvz.org/openvz-download /local/path</pre> | ||
* Europe: <pre>rsync -av --delete rsync://eu.download.openvz.org/openvz-download /local/path</pre> | * Europe: <pre>rsync -av --delete rsync://eu.download.openvz.org/openvz-download /local/path</pre> | ||
| + | <!--T:12--> | ||
Next step is to add the cron job to run the same rsync command regularly. It is suggested to do that at least hourly. | Next step is to add the cron job to run the same rsync command regularly. It is suggested to do that at least hourly. | ||
| − | == Setting up an access to your mirror == | + | == Setting up an access to your mirror == <!--T:13--> |
| + | <!--T:14--> | ||
When you are ready to open up your mirror, set up HTTP/FTP access to it. Preferrably, the mirror should be available at <tt><nowiki>http://openvz.yoursite.com/</nowiki></tt> or <tt><nowiki>http://mirrors.yoursite.com/openvz/</nowiki></tt> (same with ftp). | When you are ready to open up your mirror, set up HTTP/FTP access to it. Preferrably, the mirror should be available at <tt><nowiki>http://openvz.yoursite.com/</nowiki></tt> or <tt><nowiki>http://mirrors.yoursite.com/openvz/</nowiki></tt> (same with ftp). | ||
| − | == Announcing your mirror == | + | == Announcing your mirror == <!--T:15--> |
| + | <!--T:16--> | ||
Final step is to announce the mirror. There are two options: | Final step is to announce the mirror. There are two options: | ||
| − | * send a pull request to [https://src.openvz.org/projects/OVZ/repos/openvz-mirrors/browse openvz-mirrors] repository and add | + | <!--T:17--> |
| + | * send a pull request to [https://src.openvz.org/projects/OVZ/repos/openvz-mirrors/browse openvz-mirrors] repository and add vvs@ as reviewer (preferred way) | ||
* send an email to [mailto:mirrors@openvz.org mirrors@openvz.org] | * send an email to [mailto:mirrors@openvz.org mirrors@openvz.org] | ||
| + | <!--T:18--> | ||
Announce should contain at least the following information (see [https://src.openvz.org/projects/OVZ/repos/openvz-mirrors/commits/c85b848e76c35b216ef157cbc6d1eb823a596d7e example of announce]): | Announce should contain at least the following information (see [https://src.openvz.org/projects/OVZ/repos/openvz-mirrors/commits/c85b848e76c35b216ef157cbc6d1eb823a596d7e example of announce]): | ||
| + | <!--T:19--> | ||
* '''Site:''' - website address. Example: hosteurope.de. | * '''Site:''' - website address. Example: hosteurope.de. | ||
* Direct links to OpenVZ files on your mirror (http, ftp, rsync). Example: | * Direct links to OpenVZ files on your mirror (http, ftp, rsync). Example: | ||
| Line 56: | Line 72: | ||
* '''Master site''' - currently we have two master sites: [https://download.openvz.org download.openvz.org] (USA) and [https://eu.download.openvz.org eu.download.openvz.org] (Switzerland, Europe). Please setup mirroring from nearest OpenVZ master site and specify it in this field. | * '''Master site''' - currently we have two master sites: [https://download.openvz.org download.openvz.org] (USA) and [https://eu.download.openvz.org eu.download.openvz.org] (Switzerland, Europe). Please setup mirroring from nearest OpenVZ master site and specify it in this field. | ||
| + | <!--T:20--> | ||
Example of information about new mirror: | Example of information about new mirror: | ||
| − | Site: eu.download.openvz.org | + | <!--T:21--> |
| + | Site: eu.download.openvz.org | ||
Type: Master | Type: Master | ||
OVZ-https: eu.download.openvz.org/ | OVZ-https: eu.download.openvz.org/ | ||
| Line 71: | Line 89: | ||
State: Enabled | State: Enabled | ||
| − | == Some stats == | + | == Some stats == <!--T:22--> |
| + | <!--T:23--> | ||
OpenVZ download site is about 103 Gb now (as of Aug 2015), so your mirror will need at least the same space. It is growing at about 1.5 GB per month. | OpenVZ download site is about 103 Gb now (as of Aug 2015), so your mirror will need at least the same space. It is growing at about 1.5 GB per month. | ||
| + | <!--T:24--> | ||
The traffic for download.openvz.org is about 3T to 15T per month; it should be much lower than that for your mirror. | The traffic for download.openvz.org is about 3T to 15T per month; it should be much lower than that for your mirror. | ||
| − | == See also == | + | == See also == <!--T:25--> |
* [http://mirrors.openvz.org/ The status of OpenVZ mirrors] | * [http://mirrors.openvz.org/ The status of OpenVZ mirrors] | ||
| + | </translate> | ||
[[Category: HOWTO]] | [[Category: HOWTO]] | ||
[[Category: Infrastructure]] | [[Category: Infrastructure]] | ||
Latest revision as of 08:45, 2 May 2017
<languages /> <translate> If you want to set up a mirror of OpenVZ downloads, here's how.
Contents
Requirements
|
Warning: Please do NOT set up public OpenVZ mirror if:
|
- The mirrored content should be available through HTTP and FTP; both are optional but of course at least one should be there. In addition, you might provide rsync access — this is highly optional.
- Your http/ftp servers should return correct status for non-existent files (HTTP 404, FTP 550).
- Your mirror should be updated on a regular basis; 1 hour period is recommended.
- You should have some monitoring in place to check that your mirror is up to date and working properly and serving the files using all the protocols it supports
If you can not set up a system conforming to the above requirements — please don't attempt it.
Setting up the mirroring process
To initially mirror the contents, run:
- United States:
rsync -av --delete rsync://download.openvz.org/openvz-download /local/path
- Europe:
rsync -av --delete rsync://eu.download.openvz.org/openvz-download /local/path
Next step is to add the cron job to run the same rsync command regularly. It is suggested to do that at least hourly.
Setting up an access to your mirror
When you are ready to open up your mirror, set up HTTP/FTP access to it. Preferrably, the mirror should be available at http://openvz.yoursite.com/ or http://mirrors.yoursite.com/openvz/ (same with ftp).
Announcing your mirror
Final step is to announce the mirror. There are two options:
- send a pull request to openvz-mirrors repository and add vvs@ as reviewer (preferred way)
- send an email to mirrors@openvz.org
Announce should contain at least the following information (see example of announce):
- Site: - website address. Example: hosteurope.de.
- Direct links to OpenVZ files on your mirror (http, ftp, rsync). Example:
- OVZ-https: download.openvz.org/
- OVZ-ftp: download.openvz.org/
- OVZ-rsync: download.openvz.org/openvz-download/
- Maintainer - email address of mirror admin (whom to contact in case of problems). It will better be some generic address (like mirroradmin@ or something), forwarded to at least a few people.
- Country (code of country from ISO 3166-1, see a list here)
- Location - physical location of your mirror. Example: Sergiev Posad, Moscow region, Russia.
- Sponsor - name of your organization
- IPv6 - IPv6 support for your mirror (yes, no).
- Comment - additional information, like bandwidth, update frequency etc. Example: 1GB connection, updated hourly.
- Master site - currently we have two master sites: download.openvz.org (USA) and eu.download.openvz.org (Switzerland, Europe). Please setup mirroring from nearest OpenVZ master site and specify it in this field.
Example of information about new mirror:
Site: eu.download.openvz.org
Type: Master OVZ-https: eu.download.openvz.org/ OVZ-ftp: eu.download.openvz.org/ OVZ-rsync: eu.download.openvz.org/openvz-download/ Maintainer: Sergey Bronnikov <sergeyb@openvz.org> Country: ch Location: Sponsor: Virtuozzo IPv6: yes Comment: Master site State: Enabled
Some stats
OpenVZ download site is about 103 Gb now (as of Aug 2015), so your mirror will need at least the same space. It is growing at about 1.5 GB per month.
The traffic for download.openvz.org is about 3T to 15T per month; it should be much lower than that for your mirror.
See also
</translate>
