ReleaseEngineering/How To/Create new slaves or move them to other pools

From MozillaWiki
< ReleaseEngineering‎ | How To
Revision as of 16:25, 2 November 2012 by Armenzg (talk | contribs) (Created page with "NOTE: This is a '''DRAFT''' and needs to be revised. The intention of this page is to contain information about: * a new machine that has never exited before ** we purchased mor...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

NOTE: This is a DRAFT and needs to be revised.

The intention of this page is to contain information about:

  • a new machine that has never exited before
    • we purchased more
    • we re-purposed (Win7 slaves instead of Leopard)
  • the machine is being moved in between pools

New machine or moving between production/staging (OPSI)

The machine is new or moving between production and staging (so the OPSI server does not know about it). If this is the case, you'll need to follow ReleaseEngineering/How_To/Move_a_Slave_Between_Production_and_Staging#OPSI these instructions.

Reimaged

The machine has been re-imaged (so the OPSI server already has a key for such host). If this is the case, remove the previous HostKey on the OPSI master and reboot the machine to register again with the OPSI master (this is mentioned at the end this section). To do so:

  • start -> run -> eventvwr
    • option -> action menu -> clear all events
  • find out the OPSI hostname of the slave by looking in /etc/opsi/pckeys (production-opsi)
  • then delete the old key with opsi-admin -d method deleteClient $hostname. You can also delete it in the OPSI.jar console through a right click.
  • reboot the machine