Date: Wed, 16 Jul 2003 11:54:48 -0400 From: Ken Smith <kensmith@cse.Buffalo.EDU> To: freebsd-hubs@freebsd.org Subject: Mirror Site Requirements - Summary thus far... Message-ID: <20030716155448.GA11005@electra.cse.Buffalo.EDU>
next in thread | raw e-mail | index | archive | help
Is this a fair summary?
1) As painful as it might be, when a standard is settled on it will apply
to both existing and new sites. The standard will hopefully be low
enough to not cause too much fallout of existing sites but it's the
service level to end-users we're trying to make sure we keep reasonable.
2) To keep things simple there will three tiers of Official Mirror Sites.
The tiering labels are not necessarily a mapping of where sites get
the bits from, though it does have a small impact. The tiering labels
are more concerned with "how much stuff" and "how fast it arrives" for
the various sites.
3) Tier-0 are the ftp-master* sites, they only allow connections from
Official Mirror Sites.
4) Tier-1 sites carry "everything" (see below) and are candidates for
being in the TLD but we don't want *too* many sites in the TLD so
not all of the Tier-1's will be in the TLD. All sites that are in
the TLD will be Tier-1's, well connected, etc.
5) Tier-2 sites carry the materials needed to do a successful FTP-based
install (stuff in releases/ and ports/ directories) for the most current
versions of the -stable and -current branches (that would currently
mean FreeBSD 4.8 and FreeBSD 5.1) of at least one architecture. Note
I'm thinking sysinstall here - it's useless for sysinstall to list a
site with ISO's only... Carrying the roughly-weekly updated sets of
packages is not *required*, just the -release directory of packages
for, in this case, 4.8 and 5.1.
6) I adapt the Web pages (and sysinstall?) to have some indication of
whether a site is Tier-1 or Tier-2 with the notice saying something
along the lines of "Tier-2 sites carry enough stuff to do a successful
install for the architectures they do carry, but they may not carry all
of the architectures".
With this layout re@ will know that the machines in the TLD are likely
to have the bits fastest so the beta testers can check there first,
and they're not likely to cause a *huge* load issue on the servers.
Beta testers being (hopefully :-) above average users they can probably
poke around on their own and find something suitable if they for some
reason have problems with the "get it from a TLD machine" algorithm.
As for "everything"... :-/ The most convenient definition I can think
of is "whatever is on ftp-master" but I don't know if that's overkill.
Given the above layout we don't *need* a huge number of machines that
qualify as Tier-1 (14 at the moment :-) and I'm guessing we've got more
than that. It's not a tragedy for a host to "slip" to Tier-2, note that
none of this addresses what a machine's upstream host is or anything
like that. We can deal with that later. A Tier-1 would need to have
a Tier-0 as its upstream host but Tier-2's could also have a Tier-0 as
the upstream host. At that level the Tier designation is based more
on amount of content. I can try to come up with a better definition
of "everything" if this one isn't good enough.
If this sounds reasonable I'd suggest we stop calling them Tier-* and
come up with different designations. Maybe something like:
Tier-0 -> "Distribution Site"
Tier-1 -> "Primary Mirror Site"
Tier-2 -> "Secondary Mirror Site"
Meta comments... I've noticed the bittorrent stuff come up in several
threads, when I get some time I'll begin looking into that. My first
impressions of it are that it's probably of use for ISO distribution
but probably not for FTP-based installation mechanisms, but I don't
know its basic workings yet. I am also working on generating a list
of the current sites registered as Official Mirrors and will use that
to generate the announce-only mandatory private email list. So far
nobody has said that's a bad idea.
--
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?20030716155448.GA11005>