Tahoe on AWS

[Greg Troxel]

Sameer Verma <sverma at sfsu.edu> writes:

> I'm trying to set up a system of 1 introducer and 10 storage nodes on
> AWS, plus one client on my laptop. The introducer sets up, but when I
> run it, the introducer.furl always reflects the internal IP that AWS
> assigns and not the public IP. Is there a way around this?

How do you ensure that the storage for the 10 nodes are on different
physical disks, and that some of them are in different locations?  Does
Amazon export that kind of information, and let you supply constraints,
beyond partial-continent availability zones?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 180 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20141219/1ba1af6c/attachment.pgp>