1 |
In order to get a better handle on space utilization for our mirrors, I'm |
2 |
going to put in a mostly-firm-but-somewhat-flexible cap on overall space |
3 |
used for each release. Taking a look at the amount of space used for each |
4 |
arch in 2004.1, we have: |
5 |
|
6 |
2.9G ./ppc/2004.1 |
7 |
4.5G ./x86/2004.1 |
8 |
1.3G ./amd64/2004.1 |
9 |
2.4G ./sparc/2004.1 |
10 |
|
11 |
If you go on the recently-heard "we're only releasing x86 and 686" for x86, |
12 |
then the space there works out to ~2.2GB. |
13 |
|
14 |
There are other projects (like hardened) that want to get their stuff on |
15 |
the mirror as well, and I expect we're going to have at least one or two |
16 |
new arches releasing this time around that missed the 2004.1 deadline. As |
17 |
such, I'm proposing a 2.5GB per arch/major-top-level project cap on file |
18 |
size for the mirror. |
19 |
|
20 |
Now, lest anyone get up in arms at this, I only care about the total size |
21 |
of all the files used for a release. So, when it comes time to put 2004.2 |
22 |
stuff up on the mirror, I'm going to look at the number of arches + major |
23 |
top level projects (currently, only hardened) and multiple that by 2.5 to |
24 |
get a total size cap. As long as the total size is under that number, |
25 |
that's fine with me. |
26 |
|
27 |
Some notes: |
28 |
|
29 |
* If an arch isn't releasing for 2004.2, then no space is allocated for |
30 |
them. |
31 |
* If an arch is planning on releasing for 2004.2 and cancels at the last |
32 |
minute, then no space is allocated for them. |
33 |
* I would greatly appreciate a heads up at least 2-3 weeks prior to a |
34 |
release about arches that *will* be releasing for 2004.2. So far, I'm |
35 |
assuming x86, ppc, amd64 and sparc will all be releasing from an arch POV |
36 |
and I also assume hardened will release something as well. So, that's a |
37 |
total of 12.5GB of data that I'm expecting. If more arches will be |
38 |
releasing, please let me know as soon as possible so I can give a heads |
39 |
up to our mirrors. |
40 |
* sub-projects, such as GameCDs, will need to fit into the existing space |
41 |
requirements. Arches like AMD64 are unlikely to need a full 2.5GB of |
42 |
space, so this should allow some extra space for GameCDs and other |
43 |
special projects. If there are other unique circumstances that may |
44 |
warrant special consideration, please feel free to discuss with me on |
45 |
IRC. |
46 |
|
47 |
So, at this point, you have 12.5GB of available space to fill up with |
48 |
whatever you want. I don't care if it's 12.5GB devoted to one arch and |
49 |
everyone else is left out in the cold -- that's up to you guys to figure |
50 |
out. I just need a firm number that I can communicate to our mirror |
51 |
admins so they can plan accordingly. (again, if more arches are releasing, |
52 |
please let me know ASAP) |
53 |
|
54 |
--kurt |
55 |
|
56 |
P.S. We will also have a torrent server available for distributing ISOs and |
57 |
stages that might not make it into the above size cap. At this point, we |
58 |
have no alternate means of distributing this data (such as http or ftp) so |
59 |
please plan what goes in the 12.5GB carefully. |