On Thu, 2011-06-09 at 15:41 -0400, Chris Lalancette wrote: > Unfortunately, there is a big problem with this; the instance > ID does not always exist immediately after the ec2.launch_instances > call returns. This seems to be a generic problem with EC2, > as I've run into it several times.
The loadbalancer thing isn't much of an issue, but the instance tagging is a huge problem, since that is used to implement the user_name feature for EC2. Since tagging isn't atomic (even if EC2 behaved well, there's still a chance that our request to tag the instance fails), we should not pretend that EC2 allows assigning user-defined names to instances. ACK to this patch; it also needs to remove line 45 'feature :instances, :register_to_load_balancer' - incidentally, the EC2 drive never advertised the :user_name feature, so nothing to remove there. David
