[dev] [jira] [Updated] (LIBCLOUD-42) Add Support for Deployments using SSH Keys

["Tomaz Muraus (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LIBCLOUD-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Muraus updated LIBCLOUD-42:
---------------------------------

    Fix Version/s:     (was: 0.5.0)
                   0.5.1

> Add Support for Deployments using SSH Keys
> ------------------------------------------
>
>                 Key: LIBCLOUD-42
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-42
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Russell Haering
>             Fix For: 0.5.1
>
>         Attachments: ec2keys.diff
>
>
> There is currently no support for deploying nodes using pre-install ssh keys as is required, for example, by EC2. In my github fork[1] I have added basic support for this (I'll attach a diff as well).
> An EC2 deployment using this patch looks something like this:
> deploy_node(Provider.EC2_US_EAST, name=name, image=image, size=size,
>             deploy=deployment, ex_keyname='foo', ssh_key='foo.pem')
> My main concerns are that I'm not sure if passing the path to the private key is entirely consistent with existing conventions, and this will break if someone passes in a NodeAuthSSHKey (although that was true before as well).
> [1]: http://github.com/russellhaering/libcloud

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira