1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
|
<br><br><div class="gmail_quote">On Sun, Sep 19, 2010 at 10:54 AM, Olivier Thauvin <span dir="ltr"><<a href="mailto:nanardon@nanardon.zarb.org">nanardon@nanardon.zarb.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi all,<br>
<br>
As soon we'll have a kind of infrastructure and making the distribution<br>
will start we'll need a way to distribute it.<br>
So to be ready as soon as possible I start here a discuss about the<br>
mirror management and will make some suggestion.<br>
<br>
Nothing is done at time, so feel free to comment.<br>
<br>
1) The mirror content:<br>
- distribution<br>
- devel one<br>
- stable one<br>
<br>
is there enything else (patch, our own applications as source,<br>
documentation as flat html file) ?<br>
<br>
We also have to define the rules making a mirror valid and avoid<br>
differences between them.<br>
<br>
2) The logical mirroring process<br>
<br>
The proposal is to have a safe and access limited rsync server<br>
containing the tree (<a href="http://rsync.mageia.org" target="_blank">rsync.mageia.org</a> ?). Mirroring from this one can<br>
only be done after being authorized by our team.<br>
<br>
At second level, rsync'd from this safe server some referenced servers<br>
open to the world for all other mirrors (distrib-coffee could be one of<br>
them). The manager of these servers must be reachable, then we need to<br>
know them.<br>
<br>
So at the end all others mirrors from where everyone can fetch the<br>
distribution, and anyone could freely setup a such mirror.<br>
<br>
3) Listing mirrors<br>
<br>
I do think registering mirrors could be done by anyone, once the mirror<br>
is availlable.<br>
<br>
So i suggest to have a web application to allow mirror registration.<br>
After submission a post process could verify the URL validity and if<br>
everything is ok the new mirror would appear in official list.<br>
<br>
The main point of this idea is to not force mirrors admin to registering<br>
on any bug tracker or anything else.<br>
<br>
The second goal of such application is of course to monitor them and<br>
alert when they are down or out of sync.<br>
<br>
<br>
Feel free to comment. I'll be carrefully reading this thread !<br>
<br>
Regards.<br>
<font color="#888888"><br>
--<br>
<br>
Olivier Thauvin<br>
CNRS - LATMOS<br>
♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖<br>
</font><br>_______________________________________________<br>
Mageia-discuss mailing list<br>
<a href="mailto:Mageia-discuss@mageia.org">Mageia-discuss@mageia.org</a><br>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss" target="_blank">https://www.mageia.org/mailman/listinfo/mageia-discuss</a><br>
<br></blockquote></div><br><br>Idk if this is of any interest to you guys, but at Unity Linux we have a devel server central to everything that syncs with ibiblio thru a series of scripts. Then we have ~20 other sites that rsync with ibiblio on a regular basis. Ibiblio is a great mirror to use b/c by default there are already several other sites mirroring it.<br>
<br>Then we have a mirror monitoring system that reports the status of the mirrors.<br><a href="http://unity-linux.org/mm/mirrorstatus.html">http://unity-linux.org/mm/mirrorstatus.html</a><br><br>
|
