[tahoe-lafs-trac-stream] [tahoe-lafs] #1629: auto-configuration of tub.location for nodes running on EC2

[tahoe-lafs]

#1629: auto-configuration of tub.location for nodes running on EC2
------------------------------------------+---------------------------
 Reporter:  davidsarah                    |          Owner:
     Type:  defect                        |         Status:  new
 Priority:  major                         |      Milestone:  undecided
Component:  code-network                  |        Version:  1.9.0
 Keywords:  usability config aws ec2 lae  |  Launchpad Bug:
------------------------------------------+---------------------------
 A Tahoe node running on EC2 does not know its external IP address, unless
 it is configured in {{{[node]tub.location}}}. If the external IP changes,
 as can happen in [http://support.rightscale.com/06-FAQs/FAQ_0160_-
 _Can_the_public_or_private_IP_addresses_change_on_an_EC2_instance%3F some
 circumstances], the node will become inaccessible to external clients
 (even if it is still connected to an introducer that is using its
 EC2-internal address, for example).

 Potentially, the node could
 [https://forums.aws.amazon.com/message.jspa?messageID=122425 automagically
 detect that it is running on an EC2 instance] (at the same time getting
 its instance ID), and make an EC2 API call to get its current external IP.
 Extra credit if it can change its IP without needing to be restarted.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1629>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage