Closed
Bug 904672
Opened 11 years ago
Closed 11 years ago
install and configure the OS for new android x86 emulation servers
Categories
(Infrastructure & Operations :: RelOps: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: arich, Assigned: arich)
References
Details
(Whiteboard: [reit-x86])
Relops needs to create puppet node defs for the 64 new android x86 emulation nodes (same as the ubuntu test nodes) and kickstart them once they are installed in the datacenter.
Assignee | ||
Comment 1•11 years ago
|
||
clint/coop/hal, what should the names of these machines be? My understanding is that we're installing the linux64 ubuntu image on them, so should they match the hostnames of the rest of those machines (talos-linux64-ix-NNN), or should they have a new "OS" part like androidx86 and follow the naming convention at https://wiki.mozilla.org/ReleaseEngineering/Slave_Naming and be: t-androidx86-ix-NNN
Flags: needinfo?(hwine)
Flags: needinfo?(ctalbert)
Flags: needinfo?(coop)
As far as I know, buildbot does not base any of its determinations of what to run where on the machine name (at least I hope not!) and so we can name these whatever we want. And given that the machine name should function as a mechanism to make it easy for your team (Amy) to find/fix/diagnose issues with these machines, I'd recommend naming them following the existing convention for the linux hardware machines since that's how your team will likely think of them. I'm happy to be overruled by releng if they have a preference though, as this is just my two cents.
Flags: needinfo?(ctalbert)
Comment 3•11 years ago
|
||
Armeng is our guru of names -- what do you suggest? (In reply to Clint Talbert ( :ctalbert ) from comment #2) > As far as I know, buildbot does not base any of its determinations of what > to run where on the machine name (at least I hope not!) and so we can name > these whatever we want. Buildbot doesn't care (directly), but lots of our other scripts do care. Consistency for the win!
Flags: needinfo?(hwine) → needinfo?(armenzg)
Comment 4•11 years ago
|
||
talos-linux64-ix-NNN please. We're just expanding the pool.
Flags: needinfo?(coop)
Flags: needinfo?(armenzg)
Assignee | ||
Comment 5•11 years ago
|
||
Great, thanks, I'll start the prep work on that.
Updated•11 years ago
|
Assignee | ||
Comment 6•11 years ago
|
||
talos-linux64-ix-056.test.releng.scl3.mozilla.com to talos-linux64-ix-111.test.releng.scl3.mozilla.com are now installed. Waiting on the last two chassis to finish up talos-linux64-ix-112.test.releng.scl3.mozilla.com to talos-linux64-ix-119.test.releng.scl3.mozilla.com
Assignee | ||
Comment 7•11 years ago
|
||
talos-linux64-ix-112.test.releng.scl3.mozilla.com to talos-linux64-ix-115.test.releng.scl3.mozilla.com now complete as well. Last chassis should be onsite within the next couple days.
Assignee | ||
Comment 8•11 years ago
|
||
All systems are now installed.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•