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.
John
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?
Yes.
Is this really a viable way to put out *weekly* snapshots?
Nope. I canceled my download. My guess is that we need to do beta 1 beta 2 etc in quick successions instead of this to get enough number of downloads going and subsequent feedback hopefully.
Rahul
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?
Not happening here, I'm adding another seed to the swarm - I see it's already uploading more then it's downloading, while it is still downloading.
Is this really a viable way to put out *weekly* snapshots?
No. ;-)
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.
The snapshots (torrent ISO images) should have an updates.img which should make them installable.
Jigdo is a possibility in distributing the snapshots, but the downside is that at least one party, and preferably more then one, will need to keep hosting the slices; while on day 0 all slices are (or should be) in rawhide, on day 1 some packages might have been updated again and are thus not available anymore -unless some party keeps hosting the entire tree such as Fedora Unity does with their Re-Spins; 4 mirrors keep hosting all slices that come from the updates/ repository for as long as the Re-Spin is offered for downloading.
Kind regards,
Jeroen van Meeuwen -kanarip
On Sat, 29 Mar 2008, 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.
Looks like this is actually releng's call as they decided to host jigdo for the last beta. I'm not sure if we ever got it actually working right though.
-Mike
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.
infrastructure@lists.fedoraproject.org
-
Jeroen van Meeuwen -
Jesse Keating -
John Poelstra -
Mike McGrath -
Rahul Sundaram