[jira] [Updated] (JCLOUDS-815) The SoftLayer provider should honor the authorizePublicKey option

["Ignasi Barrera (JIRA)" <ji...@apache.org>]

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

Ignasi Barrera updated JCLOUDS-815:
-----------------------------------
    Issue Type: Improvement  (was: Bug)

> The SoftLayer provider should honor the authorizePublicKey option
> -----------------------------------------------------------------
>
>                 Key: JCLOUDS-815
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-815
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-compute
>    Affects Versions: 1.8.1
>            Reporter: Ignasi Barrera
>              Labels: softlayer
>
> Currently the SoftLayer ComputeService implementation ignores the TemplateOptions#authorizePublicKey option. The custom SoftLayerTemplateOptions provide a way to attach an existing ssh key to a node, but the generic options should be taken into account too.
> The following lines configure the SSH keys when creating a node:
> https://github.com/jclouds/jclouds/blob/master/providers/softlayer/src/main/java/org/jclouds/softlayer/compute/strategy/SoftLayerComputeServiceAdapter.java#L200-L207
> If the authorizePublicKey option has been set, a new SSH key must be created and assigned to the virtual guest. This may require creating the missing API methods to manage the SSH keys.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)