Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Jul 2003 15:27:24 -0400
From:      Ken Smith <kensmith@cse.Buffalo.EDU>
To:        freebsd-hubs@freebsd.org
Subject:   Mirror Site Requirements - Final Draft?
Message-ID:  <20030727192724.GA10869@electra.cse.Buffalo.EDU>

next in thread | raw e-mail | index | archive | help

I think this reflects our latest thoughts.  If I missed let me know.  Note
the distinction between Primary and Secondary doesn't really have any
"functional" meaning - it is just to help provide users with an indication
that a site *might* not have what they're looking for in the case of
a site being Secondary.  Beta testers should also be able to use the
list of Primaries as a guide to where they're likely to find the pre-release
builds sooner versus later (or not at all).  We can work a bit on fine
tuning what's available where later (see comment at the bottom).

Mirror Site Categories
----------------------

	- Distribution Site: ftp-master* site, ftp-master itself plus a set
	  of other machines that sync frequently from ftp-master and allow
	  only Official Mirror Sites to connect to them.

	- Primary Mirror Site: Sync at least once a day from a Distribution
	  Site, carry everything currently on ftp-master.

	- Secondary Mirror Site: Does not carry everything on ftp-master,
	  and/or syncs from a Primary Mirror Site (thus getting stuff slower).

Which category a Mirror Site fits in will be indicated on the Web page
listing the FTP mirrors, and that page will include a description of what
"Primary" versus "Secondary" means.  End-users don't need to know anything
about the Distribution Servers so they won't be mentioned in the Handbook
but will be described in the hubs article.


Requirements of all Mirror Sites
--------------------------------

1) Different user for sync jobs than anonymous FTP (and, if HTTP
   access is available, httpd).
2) Mechanism used for sync preserves (and can change later) file
   permissions.
3) Site Admin on mirror-announce@ list (still being created, not ready
   yet).  This will be a private (Official Mirrors only) list used only
   for announcements by mirror-admin@ and re@.  hubs@ will remain an
   open discussion list.
4) Directory archive sits in is /pub/FreeBSD.

Requirements for Primary Mirror Sites
-------------------------------------

1) Carries everything currently on ftp-master (note that is changing, we
   hope to drop the branches/ stuff).
2) Syncs with a Distribution Site at least once a day, preferrably twice
   a day.
3) Optionally provides access to other Official Mirror Sites through a
   secure mechanism (only allowing Official Mirror Sites to download
   "staged" releases).  This typically means running a special cvsupd
   or rsyncd with access restrictions.  Must check with mirror-admin@
   before granting this sort of access to confirm the requesting site
   is an Official Mirror Site.
4) Site Admin on hubs@ in addition to mirror-announce@.
5) Will be given a "ftpX.CC.freebsd.org" hostname and will be a candidate
   for becoming a "ftpX.freebsd.org" hostname.

Requirements for Secondary Mirror Sites
---------------------------------------

1) Simply carry all files needed for latest Production Release, which
   includes the packages for that release.  Note this means the packages
   in the -release directory for this release, not necessarily the package
   set that gets built on a roughly weekly basis.  Using FreeBSD 4.8
   for the i386 architecture as an example this means carrying:

	releases/i386/4.8-RELEASE/
	releases/i386/ISO-IMAGES/4.8/
	ports/i386/packages-4.8-release/

2) Syncs at least once a day from a Distribution Site or a Primary Mirror
   Site.
3) Will be given a "ftpX.CC.freebsd.org" name.

Misc. Comments
--------------

The http://www.freebsdmirrors.org/ site was mentioned.  We're talking
to the person who developed it now.  I had noticed its accuracy varies
quite a bit over time.  The way he collects the data relies on noticing
NS records and doing zone transfers which will break for zones we handle
centrally (e.g. the new us.freebsd.org zone :-/) and typically DNS Admins
are beginning to limit zone transfers as a security precaution.  IMO it's
a good idea but needs some re-working because of this issue along with
the extra architectures now (it only handles i386/alpha).  We're not sure
if he's interested in mucking with it at this point.



-- 
						Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030727192724.GA10869>