Tuesday, March 09, 2010

Hardware Upgrades Part 3: Solving problems 2, 3 and 5

See Part 1: The Problems

See Part 2: Solving Problems 1 and 4

This is part 3 of 3 of the series, which describes how we'll deploy all the hardware donations we've received.

Problem 3 is the AMD servers that were donated at EclipseCon 2008.  Great hardware all around, but we're running the Xen virtualization engine on top of it, and something obscure is preventing these machines from reaching their full potential.  I could spend days, weeks and months trying to figure it out, but since they perform flawlessly when run on the bare iron, the solution here is to replace our AMD Virtual Servers (powering www.eclipse.org, Bugzilla, the Wiki, and others) with some new Intel hardware.

Problem 2 is the aging Itanium2 cluster that we know as dev.eclipse.org and download.eclipse.org.  The AMD servers will be boosted with RAM and re-deployed here, as dev.eclipse.org and download.eclipse.org.  With dual quad-core processors and gobs of RAM, we'll try to stay in RAM for your file access as much as possible.

Some Intel servers, boosted with RAM courtesy of Google, will be deployed here to help power git.eclipse.org.

Problem 5 is the lone Build server.  IBM has just donated 2 awesome x3550 servers to help solve this problem, and we can re-deploy some Itanium hardware here too.

Since we'll have some leftover Itanium hardware, it will likely be re-deployed as backend server where appropriate, to take some load off NFS.

How's that for a plan?


Post a Comment

<< Home