incubator-libcloud mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Haering (JIRA)" <j...@apache.org>
Subject [libcloud] [jira] Created: (LIBCLOUD-42) Add Support for Deployments using SSH Keys
Date Mon, 28 Jun 2010 18:28:49 GMT
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


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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message