View source for ReleaseEngineering/How To/Set Up a Freshly Imaged Slave

{{Release Engineering How To|Set Up a Freshly Imaged Slave}}

If the machine is a re-purposed machine there are more steps that these needed. Check [[ReleaseEngineering/How_To/Create_new_slaves_or_move_them_to_other_pools|How to create new slaves or move them to other pools]].

If your machine has simply been re-imaged follow the instructions from the appropriate section.

= Linux/MacOS X (PuppetAgain) =
== Build/Try slaves ==
Puppet does everything. You should check to make sure that ~root/puppetize.log's modified time is after the re-image time.
== Linux AWS slaves ==
These are installed from golden AMIs created every night. There should be nothing for you to do here.
== Linux Talos slaves ==
After puppet is run, nothing else is needed.The machine can be returned back to service by simply enable in slavealloc.
You should check to make sure that ~root/puppetize.log's modified time is after the re-image time.
== Mac test slaves ==
Puppet does everything. You should check to make sure that ~root/puppetize.log's modified time is after the re-image time.


= Windows (GPO) =
== Build/Try slaves ==
* For Build and Try there no windows hardware machines ,only AWS,so since these are installed from golden AMIs which are created every night there should be nothing left to do here.
== Test slaves ==
* Host names: t-xp32-ix, t-w732-ix, t-w864-ix, t-w1064-ix
* No additional steps needed. Simply enable on slavealloc