On Sat, 2008-03-29 at 21:30 -0700, John Poelstra wrote: > I'm finding trying to get Friday's snapshot of Fedora 9 to be very > sub-optimal... 62 hours estimated to go after already timing out once. > I've got two peers and one seed :( I'll probably get it by time the > next snapshot is ready :) > > Is this happening to others? > > Is this really a viable way to put out *weekly* snapshots? > > Is hosting jigdo templates a possibility? In my situation it would work > well because I mirror the rawhide trees locally--yes I realize this begs > the question of why I need the snapshot if I already mirror rawhide, but > I'm curious if it fails to install for me just as rawhide has for the > past three days. As I mentioned in other threads, jigdo requires that the slices be available via http somewhere. The amount if time we have to spin a snapshot and get it somewhere public for it to have any sort of relevance is pretty darn short, and trying to instasync a number of mirrors hasn't gone too well in the past, and those mirrors would just quickly become overloaded and not able to handle jigdo requests anyway. (there are those that would just http mirror things instead of using jigdo). So for the most reasonable turnaround time, we use torrent. We can upload isos in a matter of hours and start the torrent system. Theoretically I can seed as well as I just did the compose, and we might be able to seed a few other places that have fast access to the snapshot. We'll keep thinking of better ways to deliver the snapshots, it's just quite difficult to do something with fast turnaround /and/ have a way to spread the delivery load. -- Jesse Keating Fedora -- All my bits are free, are yours?
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
