Tahoe on AWS

[Lukas Pirl]

On 12/20/2014 11:03 PM, Sameer Verma wrote:
> From the perspective of setting this up on AWS and the fact that I'm
> doing this just for fun/learning right now, I came across an issue
> that was somewhat of a pain - setting up each machine individually and
> then providing each machine with a security profile that contained
> this port. So, I set up one security profile, with a specific port
> from the first storage node, and then made machine into an image. Then
> I deployed that image into 9 other instances. That way, I had
> tahoe-lafs and the config set up on each machine from the get go
> (storage 2-10 are copies of storage 1). All I had to do was to change
> the nickname on each machine (also a pain, but not bad).

If you like fun/learning anyways, experiment with the provisioner of
your choice to set up Tahoe hosts (i.e. operating systems) and the
corresponding nodes (i.e. Tahoe installations/configurations).

I recently did a similar thing: I wanted to learn how to work with
Ansible and I used it to set up a Tahoe grid. This way, I can easily add
another host and get the installation done while having a coffee. Pretty
nice. Besides that I have no experiences with Puppet, Chef and friends,
I can report that Ansible is working really well.

If anyone is interested, I could provide you with the Ansible (so
called) "roles" I created. They are not streamlined and documented so
far but once this is done, I'll publish those somewhere anyways.

Best,

Lukas