ReleaseEngineering/How To/Set Up a Freshly Imaged Slave: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
No edit summary |
|||
| Line 12: | Line 12: | ||
* Build/Try slaves | * Build/Try slaves | ||
** Host names: w64-ix-* or b-2008-ix-* | ** Host names: w64-ix-* or b-2008-ix-* | ||
** | ** No additional steps needed. Simply enable on slavealloc | ||
* Test slaves | * Test slaves | ||
** Host names: t-xp32-ix, t-w732-ix, t-w864-ix | ** Host names: t-xp32-ix, t-w732-ix, t-w864-ix | ||
** No additional steps needed. Simply enable on slavealloc | ** No additional steps needed. Simply enable on slavealloc | ||
Revision as of 02:39, 16 July 2014
If the machine is a re-purposed machine there are more steps that these needed. Check 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/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
- Host names: w64-ix-* or b-2008-ix-*
- No additional steps needed. Simply enable on slavealloc
- Test slaves
- Host names: t-xp32-ix, t-w732-ix, t-w864-ix
- No additional steps needed. Simply enable on slavealloc