Tahoe on AWS

[Sameer Verma]

On Fri, Dec 19, 2014 at 3:20 AM, Greg Troxel <gdt at ir.bbn.com> wrote:
>
> 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?

I haven't gotten that far yet :-) AWS does allow you to pick regions
to run the machine, so that should provide different zones. If I was
doing this for daily use, I'd probably run a few machines on AWS in
different regions, but not all. I'd pick other cloud providers or
locations.

cheers,
Sameer