Closed
Bug 548231
Opened 15 years ago
Closed 15 years ago
Recycle 20 talos-rev2 machines for staging
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: joduinn, Assigned: jabba)
References
Details
(Whiteboard: ETA 03/11/2010)
As we bring the rev3 machines online, we can phase out the rev2 machines. The first batch of 80 rev2 minis are being recycled as follows:
20 added to osx10.5 production build/unittest pool
40 added to osx10.6 production build/unittest pool
...which leaves
20 for staging.
I'd originally thought of setting these up for talos for osx10.5, osx10.6, xp, win7, linux32, but curious if people have other suggestions. For example, instead of all 20 being staging talos, should some of these become staging builders?
Comment 1•15 years ago
|
||
Break down into:
talos-rev2-snow-001/002/003
talos-rev2-fed-001/002/003
talos-rev2-fed64-001/002/003
talos-rev2-xp-001/002/003
talos-rev2-w7-001/002/003
talos-rev2-leopard-001/002/003
talos-rev2-w764-001/002
Since we don't have an actual talos w7 x64 image yet we can just leave them idle and waiting.
Reporter | ||
Comment 2•15 years ago
|
||
now ok to push over to IT and start imaging.
Assignee: joduinn → server-ops
Component: Release Engineering → Server Operations
QA Contact: release → mrz
Comment 3•15 years ago
|
||
Upon reflection, for consistency we should call them 'r2' instead of 'rev2' - so that they match naming in production.
Summary: Recycle 20 talos-rev2 machines for staging → Recycle 20 talos-r2 machines for staging
Updated•15 years ago
|
Summary: Recycle 20 talos-r2 machines for staging → Recycle 20 talos-rev2 machines for staging
Comment 4•15 years ago
|
||
(In reply to comment #1)
> Break down into:
>
> talos-rev2-snow-001/002/003
> talos-rev2-fed-001/002/003
> talos-rev2-fed64-001/002/003
> talos-rev2-xp-001/002/003
> talos-rev2-w7-001/002/003
> talos-rev2-leopard-001/002/003
> talos-rev2-w764-001/002
>
> Since we don't have an actual talos w7 x64 image yet we can just leave them
> idle and waiting.
We only rev2 (r2) ref images for leopard and xp. Since we already have these up and working, are there any advantages to re-imaging these?
There are no snow leopard, fed, fe64, win7, or win764 ref images or even ref machines for them at the moment.
Assignee: server-ops → phong
Flags: colo-trip+
Reporter | ||
Comment 5•15 years ago
|
||
Raising to critical, because its blocking a q1 goal, as discussed with Phong, mrz yesterday morning.
(In reply to comment #4)
> (In reply to comment #1)
> > Break down into:
> >
> > talos-rev2-snow-001/002/003
> > talos-rev2-fed-001/002/003
> > talos-rev2-fed64-001/002/003
> > talos-rev2-xp-001/002/003
> > talos-rev2-w7-001/002/003
> > talos-rev2-leopard-001/002/003
> > talos-rev2-w764-001/002
> >
> > Since we don't have an actual talos w7 x64 image yet we can just leave them
> > idle and waiting.
>
> We only rev2 (r2) ref images for leopard and xp. Since we already have these
> up and working, are there any advantages to re-imaging these?
If its easier to just do the renaming/dns work without imaging then that is fine.
> There are no snow leopard, fed, fe64, win7, or win764 ref images or even ref
> machines for them at the moment.
We have ref images for these OS for rev1 and rev3 machines. Can we try them on these ref2 machines ?
Severity: normal → critical
Updated•15 years ago
|
Assignee: phong → jdow
Whiteboard: ETA 03/11/2010
Assignee | ||
Comment 6•15 years ago
|
||
Need to be freshly imaged.
Comment 7•15 years ago
|
||
Please wipe and re-image, I'd prefer to work from a fresh image.
Assignee | ||
Comment 8•15 years ago
|
||
> > talos-rev2-xp-001/002/003 -- done
Need ref images for following:
> > talos-rev2-fed64-001/002/003
> > talos-rev2-w7-001/002/003
> > talos-rev2-w764-001/002
Assignee | ||
Comment 9•15 years ago
|
||
Current status:
Done:
talos-rev2-snow-001/002/003
talos-rev2-xp-001/002/003
talos-rev2-leopard-001/002/003
Ref Image needed:
talos-rev2-fed-001/002/003
talos-rev2-fed64-001/002/003
talos-rev2-w7-001/002/003
talos-rev2-w764-001/002
I have all the minis at my desk if a machine is needed to create the reference images.
Comment 10•15 years ago
|
||
Have we attempted applying the rev3 images on rev2 machines?
Also - are the imaged machines up and ready for me to access?
Assignee | ||
Comment 11•15 years ago
|
||
(In reply to comment #10)
> Have we attempted applying the rev3 images on rev2 machines?
>
Yes, and the rev3 images for linux and windows don't work on them. The leopard and snow images took fine though, which is why those are finished.
> Also - are the imaged machines up and ready for me to access?
Not yet. They are sitting at my desk, but I can bring most of them by, as those lived in the office before. The ones that still need to be imaged will live at MPT.
Reporter | ||
Comment 12•15 years ago
|
||
(In reply to comment #11)
> (In reply to comment #10)
> > Have we attempted applying the rev3 images on rev2 machines?
> >
> Yes, and the rev3 images for linux and windows don't work on them. The leopard
> and snow images took fine though, which is why those are finished.
urgh. Instead of dealing with new ref images, we're changing plans.
1) We'll pull some existing rev3 minis from production talos, to use in staging talos for now.
2) 10 of these rev2 minis will be added to the 10.5 build pool in bug#548106
3) 10 of these rev2 minis will be added to the 10.6 build pool in bug#548109
We'll close this bug as WONTFIX, with apologies for time already spent here.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•