Setting up a mirror

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: 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 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.

• 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.

• Your should have some monitoring in place to check that your mirror is
  • serving the files using all the protocols it supports
  • updated periodically

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

rsync -av --delete rsync://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 (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: Maidenhead, UK
• 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 daily.

Some stats

OpenVZ download site is about 189Gb now (as of Aug 2015), so your mirror will need at least the same space. It is growing at about 3 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

• Download mirrors
• The status of OpenVZ mirrors