Confirmed users
4,467
edits
PostImage: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
Note: If you run into a "GRUB GRUB" error while booting, open the the IPMI console on a machine, boot an Ubuntu ISO(Virtual Storage), boot a 'rescue environment', then run "grub", with the commands "root (hd0,0)", and "setup (hd0)". After that, issue the command "dd if=/dev/sda of=mbr bs=512 count=63". Copy(and overwrite) the 'mbr' file onto the DeployStudio server into /Volumes/Deploy/Masters/PC/ImageName/mbr. That should fix the booting issue for all other imaged servers. | Note: If you run into a "GRUB GRUB" error while booting, open the the IPMI console on a machine, boot an Ubuntu ISO(Virtual Storage), boot a 'rescue environment', then run "grub", with the commands "root (hd0,0)", and "setup (hd0)". After that, issue the command "dd if=/dev/sda of=mbr bs=512 count=63". Copy(and overwrite) the 'mbr' file onto the DeployStudio server into /Volumes/Deploy/Masters/PC/ImageName/mbr. That should fix the booting issue for all other imaged servers. | ||
== Win32 (Server 2003 - build ref image) == | |||
=== Add slave(s) to configuration files === | |||
The following files need to be updated with new slaves (note that the production Buildbot config is explicitly not updated here, it will be done later): | |||
* [http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla2-staging/config.py buildbot-configs/mozilla2-staging/config.py] | |||
* [http://hg.mozilla.org/build/opsi-package-sources/file/tip/production-slaves opsi-package-sources/production-slaves] (or staging-slaves for slaves that will be in staging permanently). | |||
Once your patches have landed, you need to update the following checkouts: | |||
* On staging-master: | |||
# as cltbld | |||
cd /builds/buildbot/user-configs/clean-configs | |||
hg pull && hg up | |||
cd ../../user-configs2/clean-configs | |||
hg pull && hg up | |||
* On production-opsi (or staging-opsi if you updated staging-slaves): | |||
# as cltbld | |||
cd opsi-package-sources | |||
hg pull && hg up | |||
If the slave is re-using a hostname (eg, it has been recloned) you also need to remove it from the OPSI config on the server in order for it to get the correct hostkey. To do so, run the following command as root on the OPSI server: | |||
# .uib.local for production, .build.mozilla.org for staging | |||
opsi-admin -d method deleteClient win32-slaveNN.uib.local | |||
The slave will automatically be setup for OPSI and connect to [http://staging-master.build.mozilla.org:8010 staging-master]. | |||
=== Change OPSI server (staging slaves only) === | |||
If you are cloning or recloning a slave for staging the OPSI server needs to be adjusted in the registry. Open regedit and browse to HKEY_LOCAL_MACHINE\SOFTWARE\opsi.org\pcptch. Change the "opsiServiceURL" key to "https://10.2.71.216:4447". | |||
You also might need to uninstall and re-install opsi if the slave is connecting to production-opsi. | |||
In c:\program files\opsi.org\preloginloader\uninst run deinstall.cmd, slave will reboot then disconnect the mapped drive for production opsi, then do this: | |||
* Start Menu -> Run -> \\10.2.71.216 | |||
* Use 'pcpatch' and the root password when prompted. | |||
* Right click 'opt_pcbin' and select 'Mount as Network Drive' | |||
* Browse to z:\install\preloginloader | |||
* Double click 'opsi-prep.vbs' | |||
* Double click 'service-setup.cmd', hit a key when prompted | |||
* When prompted for a username and password use 'root' and the appropriate password. | |||
OPSI forces reboot on completion of install and then you can manage it through the opsi client. | |||
=== Set Buildbot to install === | |||
In the [http://people.mozilla.org/~bhearsum/misc/OPSI.jar OPSI Client], select the new slaves and do the following: | |||
* Select "Product Configuration" | |||
* In the "buildbot-production" row change the action to "setup" | |||
* Click the red checkmark. | |||
This will set buildbot to install on their first boot. | |||
===Run the slave through staging=== | |||
see [[ReleaseEngineering:BuildSlaveSetup]] | |||
= Windows XP = | = Windows XP = | ||
Open System Properties and go to Computer Name tab, click on Change and enter the host's hostname there. Then click on 'more settings' to add the hosts domain name to the DNS suffix field. | Open System Properties and go to Computer Name tab, click on Change and enter the host's hostname there. Then click on 'more settings' to add the hosts domain name to the DNS suffix field. | ||