Closed
Bug 880893
Opened 11 years ago
Closed 10 years ago
Request to borrow an r4 mini
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: shnguyen, Assigned: pmoore)
References
Details
(Whiteboard: [buildduty][loaner])
Hi, I will be evaluating new os x deployment software and will need to borrow an r4 snow leopard mini from scl1. Can you guys pull one from production so that I can use it for testing with the os x imaging software? Also, this will be a *long term* borrow. Please let me know, thanks!
Flags: needinfo?(coop)
Comment 1•11 years ago
|
||
Say hi to our intern, Shawn :} An r4 lion machine would work as well; we just need some sort of r4 that we can wipe and reinstall to test out both lion and snow leopard. We'll be temporarily relocating it to scl3 and probably using it for a month or two.
Comment 2•11 years ago
|
||
buildduty can give a hand with this.
Assignee: nobody → aki
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: armenzg
Whiteboard: [buildduty]
Comment 3•11 years ago
|
||
Hi Shawn! Thanks for your help!
Updated•11 years ago
|
Flags: needinfo?(coop)
Comment 4•11 years ago
|
||
talos-r4-lion-007 was scheduled for reboots-scl1; now I'm going to mark it for Shawn.
Assignee: aki → shnguyen
Comment 5•11 years ago
|
||
(Please unassign when you're done with it.)
Whiteboard: [buildduty] → [buildduty][loaner]
Updated•11 years ago
|
Blocks: talos-r4-lion-007
Reporter | ||
Comment 7•11 years ago
|
||
Hi Ben, Yes, I am still using it at the moment.
Comment 8•11 years ago
|
||
We'll be using it for a couple months, yes.
Updated•11 years ago
|
Flags: needinfo?(shnguyen)
Updated•11 years ago
|
Component: Release Engineering: Machine Management → Release Engineering: Loan Requests
QA Contact: armenzg → coop
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 9•11 years ago
|
||
Hi arr, is this host still being used?
Comment 10•11 years ago
|
||
Still in use. Will be until about mid-Q4 I suspect (since we're waiting on new hardware to replace the imaging system).
Comment 11•11 years ago
|
||
Still waiting on the new hardware to be racked/cabled.
Comment 12•11 years ago
|
||
Does the plan to re-image all lion machines as snow machines change anything in here? I can mark it in our code as not in production until this work is done. I just need to know what talos-r4-lion-007 will turn into so I can file the proper problem tracking bug.
Flags: needinfo?(arich)
Summary: Request to borrow an r4-snow → Request to borrow an r4 mini
Comment 13•11 years ago
|
||
It will eventually turn into a snow machine, but not for a while till we get casper working. It'll probably get turned into snow-171, but I would wait till we're actually ready to reimage it since it's in SCL3, not SCL1, so that will change things.
Flags: needinfo?(arich)
Comment 15•10 years ago
|
||
This is actually the only r4 system we have to test things out on because we gave releng all of our test r4s back when there was a big crunch when we were still running snow leopard and lion test machines. I think I'd like to just keep this one permanently (now that we've gotten rid of lion testers, we've doubled the size of the snow leopard pool) and close out this bug. Work for you?
Flags: needinfo?(arich)
Assignee | ||
Comment 16•10 years ago
|
||
Coop, I'd like to defer to you on this. I've checked; talos-r4-lion-00 it is currently not listed in slavealloc (it never got upgraded to mtnlion - see the tracking bug). It still has a tracking bug. If we give it permanently to relops, what admin is there for us to do (e.g. do we need to update anything in invtool to say which team hardware is assigned to etc?). Should we also close the tracking bug? From a capacity perspective, I guess one machine less does not have a big impact hit, what do you think? Thanks, Pete
Flags: needinfo?(coop)
Comment 17•10 years ago
|
||
Yes, relops can keep it. We are already making due without it.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(coop)
Resolution: --- → WONTFIX
Assignee | ||
Comment 18•10 years ago
|
||
Do we need to take care of any admin to keep track of this handover?
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(coop)
Comment 19•10 years ago
|
||
(In reply to Pete Moore [:pete][:pmoore] from comment #18) > Do we need to take care of any admin to keep track of this handover? At the very least, we should comment in the slave problem tracking bug (and then close it) and add a comment to slavealloc. We should also remove the slave from our buildbot-configs.
Flags: needinfo?(coop)
Assignee | ||
Comment 20•10 years ago
|
||
It isn't in slavealloc, and does not appear in buildbot-configs (I guess since it missed the migration from lion to mtnlion) - so I've closed the tracking bug, and it sounds like that should be enough. Thanks! Pete
Assignee: shnguyen → pmoore
Updated•6 years ago
|
Component: Loan Requests → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•