diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101021/001314.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101021/001314.html | 204 |
1 files changed, 204 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101021/001314.html b/zarb-ml/mageia-dev/20101021/001314.html new file mode 100644 index 000000000..9da3e4032 --- /dev/null +++ b/zarb-ml/mageia-dev/20101021/001314.html @@ -0,0 +1,204 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Mirror tree structure + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20tree%20structure&In-Reply-To=%3C201010211716.06866.bgmilne%40multilinks.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001311.html"> + <LINK REL="Next" HREF="001309.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror tree structure</H1> + <B>Buchan Milne</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20tree%20structure&In-Reply-To=%3C201010211716.06866.bgmilne%40multilinks.com%3E" + TITLE="[Mageia-dev] Mirror tree structure">bgmilne at multilinks.com + </A><BR> + <I>Thu Oct 21 18:16:06 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001311.html">[Mageia-dev] Mirror tree structure +</A></li> + <LI>Next message: <A HREF="001309.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1314">[ date ]</a> + <a href="thread.html#1314">[ thread ]</a> + <a href="subject.html#1314">[ subject ]</a> + <a href="author.html#1314">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thursday, 21 October 2010 06:37:37 Olivier Thauvin wrote: +><i> * J.A. Magallón (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">jamagallon at ono.com</A>) wrote: +</I>><i> > On Wed, 20 Oct 2010 18:34:24 +0200, Olivier Thauvin +</I><<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">nanardon at nanardon.zarb.org</A>> wrote: +><i> > > Hi, +</I>><i> > +</I>><i> > ... +</I>><i> > +</I>><i> > > Now come the question: "what is a valid mirror ?", eg, what a mirror +</I>><i> > > should have as file to be valid ? +</I>><i> > +</I>><i> > Some ideas (probably silly ;)). +</I>><i> > +</I>><i> > Why don't you split mirrors in 2 categories: +</I>><i> > - Software (RPM) repo mirrors, available for network install or urpmi. +</I>><i> > +</I>><i> > (distrib+people+software). +</I>><i> > +</I>><i> > - ISO mirrors. Avaliable for torrenting or ftp. MDV2010.1 release isos +</I>><i> > are +</I>><i> > +</I>><i> > about 15Gb. With 2 releases per year, thats 30Gb per year, 200 Gb on 6 +</I>><i> > years. Some places can just mirror this...you lower the 700Gb to 500, +</I>><i> > not bad. +</I>><i> > +</I>><i> > so mirroring can be done by version (or was this what you wanted to +</I>><i> > avoid?). +</I>><i> +</I>><i> Yes, I tried to avoid it because I perfectly know mirrors will take care +</I>><i> to mirror new version every 6 months (ibiblio example again, nobody had +</I>><i> a look for several years, at least since 2008). +</I> +This will result in fewer mirrors (those that cannot or choose not to dedicate +~ 1TiB). I would rather consider other solutions to this problem. On my own +mirror (which has a total of 820GB available at present), I use exclude +options to rsync in my mirror scripts (but, I have to change these after each +release). + +Maybe instead we could provide exclude-list files on the mirror, so mirror +maintainers can use --exclude-from=/path/to/mageia/mirror_cfg/old_releases.cfg + +Also, in order to try and expedite getting what most users need out to mirrors +first, I would prefer either: +-development tree separate from releases +-development release should be selected last by mirroring tools (e.g. follow +alphabetically all stable releases if not separate) + + +><i> +</I>><i> > BTW +</I>><i> > <nitpickin> +</I>><i> > - could you kill the final 's' on all the names ? +</I>><i> > +</I>><i> > distribs -> distrib +</I>><i> +</I>><i> Done +</I> +Maybe 'releases' or 'release' instead? + +><i> +</I>><i> > iso (you didnt named it 'isos') +</I>><i> > peoples -> people +</I>><i> +</I>><i> Done +</I>><i> +</I>><i> > software (not softwares) +</I>><i> +</I>><i> Is already 'software' +</I>><i> +</I>><i> > - could you not mix case in names (SRPMS <-> x86_64), just srpms... +</I>><i> +</I>><i> This part depend on BS and how this team working on it will organise the +</I>><i> distrib. I'll suggest them. +</I>><i> +</I>><i> > - could be the arch names more uniform ? in my personal scripts/setups +</I>><i> > +</I>><i> > I use x86-32 and x86-64. +</I> +Is x86-32 a valid architecture for rpm etc.? While uniformity might be nice, +unfortunately vendors don't necessarily choose uniform architecure names, and +it might be better to match the repo structure to values that can be +determined directly (and not heuristcally) . + +I've also never seen 'uname -m' report x86-32 or x86_32. + +><i> > Moreover, perhaps in a not so near future some +</I>><i> > adventurous soul builds Mageia on ARM or Sparc, so why not sort things +</I>><i> > like +</I>><i> > +</I>><i> > distrib/cauldron/srpm +</I>><i> > distrib/cauldron/x86/32/iso +</I>><i> > +</I>><i> > /rpm +</I>><i> > +</I>><i> > /64 +</I>><i> > +</I>><i> > /arm/32 +</I>><i> > +</I>><i> > /64 +</I> +I don't know if memory address space is a useful differentiator here, as +features differ substantially in different ARM cores of the same family or +architecture version. E.g., Fedora has an 'armv5tel' architecture, N900 ships +.deb's with 'armel' as the architecture. See +<A HREF="http://en.wikipedia.org/wiki/ARM_architecture">http://en.wikipedia.org/wiki/ARM_architecture</A> + +><i> > +</I>><i> > /sparc/32 +</I>><i> > +</I>><i> > /64 +</I> +AFAIK, the valid architecture names for sparc are sparc,sparc64,sparcv9. + +><i> +</I>><i> This depend again on BS part. +</I>><i> +</I>><i> > The drawback is that ISOs are in the same tree so no separate mirroring +</I>><i> > is possible, but I think you didn't want this anyways. +</I>><i> +</I>><i> I'll take care to this. +</I>><i> +</I>><i> > All this renaming in case it is not some kind of standard for tree layout +</I>><i> > or the like... +</I>><i> > </nitpickin> +</I>><i> > +</I>><i> > Just my 2€cent, you will judge... +</I> +The readme file mentions that mirrors must sync every 2 hours. For tier1 +mirrors, I would agree, however you may need to stagger sync intervals to +lower tiers (e.g. 4 hours at tier2 and 12 hours at tier3). + +It may be worthwhile to try and estimate the actual rsync bandwidth that must +be achieved to make a specific tier. + +(I am not able to sync every 2 hours, probably not 4, maybe 12, though my +mirror currently syncs daily - for Mandriva I could sync 'official' more +regularly, but not 'devel'). + + +Regards, +Buchan +</PRE> + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001311.html">[Mageia-dev] Mirror tree structure +</A></li> + <LI>Next message: <A HREF="001309.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1314">[ date ]</a> + <a href="thread.html#1314">[ thread ]</a> + <a href="subject.html#1314">[ subject ]</a> + <a href="author.html#1314">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |