Closed Bug 975578 Opened 10 years ago Closed 10 years ago

moving panda infrastructure from scl1->scl3

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hwine, Assigned: hwine)

References

Details

Please move the 10 racks of pandas & support equipment from scl1 to scl3
in 4 separate batches as follows:

 - each batch must be in production use in scl3 before the next one
comes down in scl1
 - all equipment in each rack must stay together to preserve
configuration details (of support gear, all network config will change)

RelEng will need one business day notice to turn off the racks.
RelEng will need one full business day to return units to production,
assuming no issues.

The batch sizes we can accommodate without closing trees is 2 or 3
racks. Our preferred sequence is to start with batches of 2 racks to
work out any issues in process.

Please open blocker bugs for the actual work on each batch.
Anything left here?
Just to celebrate victory again! \o/
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.