Rawhide 20080328 Snapshot Released
jkeating at redhat.com
Sat Mar 29 15:53:28 UTC 2008
On Sat, 2008-03-29 at 22:59 +0900, John Summerfield wrote:
> Is it difficult to release jigdos?
The problem is this.
Jigdo would require the exploaded bits be available by http. Trying to
sync all that content around the mirrors in any sort of reasonable time
frame is not going to happen. Hanging the entire tree off of a single
http point is not going to happen either, that point would quickly drown
under the connections. We can't just rely on rawhide as tomorrow the
rawhide content will be different and you wouldn't be able to complete
If we're to have any sort of fast to the public snapshoting, we have to
use a delivery mechanism that is capable of spreading the bandwidth load
throughout the users without bringing down the host. Right now, that
only leaves us with bittorrent as an option.
Now, if there were some way to combine bittorrent and jigdo and if jigdo
had better failover methods when mirrors are hit without the content we
could potentially do something better. Jigdo + rawhide + whatever you
already have for the majority of the content, bittorrent to suck down
the very last little bit or something along those lines.
Fedora -- All my bits are free, are yours?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/test/attachments/20080329/352a9712/attachment.bin
More information about the test