[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1734: set up marlowe's "speed-fiber" buildslave
Tahoe-LAFS
trac at tahoe-lafs.org
Fri Mar 20 19:28:13 UTC 2015
#1734: set up marlowe's "speed-fiber" buildslave
-------------------------+-------------------------------------------------
Reporter: warner | Owner: marlowe
Type: task | Status: closed
Priority: normal | Milestone: soon (release n/a)
Component: dev- | Version: n/a
infrastructure | Keywords: performance speed bandwidth
Resolution: wontfix | buildslave
Launchpad Bug: |
-------------------------+-------------------------------------------------
Changes (by warner):
* status: new => closed
* resolution: => wontfix
Old description:
> 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.
New description:
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.
--
Comment:
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.
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1734#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list