Closed
Bug 524843
Opened 15 years ago
Closed 15 years ago
Replace staging-talos minis in colo with production talos rev2 machines
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lsblakk, Assigned: phong)
References
Details
Please take the following 10 machines out of the colo and bring them to 650 Castro for putting in the server room here:
qm-pleopard-stage01
qm-plinux-stage01
qm-ptiger-stage01
qm-pvista-stage01
qm-pxp-stage01
talos-rev1-leopard01
talos-rev1-linux03
talos-rev1-linux04
talos-rev1-vista01
talos-rev1-xp01
talos-rev2-x6401
In their spots, replace with 11 new minis from bug 524842:
qm-pvista-try10
qm-pvista-try11
qm-pubuntu-try10
qm-pubuntu-try11
qm-pleopard-try08
qm-pleopard-try09
qm-pleopard-try10
qm-pleopard-try11
qm-pxp-try08
qm-pxp-try09
qm-pxp-try10
Reporter | ||
Comment 1•15 years ago
|
||
The staging environment is in high use and so if it's possible to do this move on a Friday and have the following Monday to get it set up again that would be great. The same request has been made in the dependent bug on moving the talos-staging-master VM.
Assignee | ||
Updated•15 years ago
|
Assignee: server-ops → phong
Flags: colo-trip+
Reporter | ||
Comment 2•15 years ago
|
||
When these machines are moved, can we please change the names of a few of them as follows:
qm-pleopard-stage01 --> talos-rev1-leopard02
qm-plinux-stage01 --> talos-rev1-linux05
qm-ptiger-stage01 --> talos-rev1-tiger01
qm-pvista-stage01 --> talos-rev1-vista02
qm-pxp-stage01 --> talos-rev1-xp02
Comment 3•15 years ago
|
||
phong, can you provide an ETA? What resources do you need to get this done by Friday?
Severity: normal → critical
Assignee | ||
Comment 4•15 years ago
|
||
I just need the switch and a location for these and I'll have them up by the end of the day.
Comment 5•15 years ago
|
||
Either QA lab and the switch on derek's desk or the server room in suite 280.
Assignee | ||
Comment 6•15 years ago
|
||
It's in the QA lab handed over to lsblakk.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•