The agreed plan for this host is to create one or more new VMs in scl3, and transfer its responsibilities there. We can build out nice new centos6 VMs, and be free of the cruft currently running on cruncher. Bug 739728 is about auditing what's on cruncher now, but while that's going on we can start migrating the stuff we already know is on cruncher. Please describe what the new VMs should look like -- the usual RAM, disk, CPU questions -- and assign to me, and I'll get them running and hand back.

Oh, and we would like to have this VM evacuated from sjc1 by the 4/23 train (not the 4/9 train as I initially thought in the meeting - sorry about that)

ping?

let's give assigning this to bear a shot :)

The VM should match what we currently have.

Hoorj! So, that's: Hostname: cruncher.srv.releng.scl3.mozilla.com Disk: 75G (local) RAM: 8G CPU: 1 OS: CentOS 6.2 <** Aj was setting up a template for this? This is a shared sandbox VM, hence the relatively beefy stats. Critical since we're hoping to evacuate this host from sjc1 in time for this weekend.

dustin - confirming that the disk for cruncher will be copied as is to the new VM?

Bear - no, but we can rsync what we need. This is down to "major" since this host doesn't need to move by Monday - it's on a bm-vmware* host that will need to move soon, though.

ok, that may require a small downtime window given that buildapi is involved. I need to find that out and will check back either way.

Aj, ready to roll on this?

Any ETA on this VM?

building out this template now.

cruncher.srv.releng.scl3.mozilla.com has address 10.26.48.43 https://inventory.mozilla.org/en-US/systems/show/6029/ [mburns@boris ~]$ ssh cruncher.srv.releng.scl3.mozilla.com [mburns@cruncher ~]$