Opened at 2011-12-01T19:04:48Z
Last modified at 2013-01-04T20:29:25Z
#1629 new enhancement
auto-configuration of tub.location for nodes running on EC2
| Reported by: | davidsarah | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | code-network | Version: | 1.9.0 |
| Keywords: | usability config aws ec2 LeastAuthority.com | Cc: | |
| Launchpad Bug: |
Description
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 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 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.
Change History (3)
comment:1 Changed at 2012-03-29T19:15:36Z by davidsarah
- Priority changed from major to normal
comment:2 Changed at 2012-04-01T04:33:49Z by davidsarah
- Type changed from defect to enhancement
comment:3 Changed at 2013-01-04T20:29:25Z by zooko
- Keywords LeastAuthority.com added; lae removed
Note: See
TracTickets for help on using
tickets.
