Closed Bug 501526 Opened 16 years ago Closed 15 years ago

Ensure geriatric machines are on MPT network

Categories

(mozilla.org Graveyard :: Server Operations: Projects, task)

x86
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jhford, Assigned: dmoore)

References

Details

There are 10 older computers which need to be able to report to Production-Master. To do this they need to be on the MPT network. The machines are currently in the server room at our Mountain View office.
There's going to be some engineering work involved here - we're not currently configured to bridge Vlan71 from the colo to the office. Do they -need- to be on the same Vlan? It's all routable.
Assignee: server-ops → dmoore
as long as they can establish a TCP session to production master it should be good.
..or to avoid any latency questions, once these machines are imaged up, would it be easier to just move these to the colo, along with the rest of the build machines?
Not really easier - the colo is really suited for rack mount hardware. Let's try this first and see what the results are.
John, I believe you said this was low prio but do you have a deadline we should be aware of?
Talked about this in the last RelEng meeting - there's some engineering work that has to happen on our side that we're working on.
Component: Server Operations → Server Operations: Projects
(In reply to comment #5) > John, I believe you said this was low prio but do you have a deadline we should > be aware of? From today's RelEng meeting, it looks like we'll need these systems up, and configured to be running unittests automatically several weeks before the 1.9.2 (FF3.6) release. Also, note that once these machines are up, it'll take RelEng a some days (<1 week) to configure them, and verify if they are working ok. (In reply to comment #6) > Talked about this in the last RelEng meeting - there's some engineering work > that has to happen on our side that we're working on. Curious - what work? If its about having MPT VPN visible in MV office, when would this be avaiable to start testing? Also, do we have a contingency in mind, in case the latency does turn out to be a problem?
Do you have a hard deadline?
Re: the placement of these servers in the MV office. We resolved the majority of expected hurdles during the build network expansion within MPT. The act of provisioning and integrating a new network with the existing build network is a very similar process to what we're looking at here. Latency is not an expected concern, as the network link from MV to MPT adds (on average) around 3ms of overhead compared to the local network.
We are going to have a buildbot master locally at 650 Castro
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.