1) We have foopies in MTV, which per meeting w/IT, are being moved to the new MTV office with the tegras, lock-stock-and-barrel, until end 2014. 2) We have foopies in SCL1, which we need to decide what to do with. Specifically in SCL1: foopy25.build.scl1.mozilla.com foopy33.build.scl1.mozilla.com foopy34.build.scl1.mozilla.com foopy35.build.scl1.mozilla.com foopy36.build.scl1.mozilla.com foopy37.build.scl1.mozilla.com From email w/coop, foopy2534/36 are still powered on, but *not* in use, so could be moved/reimaged at any time. From email w/arr, these foopies are all HP machines, which we could reuse as linux64 builders.
John, is this a request to repurpose the HPs in scl1, or did you want some discussion to take place within releng before deciding that?
Amy, let's go ahead and re-purpose these as linux64 builders. I'll file dependent bugs for RelEng to handle the rest of the work.
Per bug https://wiki.mozilla.org/ReleaseEngineering/Slave_Naming these will be called: b-linux64-hp-001.build.scl1.mozilla.com b-linux64-hp-002.build.scl1.mozilla.com b-linux64-hp-003.build.scl1.mozilla.com b-linux64-hp-004.build.scl1.mozilla.com b-linux64-hp-005.build.scl1.mozilla.com b-linux64-hp-006.build.scl1.mozilla.com
Summary: decide what to do with remaining foopies in SCL1+MTV → repurpose old HP foopies as linux64 builders
These are all up and running now.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.