PIFR 2 client added to Pantheon

In order to support qa.drupal.org in testing Drupal 7, we've made a AMI of PIFR 2 on Debian Lenny (64-bit). The purpose of this client is to grab a test from qa.drupal.org, run it, and send the results back to the server.

If you wish to fire up an instance and donate to testing of Drupal 7, here are the instructions (from http://qa.drupal.org/node/44):

1. Get an account on the master server or have someone add your client test server and provide you an API key.
2. If you create the account yourself on the master server, in your master server account, at user/#/pifr, add a client of type Test on the master and copy the key to the client at admin/pifr/configuration.
3. At admin/pifr/configuration on the client (default username/password is drupaltesting1/testingadmin, add the API key and master server URL. The other client defaults are OK. For maximum performance, set concurrency to at least the number of CPU cores available for testing on the server. If unsure, check the output of htop, which is installed (an AWS large instance is 2 cores)
4. Toggle the state on the client so it is enabled at admin/pifr.
5. On the master server at user/#/pifr or admin/pifr/server, enable the client in the operations field.

The next cron on the client should start a self test. If the self test succeeds, it will start testing patches from the project server. The client will list the number of test assertions it has completed for a test at admin/pifr. Note the client will run a complete cycle of patch testing twice before becoming enabled for project patch testing. The first it to make sure the client correctly catches an intentional breakage of the checkout. The second is to make sure a clean checkout has no failures or exceptions.

The AMI ID's are:

US-East: ami-e240a28b
US-West: ami-4d207108
EU-West: ami-bdecc7c9