set up marlowe's "speed-fiber" buildslave

[warner]

As per discussion on IRC, let's set up a speedtest builder using Marlowe's fiber-to-the-home link (15MB upstream, wow!).

The slavename is "marlowe-fiber", and uses the credentials I previously sent out. Necessary tasks on marlowe's side:

• pick a SLAVEDIR. I recommend creating a separate user account just for the buildslave, maybe named "bb-tahoe", in which case SLAVEDIR could be ~bb-tahoe/slave-tahoe
• buildslave create-slave SLAVEDIR MASTER marlowe-fiber PASSWORD
• tahoe create-client -n marlowe-fiber -i SPEEDGRIDINTROFURL ~/tahoe-speed-client
• buildslave start SLAVEDIR
• add a cronjob to start the buildslave at reboot

(you might want to add -p tcp:PORT:interface=127.0.0.1 to keep it from stealing 3456, if you use other tahoe clients on that box. The test will work with any random port, and reads it from the clientdir each time)

The buildmaster should be ready to roll.. once you do 'buildslave start', it should take over. I've configured it to run nightly (at 5am pacific), but you can check that it's working by just hitting the "force build" button on the "speed-fiber" builder.

[warner]

oh, you'll also need to edit tahoe.cfg and set shares.happy=1, since the performance-testing grid doesn't have a full complement of servers.

How this works: the buildslave will update it's copy of the tahoe source code, build it, then use that bin/tahoe to start the client in ~/tahoe-speed-client. That client will connect to the perfgrid. Then the buildslave will tell the client to upload/download files in a variety of sizes, measuring the time it takes. When the test is done, the client will be shut down. So you have to configure the client ahead of time, but don't need to start it (the buildslave will take care of that).

[warner]

closing this stale one as a WONTFIX.. the perfnet infrastructure is no longer around (we don't have the Atlas machines anymore). If someone offers a new home-connection buildslave, and we can find somewhere to host the perfnet server side of it, we can revisit this one.