| 2012-02-01 19:24:59 |
Duncan McGreggor |
bug |
|
|
added bug |
| 2012-02-01 19:25:50 |
Duncan McGreggor |
txaws: assignee |
|
DreamObjects Team (dreamobjects-team) |
|
| 2012-02-01 19:25:55 |
Duncan McGreggor |
txaws: importance |
Undecided |
High |
|
| 2012-02-01 19:25:58 |
Duncan McGreggor |
txaws: milestone |
|
0.3 |
|
| 2012-02-01 23:00:35 |
Duncan McGreggor |
txaws: status |
New |
In Progress |
|
| 2012-02-01 23:09:32 |
Duncan McGreggor |
branch linked |
|
lp:~dreamhosters/txaws/925052-improved-endpoints |
|
| 2012-02-02 00:35:53 |
Duncan McGreggor |
description |
Users/developers not familiar with txAWS can be easily confused by the default settings for regions and endpoints.
We should improve the error message for null results on instance queries that indicate something along the lines of "No instances found for %(region)s at endpoint %(endpoint)s."
We should add an option "all" (NOT enabled by default) that will iterate through all regions/endpoints, building a list of any running instances.
Depends on:
bug #925050 |
Users/developers not familiar with txAWS can be easily confused by the default settings for regions and endpoints.
We should improve the error message for null results on instance queries that indicate something along the lines of "No instances found for %(region)s at endpoint %(endpoint)s."
We should add an option "all" (NOT enabled by default) that will iterate through all regions/endpoints, building a list of any running instances.
Or perhaps, better than that, would be a new method on AWSServiceRegion that finds active instances and returns a region object for each instance.
Depends on:
bug #925050 |
|
| 2012-02-04 06:18:38 |
Duncan McGreggor |
description |
Users/developers not familiar with txAWS can be easily confused by the default settings for regions and endpoints.
We should improve the error message for null results on instance queries that indicate something along the lines of "No instances found for %(region)s at endpoint %(endpoint)s."
We should add an option "all" (NOT enabled by default) that will iterate through all regions/endpoints, building a list of any running instances.
Or perhaps, better than that, would be a new method on AWSServiceRegion that finds active instances and returns a region object for each instance.
Depends on:
bug #925050 |
Users/developers not familiar with txAWS can be easily confused by the default settings for regions and endpoints.
We should improve the error message for null results on instance queries that indicate something along the lines of "No instances found for %(region)s at endpoint %(endpoint)s."
We should also add a new method on AWSServiceRegion that finds active instances and returns a region object for each instance.
Depends on:
bug #925050 |
|
