Difference between revisions of "Setting up a mirror"

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.

Requirements

Warning: Please do NOT set up public OpenVZ mirror if:

you don't have enough resources (disk space, bandwidth, admin staff);
you are not committed to maintaining it for at least years;
you do not have automatic monitoring in place and staff to fix it quickly.

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.

@@ Line 1: / Line 1: @@
+<languages />
+<translate>
+<!--T:1-->
 If you want to set up a mirror of OpenVZ downloads, here's how.
-== Requirements ==
+== Requirements == <!--T:2-->
-* The mirrored contents 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:3-->
+{{Warning|Please do NOT set up public OpenVZ mirror if:
+* you don't have enough resources (disk space, bandwidth, admin staff);
+* you are not committed to maintaining it for at least years;
+* you do not have automatic monitoring in place and staff to fix it quickly.}}
+<!--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).
+<!--T:6-->
 * Your mirror should be updated on a regular basis; 1 hour period is recommended.
-* Your should have some monitoring in place to check that your mirror is
+<!--T:7-->
-** serving the files using all the protocols it supports
+* 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
-** updated periodically
+<!--T:8-->
+If you can not set up a system conforming to the above requirements — please don't attempt it.
-If you can set up a system conforming to the above requirements — read on.
+== Setting up the mirroring process == <!--T:9-->
-== Setting up the mirroring process ==
+<!--T:10-->
+To initially mirror the contents, run:
-To initially mirror the contents, run
+<!--T:11-->
-<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>
+<!--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.
-== 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).
-== Announcing your mirror ==
+== Announcing your mirror == <!--T:15-->
+<!--T:16-->
+Final step is to announce the mirror. There are two options:
+<!--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]
+<!--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]):
+<!--T:19-->
+* '''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 [http://www.staff.science.uu.nl/~penni101/mirmon/svn/trunk/countries.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: [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.
-Final step is to announce the mirror by sending an email to [mailto:mirrors@openvz.org mirrors@openvz.org]. It should contain at least the following information:
+<!--T:20-->
+Example of information about new mirror:
-* physical location of your site (country, state/province, city);
+ <!--T:21-->
-* frequency of updates;
+Site: eu.download.openvz.org
-* URL(s) to access the mirror;
+ Type: Master
-* 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.
+ 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 ==
+== Some stats == <!--T:22-->
-OpenVZ download site is about 32 GB now (as of Apr 2009), so your mirror will need at least the same space. It is growing at about 1 GB a month.
+<!--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.
+<!--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.
-== See also ==
+== See also == <!--T:25-->
-* [[Download mirrors]]
+* [http://mirrors.openvz.org/ The status of OpenVZ mirrors]
+</translate>
 [[Category: HOWTO]]
 [[Category: Infrastructure]]

Difference between revisions of "Setting up a mirror"

Latest revision as of 08:45, 2 May 2017

Contents

Requirements

Setting up the mirroring process

Setting up an access to your mirror

Announcing your mirror

Some stats

See also

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Services

Donate

Tools