The new server is up and has all the software installed on it, so now we need to come up with a plan for moving the systems to the new setup. It will /almost/ be possible to do it cleanly with DNS without anyone noticing--just bring apache up on the new server, whose scripts will read and write the database on the old server, and switch "www" to point to it. During the time when user's DNS caches are still live, some will point to the old server, but it will be sharing the same database, so both systems can run concurrently with no problem. The glitch: images. Those are written to the filesystem rather than to the database, so images uploaded on one server will appear in the database of both, but only on one filesystem. One way to fix this is to NFS-mount the image filesystem on both machines, but NFS is not terribly reliable and will increase network traffic. Another way to do it is a more traditional switchover that will turn off the scripts on the old server when we enable to new one, and put up a static page that points people to the new server under a name other than "www" while their caches are still live. Another thing to consider is moving "test" over first, pointing to the old database, and try the transition method on that before we try it on "www". Jason, regardless of which way we go, you can start by reducing the lifetime of "test" and "www" in DNS, and make entries for "pliny" and "larousse". We also need to change the canonical name of ww to pliny--I can do that, but I'm not sure what else that might effect, so I haven't done it yet. -- Lee Daniel Crocker &lt;lee(a)piclab.com&gt; <http://www.piclab.com/lee/> "All inventions or works of authorship original to me, herein and past, are placed irrevocably in the public domain, and may be used or modified for any purpose, without permission, attribution, or notification."--LDC _______________________________________________ Wikitech-l mailing list Wikitech-l(a)wikipedia.org http://www.wikipedia.org/mailman/listinfo/wikitech-l

(Jimmy Wales &lt;jwales(a)bomis.com&gt;)m>): Lee Daniel Crocker wrote: Isn't this true: for all images already uploaded, there is no problem. Only when a new image is uploaded, it will go to one or the other filesystem? I think this could be tolerable if we disable image uploading on the "old" server (now the "database server"), just to make sure nothing gets uploaded there.

I am only in control of wikipedia.com, I don't know who can change the TTL on wikipedi.org subdomains. Jason Lee Daniel Crocker wrote: -- "Jason C. Richey" &lt;jasonr(a)bomis.com&gt; _______________________________________________ Wikitech-l mailing list Wikitech-l(a)wikipedia.org http://www.wikipedia.org/mailman/listinfo/wikitech-l

Yeah, I noticed that right after I sent this mail... For some reason, I thought that wikipedia.org was a different situation (in terms of DNS) than wikipedia.com. I don't know what made me think that. Jason Jimmy Wales wrote: > How's that? I'm sorry, I don't understand. It's all in my register.com > account, right? > > Jason Richey wrote: > > > I am only in control of wikipedia.com, I don't know who can change the > > TTL on wikipedi.org subdomains. > > > > Jason > > > > Lee Daniel Crocker wrote: > > > > > > > > Jason, regardless of which way we go, you can start by reducing > > > the lifetime of "test" and "www" in DNS, and make entries for > > > "pliny" and "larousse". We also need to change the canonical > > > name of ww to pliny--I can do that, but I'm not sure what else > > > that might effect, so I haven't done it yet. > > > > > > -- > > > Lee Daniel Crocker &lt;lee(a)piclab.com&gt; <http://www.piclab.com/lee/> > > > "All inventions or works of authorship original to me, herein and

> > > are placed irrevocably in the public domain, and may be used or

> > > for any purpose, without permission, attribution, or

-- "Jason C. Richey" &lt;jasonr(a)bomis.com&gt; _______________________________________________ Wikitech-l mailing list Wikitech-l(a)wikipedia.org http://www.wikipedia.org/mailman/listinfo/wikitech-l

I belive that it would be a worthwhile investment for wikipedia to invest in an easyDNS account. i believe its important for the project to have full control over their dns at all times.... and its not expensive at all. i use it and i absolutely love it.. and if a couple of people want to, im willing to chip in for it.