Closed
Bug 757985
Opened 13 years ago
Closed 13 years ago
bigtent: build production VMs
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: petef, Assigned: ckolos)
References
Details
(Whiteboard: [qa+])
VMs: 3x in scl2, 3x in phx1
see bug 757984 for whatever specs we end up deciding on.
| Reporter | ||
Updated•13 years ago
|
Group: services-infra
Updated•13 years ago
|
Whiteboard: [qa+]
| Reporter | ||
Comment 1•13 years ago
|
||
Actually, we're going to end up with 9 VMs per dc:
bigtent-microsoft{1,2,3}.idweb
bigtent-google{1,2,3}.idweb
bigtent-yahoo{1,2,3}.idweb
Ideally these will be SL6 on the new prod VM gear.
Not sure if our global ACLs are implemented in scl2 & phx1 prod yet... so this may be blocked on that.
Assignee: nobody → ckolos
| Assignee | ||
Comment 2•13 years ago
|
||
dns done
| Assignee | ||
Comment 3•13 years ago
|
||
completed
inventory is as follows:
[root@vm2-1.scl2.svc ~]# virsh list --all
Id Name State
----------------------------------
3 bigtent-microsoft1.idweb.scl2 running
5 bigtent-yahoo2.idweb.scl2 running
7 bigtent-google3.idweb.scl2 running
[root@vm2-2.scl2.svc ~]# virsh list --all
Id Name State
----------------------------------
6 bigtent-yahoo3.idweb.scl2 running
7 bigtent-google1.idweb.scl2 running
8 bigtent-microsoft2.idweb.scl2 running
[root@vm2-3.scl2.svc ~]# virsh list --all
Id Name State
----------------------------------
3 bigtent-yahoo1.idweb.scl2 running
6 bigtent-google2.idweb.scl2 running
7 bigtent-microsoft3.idweb.scl2 running
| Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 5•13 years ago
|
||
Chris, can you build out the 9 at phx1 (same as scl2)
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 6•13 years ago
|
||
all built. scl2 and phx1.
bigtent-google1.idweb.scl2.svc.mozilla.com: 17:52:12 up 39 days, 6 min, 0 users, load average: 0.00, 0.03, 0.01
bigtent-google2.idweb.scl2.svc.mozilla.com: 17:52:12 up 42 days, 5:36, 0 users, load average: 0.00, 0.01, 0.00
bigtent-google3.idweb.scl2.svc.mozilla.com: 17:52:12 up 19 days, 5:08, 0 users, load average: 0.02, 0.02, 0.00
bigtent-microsoft1.idweb.scl2.svc.mozilla.com: 17:52:12 up 19 days, 5:08, 0 users, load average: 0.00, 0.02, 0.00
bigtent-microsoft2.idweb.scl2.svc.mozilla.com: 17:52:12 up 39 days, 6 min, 0 users, load average: 0.00, 0.00, 0.00
bigtent-microsoft3.idweb.scl2.svc.mozilla.com: 17:52:12 up 42 days, 5:36, 0 users, load average: 0.00, 0.00, 0.00
bigtent-yahoo1.idweb.scl2.svc.mozilla.com: 17:52:12 up 42 days, 5:36, 0 users, load average: 0.00, 0.00, 0.00
bigtent-yahoo2.idweb.scl2.svc.mozilla.com: 17:52:12 up 19 days, 5:08, 1 user, load average: 0.00, 0.00, 0.00
bigtent-yahoo3.idweb.scl2.svc.mozilla.com: 17:52:12 up 19 days, 5:02, 0 users, load average: 0.00, 0.00, 0.00
bigtent-google1.idweb.phx1.svc.mozilla.com: 17:51:17 up 6:55, 0 users, load average: 0.00, 0.00, 0.00
bigtent-google2.idweb.phx1.svc.mozilla.com: 17:51:17 up 18 days, 8:23, 0 users, load average: 0.00, 0.00, 0.00
bigtent-google3.idweb.phx1.svc.mozilla.com: 17:51:17 up 18 days, 8:27, 0 users, load average: 0.00, 0.00, 0.00
bigtent-microsoft1.idweb.phx1.svc.mozilla.com: 17:51:17 up 18 days, 8:27, 1 user, load average: 0.08, 0.05, 0.01
bigtent-microsoft2.idweb.phx1.svc.mozilla.com: 17:51:17 up 6:55, 0 users, load average: 0.00, 0.00, 0.00
bigtent-microsoft3.idweb.phx1.svc.mozilla.com: 17:51:17 up 18 days, 8:23, 0 users, load average: 0.00, 0.00, 0.00
bigtent-yahoo1.idweb.phx1.svc.mozilla.com: 17:51:17 up 18 days, 8:23, 0 users, load average: 0.12, 0.04, 0.01
bigtent-yahoo2.idweb.phx1.svc.mozilla.com: 17:51:17 up 18 days, 8:26, 0 users, load average: 0.00, 0.00, 0.00
bigtent-yahoo3.idweb.phx1.svc.mozilla.com: 17:51:17 up 6:55, 0 users, load average: 0.23, 0.60, 0.39
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Comment 7•13 years ago
|
||
OK. No SSH or ping access to Prod VMs, but I was able to 'host" all of these.
Will use Comment 6 as verification.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•