Closed Bug 1016521 Opened 11 years ago Closed 11 years ago

Clone glow1.dmz.phx1 to SCL3

Categories

(Infrastructure & Operations :: Virtualization, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gozer, Assigned: cknowles)

References

Details

The glow project is currently running on a single VM in PHX1, and for redundancy, and because we are spinning up bouncer in SCL3, I'd like to have an identical VM in SCL3. The glow folks can take care of setup, it just needs to be a VM with similar specs.
glow in phx1 was made in bug 985564, then oversized to handle the initial launch day in bug 1001457, which we're supposed to take back at some point. OK to make this new guy with the old stats?
(In reply to Greg Cox [:gcox] (plz don't needinfo me) from comment #1) > glow in phx1 was made in bug 985564, then oversized to handle the initial > launch day in bug 1001457, which we're supposed to take back at some point. > OK to make this new guy with the old stats? Yes, that should be fine at the old stats.
Alright, we'll get on that shortly. CJK
Assignee: server-ops-virtualization → cknowles
glow1.dmz.scl3.mozilla.com exists, it's got the old stats of 2CPU, 8GRAM. It's had initial puppet and nagios stubs done, so it's ready for your loving customization. If you have concerns with the initial setup, let me know. CJK
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.