On Tue, Jun 02, 2009 at 09:30:17PM +0200, Thorsten Leemhuis wrote: > On 02.06.2009 00:22, Matt Domsch wrote: > > On Mon, Jun 01, 2009 at 04:03:04PM -0400, Paul W. Frields wrote: > >> I'm getting out of my ken here, but could this be done in stages with > >> I2 connected hosts getting the bits early/first and then moving on to > >> others? > > We need to move ~130GB to each of ~230 mirrors, in about 4 > > days. The 130GB is what we posted for F10. Of that, 48GB were ISOs, 93GB was the Everything/ tree which was hardlinked from rawhide, so yes, that would cut down on the transfer quite a bit. Honestly, I don't recall how the signing aspect went for F10. If the process involved signing, then copying the packages into the Everything tree, then there wouldn't be hardlinks to help. > I'd like to question these numbers. All the SRPMS (18 GByte) and RPMS > (20 GByte per arch) of a new release are in the rawhide trees already -- > thus if they are hardlinked properly then they can be transferred in a > minute or two. The install CD and DVD images (~ 8 GByte each per arch?) > are bigger, but if we get RC with the final name transferred to the > mirrors ahead of time then they can be updated relative quickly as well, > as only a few bit change. RCs with the final name haven't been posted for the mirrors ahead of time, yet. We could consider it for F12 though. > The spins that get compressed are a problem. But we only send Desktop > and KDE spins to the mirrors for x86-32 and x86-64 afaics -- so roughly > 3 GByte in total. Right. > So 3 GByte + some other random stuff that changed -- install.img, > boot.iso, and some other things. Not sure how much that will sum up to, > but can't sum up to that much -- maybe 3 or 5 more GByte. > > Let's say it are 10 GBtyte. It afaics shouldn't take more then a day if > all mirrors look out for new stuff at least every 4 hours and have a > link that isn't slow by todays standards. > > Or what am I missing? I think you're right, except that RC ISOs aren't published ahead of time for mirrors to sync, and signing of the RPMs that land in the Everything tree if they weren't signed, or were signed with a different key. I believe the signing process has changed for F11, so the packages in rawhide are signed with the F11 release key. I think that means at some point, either through a mass rebuild, or through a resigning, rawhide will then need to be re-signed with the F12 key. -- Matt Domsch Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
