Closed Bug 564058 Opened 15 years ago Closed 15 years ago

Move try slaves out of sandbox and into build network

Categories

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

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
x86
All
Type:
task
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: lsblakk, Assigned: jabba)

References

Details

Please move try-w32-slave20 (10.2.76.173) out of the sandbox and into the build network.
Also move try-linux-slave08 and try-mac-slave13 into build.
OS: Windows Server 2003 → All
Summary: Move try-w32-slave20 into build network → Move try slaves out of sandbox and into build network
Severity: normal → major
Assignee: server-ops → jdow
Flags: colo-trip+
is there any else that needs to be done other than updating dns and moving the ports over to the buld vlan?
actually, yes. in fact these will need to be re-imaged with their respective ref-images since they are in the sandbox and not guaranteed to be safe. we should start with clean images in the build network.
Eta on this?
try-win32-slave20 and try-linux-slave08 are both VMs. Can I delete these now?
delete them and recreate them again with the same names, but in the build network? - yes
try-w32-slave20.build.m.o 10.2.90.170 try-linux-slave08.build.m.o 10.2.90.171
try-mac-slave13.build.m.o 10.2.90.173
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.