[LIBCLOUD-367] Proper use of create_node and NodeAuthSSHKey

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.14.0-beta3
• Component/s: Compute
• Assignee: Tomaz Muraus
• Reporter: John Carr
• Created: 29/Jul/13 11:01
• Updated: 28/Nov/13 09:01
• Resolved: 01/Aug/13 17:52

Description

I've read through the documentation and code and it's not clear to me the proper way to do this.

My wishful thinking is that I can pass NodeAuthSSHKey to a Driver's create_node function as the 'auth' argument... if driver.features['create_node'] contains 'ssh_key'. Likewise NodeAuthPassword is used to set the initial password when the 'create_node' feature contains 'password'.

However the code doesn't really back that up, and EC2 in particular doesn't support that.

Is there an interface to determine if I can pass NodeAuth* to create_node? If there is, what is it? I will then submit patches to advertise support for NodeAuth* on drivers that do and try and improve the docs.

If there isn't, I would like to add one. The one I described would be the ideal one, i think, but it would have side effects on EC2/deploy_node?