Tahoe on AWS

[Daira Hopwood]

On 20/12/14 22:03, 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 imaged the first machine after creating the base directory for
the Tahoe-LAFS node, this might not work properly. The problem is that
the nodes will all have the same tubid, private key, etc., so they won't
be distinguishable as separate nodes. You need to create each node using
a separate 'tahoe create-node' command, unfortunately.

-- 
Daira Hopwood ⚥

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20141220/54096543/attachment.pgp>