Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ace-dev@incubator.apache.org
Date: Fri, 2 Dec 2011 00:10:40 +0000 (UTC)
From: "Paul Bakker (Updated) (JIRA)" <jira@apache.org>
To: ace-dev@incubator.apache.org
Message-ID: 
 <936266216.33406.1322784640311.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <58931236.33404.1322784640250.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (ACE-208) Amazon node launcher should be able to
 use an existing key pair
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Paul Bakker updated ACE-208:
----------------------------

    Attachment: Added_config_option_to_configure_an_existing_keypair.patch
    
> 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.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