Hey, how would you feel about whirr generating a bit of ssh configuration for you? This would make it simpler to log into your whirr-launched machines (simply 'ssh publichostname') Tools like http://code.google.com/p/parallel-ssh/ also depend on a correctly setup passwordless ssh, so those would benefit as well.
The idea would be to inject something like this: ###### BEGIN WHIRR your-cluster-name ###### # This is automatically updated by whirr. Your puny manual editing hands stand no chance Host ec2-12.23.45.67.ec2.amazon-aws.com User yourclusteruser IdentityFile yourwhirr-private-key PasswordAuthentication no UserKnownHostsFile ~/.whirr/your-cluster-name/known_hosts I'm not sure yet about the UserKnownHostsFile. We could just use /dev/null + StrictHostKeyChecking = no, but that's less secure. WDYT?
