id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
1734	"set up marlowe's ""speed-fiber"" buildslave"	warner	marlowe	"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.
"	task	closed	normal	soon (release n/a)	dev-infrastructure	n/a	wontfix	performance speed bandwidth buildslave