libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <>
Subject [jira] [Updated] (LIBCLOUD-367) Proper use of create_node and NodeAuthSSHKey
Date Thu, 28 Nov 2013 09:01:51 GMT


Tomaz Muraus updated LIBCLOUD-367:

    Fix Version/s: 0.14.0-beta3

> Proper use of create_node and NodeAuthSSHKey
> --------------------------------------------
>                 Key: LIBCLOUD-367
>                 URL:
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>            Reporter: John Carr
>            Assignee: Tomaz Muraus
>             Fix For: 0.14.0-beta3
>         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
> 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 was sent by Atlassian JIRA

View raw message