These will be separated from the main pool of machines and need to have their keys removed, passwords changed, etc. Hopefully we'll be able to puppet our way to all of this.

Looks like neither passwords nor keys are puppet managed on bld-lion-r5 machines. All we need to do here is pick a couple of machines, clean out their buildslave dir, and repoint them in slavealloc.

Going to use bld-lion-r5-095 and 096 for this. Dustin is using 096 to work on bug 760093 right now.

Comment on attachment 742444 [details] [diff] [review] remove them from old puppet Updated scl3-production-puppet.

In production

When the DNS zones and DHCP bits are correctly generated, these should be renamed as follows: bld-lion-r5-095 -> servo-lion-r5-001.build.servo.releng.scl3.mozilla.com 10.26.80.21 bld-lion-r5-096 -> servo-lion-r5-002.build.servo.releng.scl3.mozilla.com 10.26.80.22

(In reply to Amy Rich [:arich] [:arr] from comment #7) > When the DNS zones and DHCP bits are correctly generated, these should be > renamed as follows: > > bld-lion-r5-095 -> servo-lion-r5-001.build.servo.releng.scl3.mozilla.com > 10.26.80.21 > bld-lion-r5-096 -> servo-lion-r5-002.build.servo.releng.scl3.mozilla.com > 10.26.80.22 I updated inventory with these changes - both the name of the host + the key/value store.

These machines are connected to the master now. If we need script changes or buildbot master config changes to make the builds work I'll file a new bug.