Confirmed users
4,467
edits
PostImage: Difference between revisions
→Win32 (Server 2003 - build ref image)
No edit summary |
|||
| Line 18: | Line 18: | ||
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): | 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/buildbot-configs/file/tip/mozilla2-staging/config.py buildbot-configs/mozilla2-staging/config.py] | ||
| Line 42: | Line 42: | ||
The slave will automatically be setup for OPSI and connect to [http://staging-master.build.mozilla.org:8010 staging-master]. | 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". | 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". | ||
| Line 59: | Line 59: | ||
OPSI forces reboot on completion of install and then you can manage it through the opsi client. | 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: | In the [http://people.mozilla.org/~bhearsum/misc/OPSI.jar OPSI Client], select the new slaves and do the following: | ||
* Select "Product Configuration" | * Select "Product Configuration" | ||
| Line 67: | Line 67: | ||
This will set buildbot to install on their first boot. | This will set buildbot to install on their first boot. | ||
==Run the slave through staging== | |||
see [[ReleaseEngineering:BuildSlaveSetup]] | 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. | ||