Closed Bug 659008 Opened 13 years ago Closed 13 years ago

scl1-production-puppet-new: new centos 5 KVM in scl1

Categories

(Infrastructure & Operations :: RelOps: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: arich)

References

Details

To migrate scl-production-puppet (bug 659005), we'll need a new KVM instance in scl1.  The current system has

 1 CPU
 4 GB RAM (most of which seems to be cache)
 15 GB / (7.4 used)
 213GB /builds (9.0 used)

Based on http://ganglia1.build.scl1.mozilla.com/ganglia/graph.php?g=mem_report&z=large&c=RelEngSCL1&h=scl-production-puppet.build.scl1.mozilla.com&m=load_one&r=hour&s=descending&hc=4&mc=2&st=1306166623 I think we can make do with

 1 CPU
 1 GB RAM
 40GB /

Let's name the new host scl-production-puppet-new; we can swap the DNS record when we're ready to cut over to the new system.
Summary: new centos 5 KVM in scl1 → scl1-production-puppet-new: new centos 5 KVM in scl1
Just because it's less disruptive to decrease than increase after the fact, I've built it with 2G of RAM (which also means 2G of swap) for those times when a bunch of machines reboot at once and slam it.  Please open a new ticket when you're ready to cut over and change the hostname/IP.
Assignee: server-ops-releng → arich
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.