This is to track getting a new ESX server for the community build network. The current ESX machine (cb-vmware01.mozilla.org) is out of disk and showing about 70-95+% memory and CPU utilization. The new machine should basically match the specs of the current cb-vmware01 machine, but if we can get more disk or memory or whatever for the same cost, that would be great.

John, is this something that's still needed? cb-vmware01 isn't out of disk space at all (> 300GB free space) . CPU is between 70-95% but I'm not convinced that any of the VMs are having issues with that at the moment. Originally preed needed disk space to update VMs to the new ref images and though it was out of space. It wasn't and he finished that task. If there isn't a need at the moment (more community build VMs?), I'd rather save this machine.

(In reply to comment #1) > If there isn't a need at the moment (more community build VMs?), I'd rather > save this machine. There is no immediate need from my perspective, unless a project leader (chime in now) envisages needing an extra VM in the near future. It's not imminent, but we will likely be pushing Thunderbird builds out onto the community network eventually, and it will be good to be ahead of that when it happens.

Unless I hear otherwise, I'll WONTFIX this. What happens to TB builds is largely undetermined and could/should be on it's own hardware instead of shared community build hardware. But that can be addressed separately.

When we might branch 1.9 or we want to start supporting mozilla2 for the community project, we might want/need additional tinderboxen to do that. Bug 392438 will only temporarily need more space, that should be easy to handle with current resources. I'm not sure though how many locales the current solution for bug 391656 can handle without making cycle times of the main SeaMonkey boxen much worse (esp. for the Windows one), mainly due to checkout.