[
https://issues.apache.org/jira/browse/LIBCLOUD-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726714#comment-13726714
]
ASF subversion and git services commented on LIBCLOUD-367:
----------------------------------------------------------
Commit 506c0fc07aaeb5c7477c3ab920d5e1a48777bb12 in branch refs/heads/0.13.x
from [~jc2k]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=506c0fc ]
Fix create_node feature metadata (LIBCLOUD-367)
Signed-off-by: Tomaz Muraus <[email protected]>
Conflicts:
libcloud/compute/drivers/ec2.py
> 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
> Assignee: Tomaz Muraus
> Attachments: 0001-Fix-create_node-feature-metadata-LIBCLOUD-367.patch
>
>
> 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
