[dev] [jira] [Created] (LIBCLOUD-367) Proper use of create_node and NodeAuthSSHKey

["John Carr (JIRA)" <ji...@apache.org>]

John Carr created LIBCLOUD-367:
----------------------------------

             Summary: Proper use of create_node and NodeAuthSSHKey
                 Key: LIBCLOUD-367
                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-367
             Project: Libcloud
          Issue Type: Bug
          Components: Compute
            Reporter: John Carr


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?



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira