ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Bakker (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACE-208) Amazon node launcher should be able to use an existing key pair
Date Fri, 02 Dec 2011 09:29:39 GMT

    [ https://issues.apache.org/jira/browse/ACE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161505#comment-13161505
] 

Paul Bakker commented on ACE-208:
---------------------------------

To use an existing key pair you need to install the private key on the ACE machine and specify
the path to this file in the node launcher configuration. I also upgraded the SSH library
to jclouds-sshj because this is recommended. 
                
> Amazon node launcher should be able to use an existing key pair
> ---------------------------------------------------------------
>
>                 Key: ACE-208
>                 URL: https://issues.apache.org/jira/browse/ACE-208
>             Project: Ace
>          Issue Type: New Feature
>            Reporter: Paul Bakker
>         Attachments: Added_config_option_to_configure_an_existing_keypair_and_private_key.patch
>
>
> Now a new key pair is always created for new nodes. This is not always convenient because
you need to first save the key pair to ssh to the new machine. Most of the time you already
have a key pair for a group of nodes, this should be usable from the node launcher.
> I patched this by adding a "keypair" configuration option. If this new configuration
option is omitted the behavior remains the same. If you specify a value, the value is the
name of the key pair.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message