Closed Bug 765443 Opened 12 years ago Closed 12 years ago

what is the name of cb-vmware1 and its IP?

Categories

(SeaMonkey :: Release Engineering, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ewong, Assigned: ewong)

Details

cb-vmware1 was moved from sjc1 to scl3, but was renamed something else.
we'd like to know what it is (so we can update our records)
Assignee: server-ops → mburns
Ok, got a chat over IRC that solves this for serverOps, over to SeaMonkey::Releng for sake of getting our docs updated.

Assigning to ewong incase he feels up to doing so sanely (if you can't think of good wording, assign back to me and I'll grab it within the next week or two)

Anyway, heres a simple IRC log:

[19:03:35]	<lerxst>	Callek: i can speak to that bug a little bit.
[19:03:49]	<lerxst>	Callek: cb-vmware1 wasn't quite moved to scl3
[19:04:11]	<Aj>	Callek: lerxst: was about to comment as well inventory shows other wise .., thanks
[19:04:20]	<lerxst>	Callek: all the VMs it was hosting were either destroyed, moved to the scl3 esx cluster, or rebuilt as new VMs on the scl3 esx cluster
[19:04:20]	<Callek>	lerxst: what we want to know is basically "what host(s) are our current seamonkey VMs on"
[19:04:42]	<lerxst>	Callek: right. so the answer to that question is, it could be on any one of esx[1-12].private.scl3.mozilla.com. they move around as load is adjusted
[19:04:56]	<lerxst>	Callek: the only important thing you need to know for escalation is that your VMs are "on the scl3 esx cluster",
[19:05:03]	<Callek>	lerxst: ok, thats what we (needed) to know..
[19:05:05]	<lerxst>	Callek: the vCenter Server that manages that cluster is vc1.private.scl3.mozilla.com
[19:05:13]	<Callek>	lerxst: great -- thanks
[19:05:17]	<lerxst>	all of ops knows this too so you shouldn't have too much trouble during an escalation
[19:05:53]	<Callek>	lerxst: yea, I like to provide "what I think is enough info" and expand on that if someone has questions
[19:06:14]	<Callek>	and having the info for the expanded Q's is always helpful, especially if on-call ends up being a relatively new hire, and doesn't know all the finer details
[19:06:38]	<lerxst>	sure, totally understand
Assignee: mburns → ewong
Component: Server Operations → Release Engineering
Product: mozilla.org → SeaMonkey
QA Contact: phong → release
Version: other → unspecified
Updated the notes.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.