From evanwebb at gmail.com Mon Oct 17 17:57:07 2005 From: evanwebb at gmail.com (Evan Webb) Date: Mon, 17 Oct 2005 14:57:07 -0700 Subject: [Support-mirrors] GEM mirroring Message-ID: <92f5f81d0510171457x54ffa858l7f18407cad7d32dd@mail.gmail.com> I've brought it up before, but recent discussions are making me ask again: Any thoughts about gem mirroring? I mentioned it to Chad, he seemed to think it would be fairly easy. I'm happy to code it up, but I'd like to discuss the logistics first. Here's my thoughts. * GEMS are mirrored Out of band of the the actual gem download process, probably using the existing rsync setup the rest of rubyforge mirroring is using. * The mirror gem server then just serves up random 3xx HTTP Redirects to the other gem servers (which would include a normal gem server running on another port of the rubyforge gem server) Since rubygems use Net::HTTP, the HTTP Redirect should work without having to change any clients (this would of course have to be tested). Hows this sound? - Evan Webb -- When I do good, I feel good; when I do bad, I feel bad, and that is my religion. -- Abraham Lincoln (1809 - 1865) From robby.lists at planetargon.com Mon Oct 17 18:18:28 2005 From: robby.lists at planetargon.com (Robby Russell) Date: Mon, 17 Oct 2005 15:18:28 -0700 Subject: [Support-mirrors] GEM mirroring In-Reply-To: <92f5f81d0510171457x54ffa858l7f18407cad7d32dd@mail.gmail.com> References: <92f5f81d0510171457x54ffa858l7f18407cad7d32dd@mail.gmail.com> Message-ID: <1129587509.6730.232.camel@linus> On Mon, 2005-10-17 at 14:57 -0700, Evan Webb wrote: > I've brought it up before, but recent discussions are making me ask > again: Any thoughts about gem mirroring? I mentioned it to Chad, he > seemed to think it would be fairly easy. I'm happy to code it up, but > I'd like to discuss the logistics first. > > Here's my thoughts. > * GEMS are mirrored Out of band of the the actual gem download > process, probably using the existing rsync setup the rest of rubyforge > mirroring is using. > * The mirror gem server then just serves up random 3xx HTTP Redirects > to the other gem servers (which would include a normal gem server > running on another port of the rubyforge gem server) > > Since rubygems use Net::HTTP, the HTTP Redirect should work without > having to change any clients (this would of course have to be tested). > > Hows this sound? > > - Evan Webb What happens if the main RubyForge gem site isn't responding for some reason? Have you considered some sort of round-robin DNS trickery? -- /****************************************************** * Robby Russell, Owner.Developer.Geek * PLANET ARGON, Open Source Solutions & Web Hosting * Portland, Oregon | p: 503.351.4730 | f: 815.642.4068 * www.planetargon.com | www.robbyonrails.com * Programming Rails | www.programmingrails.com *******************************************************/ From evanwebb at gmail.com Mon Oct 17 18:25:24 2005 From: evanwebb at gmail.com (Evan Webb) Date: Mon, 17 Oct 2005 15:25:24 -0700 Subject: [Support-mirrors] GEM mirroring In-Reply-To: <1129587509.6730.232.camel@linus> References: <92f5f81d0510171457x54ffa858l7f18407cad7d32dd@mail.gmail.com> <1129587509.6730.232.camel@linus> Message-ID: <92f5f81d0510171525y6fc53fc7lfc1d3f0c4ff7ffb2@mail.gmail.com> Sure, we could setup RRDNS on gems.rubyforge.org as well. I'd prefer not use RRDNS as the actual mechanism to direct to people to a different servers (instead of http redirects) because RRDNS has lots of caching problems. Best would be to setup a few masters that know all the others and just the masters are in RRDNS, they then still server http redirects to other servers. - Evan On 10/17/05, Robby Russell wrote: > On Mon, 2005-10-17 at 14:57 -0700, Evan Webb wrote: > > I've brought it up before, but recent discussions are making me ask > > again: Any thoughts about gem mirroring? I mentioned it to Chad, he > > seemed to think it would be fairly easy. I'm happy to code it up, but > > I'd like to discuss the logistics first. > > > > Here's my thoughts. > > * GEMS are mirrored Out of band of the the actual gem download > > process, probably using the existing rsync setup the rest of rubyforge > > mirroring is using. > > * The mirror gem server then just serves up random 3xx HTTP Redirects > > to the other gem servers (which would include a normal gem server > > running on another port of the rubyforge gem server) > > > > Since rubygems use Net::HTTP, the HTTP Redirect should work without > > having to change any clients (this would of course have to be tested). > > > > Hows this sound? > > > > - Evan Webb > > What happens if the main RubyForge gem site isn't responding for some > reason? Have you considered some sort of round-robin DNS trickery? > > > -- > /****************************************************** > * Robby Russell, Owner.Developer.Geek > * PLANET ARGON, Open Source Solutions & Web Hosting > * Portland, Oregon | p: 503.351.4730 | f: 815.642.4068 > * www.planetargon.com | www.robbyonrails.com > * Programming Rails | www.programmingrails.com > *******************************************************/ > > -- When I do good, I feel good; when I do bad, I feel bad, and that is my religion. -- Abraham Lincoln (1809 - 1865) From halostatue at gmail.com Mon Oct 17 21:27:12 2005 From: halostatue at gmail.com (Austin Ziegler) Date: Mon, 17 Oct 2005 21:27:12 -0400 Subject: [Support-mirrors] GEM mirroring In-Reply-To: <92f5f81d0510171457x54ffa858l7f18407cad7d32dd@mail.gmail.com> References: <92f5f81d0510171457x54ffa858l7f18407cad7d32dd@mail.gmail.com> Message-ID: <9e7db9110510171827l6dbf970fye1db9cb16ba39589@mail.gmail.com> On 10/17/05, Evan Webb wrote: > I've brought it up before, but recent discussions are making me ask > again: Any thoughts about gem mirroring? I mentioned it to Chad, he > seemed to think it would be fairly easy. I'm happy to code it up, but > I'd like to discuss the logistics first. Gems implicitly supports this. I am asking the Gems team what can be done to alleviate the 768kbps pipe for RubyForge itself. -austin -- Austin Ziegler * halostatue at gmail.com * Alternate: austin at halostatue.ca