ReferencePlatforms/Test/WinXP

Configuration Details

From XP SP2 OEM, X11-45391

Downloaded Software Updates

TODO

Configuration Changes

• Turned OFF all automatic updates
• Turned ON firewall; allowed RDP and SSH
• Turned off all MS networking, leaving only TCP/IP
• Created tester account
• Turned on RDP; allowed tester and Administrator to connect
• Turned off screensavers
• Select 'Windows XP' theme in Display options
• Select screen size 1280x1024 in Display options
• Turn off all sleep features.
• My Computer -> Properties -> Advanced -> Performance -> Custom -> Select all checkboxes

Install supplemental language support

(from http://www.microsoft.com/globaldev/handson/user/xpintlsupp.mspx)

• used XP SP2 OEM, X11-45391

Install Third-party applications

• Python 2.4.4
  • 'Install for all users'
  • Append 'C:\python24;c:\python24\scripts' to the PATH.
• Python Win32 Extensions
• PyYaml
• Info-Zip
  1. Download and extract Info-Zip
  2. Place 'unzip.exe' and 'unzip32.dll' in c:\windows
• CVS
  1. Download CVS
  2. Extract to c:\windows
• Wget
  1. Download Wget to c:\windows
• Chmod, rm, etc.
  1. Download and install Coreutils
  2. Append 'c:\program files\gnuwin32\bin' to PATH.
• Twisted 2.4.0 (Includes zope-interface)

Speedswitch XP

• bug 393940

RealVNC

VNC *must* be used to get real performance numbers. Download and install RealVNC.
On the 'Select Additional Tasks' page use the following options:
[x] Register and configure VNC Server for Service-Mode
[x] Start the VNC Server in Service-Mode
When the 'VNC Server Properties (Service-Mode)' window pops up:

1. Use 'VNC Password Authentication'
2. Click 'Configure' and set a password
3. Click 'Connections'
4. Make sure 'Accept connections on port:' is checked and set to port 5900
5. Uncheck 'Serve Java viewer via HTTP'.
6. Restart the computer

Do not logon with RDP from this point on. It will break the VNC server.

Buildbot

cvs -d:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -d buildbot mozilla/tools/buildbot
cd buildbot
c:\python24\python setup.py build
c:\python24\python setup.py install

Change the contents of c:\python24\scripts\buildbot.bat to '@python c:\python24\scripts\buildbot %*

Setting up a Buildbot Slave

How to setup a Buildbot Talos slave (replace the master.host, username, and password with the correct values)

cd c:\
mkdir talos-slave
buildbot create-slave talos-slave master.host:9989 username password

Edit the buildbot.tac file to have keepalive = None

You should then start the slave once to create the proper directory structure.

buildbot start talos-slave
buildbot stop talos-slave

Apache

The DocumentRoot will be dependent on the builddir of your Buildbot slave. In this section that directory will be referred to as $BUILDDIR.

For machines in the pool of slaves, $BUILDDIR should be 'talos-data'.

Pageset

You will need to install a page set in c:\pages.

The rest

• Download and install Apache 2.2.4
• Set 'Network Domain' and 'Server Name' to 'localhost'.
• Create an empty directory so Apache doesn't complain:

mkdir c:/talos-slave/$BUILDDIR/talos

• Change DocumentRoot and 'C:/Program Files..." <Directory> tag to 'c:/talos-slave/$BUILDDIR/talos'.
• Add an alias so Apache knows where the pageset is. Add this to your httpd.conf:

Alias /page_load_test/pages c:/pages
<Directory c:/pages>
    Options Indexes
    Order allow,deny
    Allow from all
</Directory>

• Restart Apache from the system tray icon
• Test the install by browsing to 'http://localhost/page_load_test/framecycler.html'. You should see rapidly changing pages.
• Turn off logging, remove any lines that begin with "CustomLog"

Updating Talos

Assuming your Buildbot master configuration is proper, Buildbot will automatically update Talos on every performance run. If the pageset is updated, you will need to refresh c:/pages.

Post-cloning Setup for Pool

OPSI Installation

• Start Menu -> Run -> 'cmd'
• Run the following in the command line:

cd c:\users\mozqa
install-opsi.bat

You will be prompted twice for a username and password. The first time, use 'pcpatch' and the standard root password. The second time, use 'root' and the standard root password.

Then,

• Open up the OPSI Client and look for the slave
  • Highlight the slave, go to Log Files, and then opsiconfd - look for errors in that log.

If the slave shows up in the OPSI client, and there's no errors in the opsiconfd log, you're done! If it doesn't, or there is errors, cry (and talk to bhearsum).

The rest

• Edit c:\talos-slave\buildbot.tac.sample and update buildmaster_host and slavename appropriately
• Rename buildbot.tac.sample to buildbot.tac
• Reboot