[
https://issues.apache.org/jira/browse/JCLOUDS-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901196#comment-13901196
]
Ignasi Barrera commented on JCLOUDS-468:
----------------------------------------
The DigitalOcean provider also needs a better keypair creation strategy. It
could be worth trying to extract the AWS logic, as the checks it performs seem
to be generic, into a strategy in jclouds-compute so we can easily align all
providers with the standard keypair creation flow. WDYT?
> Nova needs to handle key pair creation better in the ComputeService
> -------------------------------------------------------------------
>
> Key: JCLOUDS-468
> URL: https://issues.apache.org/jira/browse/JCLOUDS-468
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-compute
> Reporter: Everett Toews
> Priority: Minor
> Labels: openstack
> Fix For: 1.8.0
>
>
> Nova needs a strategy so it behaves more like
> org.jclouds.aws.ec2.compute.strategy.CreateKeyPairPlacementAndSecurityGroupsAsNeededAndReturnRunOptions.createNewKeyPairUnlessUserSpecifiedOtherwise()
>
> Right now it only has
> org.jclouds.openstack.nova.v2_0.compute.loaders.CreateUniqueKeyPair which
> does not examine TemplateOptions to determine what to do.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
