Closed Bug 438950 Opened 17 years ago Closed 17 years ago

Clone production-prometheus-vm for secondary 1.8 build machine

Categories

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

Product:
mozilla.org Graveyard
Component:
Server Operations
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: joduinn, Assigned: mrz)

References

Details

This should be a clone of production-prometheus-vm. This can go on "slower" sata disks.
Assignee: server-ops → mrz
cold clones are cleaner - can this be take offline?
hostname?
pass back when ready to clone.
Assignee: mrz → nobody
Component: Server Operations → Release Engineering
QA Contact: justin → release
production-prometheus-vm is now offline, so you can clone from it. Can you please call the new clone "production-prometheus-vm02"?
Assignee: nobody → server-ops
Component: Release Engineering → Server Operations
QA Contact: release → justin
SATA or FCAL?
Assignee: server-ops → mrz
(In reply to comment #0) > This should be a clone of production-prometheus-vm. > > This can go on "slower" sata disks. > (In reply to comment #5) > SATA or FCAL? > sata.
Cloned @ production-prometheus-vm02 / 10.2.71.138
Status: NEW → RESOLVED
Closed: 17 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.